SELECTED BUILDS · EVIDENCE BEFORE PROMISES
Systems we have built. Not a list of things we might.
A curated record of working client and internal systems: what goes in, what the system does, what comes out, where people stay in control and what proof class applies.
Each build is inspectable before it asks for belief.
client-liveWorking client case study with public-safe evidence.
internal-liveWorking internal system with private source boundaries.
controlled-testMeasured test evidence from a defined run.
development-previewNo working-loop evidence published.
Instantly Boost+
An Instantly integration that turns supplied LinkedIn profiles or domains into verified contact data, researched personalisation, tailored offers and strategic outreach—then stops when a real sales conversation begins.
- Input
- LinkedIn profiles or company domains
- System work
- Verify, research, write, send and classify replies
- Output
- Sales-ready enquiries for the client's team
- Human boundary
- Sales team owns booking, selling and closing
- Proof class
- controlled-test
First controlled test: 13 replies from 157 leads · 8.28% reply rate.
Inspect proofHeyReach Boost+
A HeyReach integration that turns conversation history, tone, relationship stage and enrichment context into carefully prepared DM drafts—leaving judgment and the final send with a person.
- Input
- Conversation history, account instructions and enrichment context
- System work
- Sync, interpret relationship stage and prepare drafts
- Output
- Reviewable relationship-aware DM drafts
- Human boundary
- A person edits, approves and sends manually
- Proof class
- internal-live
Working internal sync, relationship-stage, review-queue and manual send states.
See workflowGolved's Devlogs
An evidence-led devlog pipeline that gathers relevant work from team and community context, builds one canonical dossier, checks it for private material and prepares channel-ready drafts for human review.
- Input
- Development notes, release context and approved community material
- System work
- Collect, dossier, guard, adapt and queue review
- Output
- Channel-ready devlog drafts and public archive entries
- Human boundary
- John reviews and manually publishes
- Proof class
- internal-live
Working dossier, redaction and channel-draft pipeline with a public devlog archive.
Inspect proofArgus Watchtower
An evidence-first watchtower that turns operational signals into prioritised findings, safe actions and accountable follow-up. The next 1% is an operating cadence, not guaranteed 1%-daily compounding.
- Input
- Allowlisted operational signals and expected-state rules
- System work
- Compare signals, classify findings and route safe action
- Output
- Prioritised findings with evidence and owner lane
- Human boundary
- Unsafe or uncertain work remains human-required
- Proof class
- internal-live
Working internal projection of signals, findings, severity, source counts and safe actions.
Inspect proofKleos Bug Bounty
A live-development concept for a character-led Discord bug-bounty loop: community reports become structured issues, resolution travels back to the reporter and approved rewards recognise useful contributions.
- Input
- Proposed Discord bug reports
- System work
- Plan report structure, triage and resolution reply
- Output
- Planned issue and recognition loop
- Human boundary
- Moderator and developer approval required
- Proof class
- development-preview
Development preview · no working-loop evidence published.
View development previewCompare the fit quickly.
Build status says where the page sits today. Proof class says what kind of evidence supports the claim.
InstantlyClient case study · liveLinkedIn profiles or company domainsSales-ready enquiries for the client's teamSales team owns booking, selling and closingcontrolled-test
HeyReachInternal build · ForgeOS launch componentConversation history, account instructions and enrichment contextReviewable relationship-aware DM draftsA person edits, approves and sends manuallyinternal-live
GolvedInternal build · ForgeOS rebuild plannedDevelopment notes, release context and approved community materialChannel-ready devlog drafts and public archive entriesJohn reviews and manually publishesinternal-live
ArgusInternal build · joining ForgeOSAllowlisted operational signals and expected-state rulesPrioritised findings with evidence and owner laneUnsafe or uncertain work remains human-requiredinternal-live
KleosIn live development · coming soonProposed Discord bug reportsPlanned issue and recognition loopModerator and developer approval requireddevelopment-preview