Builder
Forge
Forge is the one that ships. Give it Archer's plan and it writes the code, wires the integrations and fixes what's broken, then verifies its own work before calling it done. This entire site, Forge built. I'm not being cute; check the footer.
I'm not a developer. I'm an ex-lawyer with a publishing company and a list of things that need building: landing pages, signup forms, spreadsheets that talk to each other, the little scripts that glue a business together. Forge is how those get built without me hiring anyone or learning to code at midnight.
Two habits make it trustworthy. It builds the smallest thing that works instead of the impressive thing that doesn't, and it verifies before it reports: runs the code, submits the form, checks the email arrived. When something fails you see the actual error, because a builder that only brings good news is a builder you end up checking on anyway.
What Forge does
- ✓Builds from a plan: pages, scripts, automations, integrations, fixes.
- ✓Builds the smallest thing that works first, then verifies it actually runs.
- ✓Matches the conventions already in your project instead of imposing its own.
- ✓Reports honestly. If the tests fail, you see the error, not a shrug.
One job, start to finish
Archer's plan says step three is "build the signup page and wire the email tool". Here's what Forge does with that line.
- 1
Forge reads the plan and the vault: which email tool you use, what the brand looks like, what already exists so it doesn't rebuild it.
- 2
It builds the smallest working version first: one page, one form, one welcome email.
- 3
Then it verifies, and verifying means doing: it submits the form, watches the webhook fire, checks the thank-you page on mobile.
- 4
Something's off (there's always something): the email tool rate-limits free accounts. Forge notes it instead of hiding it.
- 5
You get the report: built, verified, and one open item with a cost attached, before it becomes Saturday's mystery.
- 6
It hands the work to Bench for review, because the builder marking its own homework is how gurus end up refunding people.
What a real Forge report looks like
FORGE · Build summary Built: signup landing page + email-tool webhook Verified: form submits, welcome email fires, thank-you page renders on mobile (tested all three, not assumed) Open: the email tool rate-limits at 100/day on the free tier. Fine for launch, will need the $15 plan if this works. Next: hand to Bench for review, or wire the second sequence?
Illustrative example. Note the 'Open' line: Forge tells you about the rate limit before it becomes Saturday's mystery.
Where Forge fits in the crew
Forge works from Archer's plan and hands finished work to Bench for review before it ships. Build, verify, review. In that order, every time.
The honest bit
Forge needs a plan or at least a clear ask; 'make it better' produces exactly what you'd expect. It will also tell you when a job is bigger than a quick build rather than half-building it, which is occasionally not what I want to hear and always what I need to.
Straight from Forge’s actual file
Every crew member is a file you can read and edit. This is a real slice of the one you get, not a mock-up. The full file, and the other seven, come with the download.
## How you work - Don't over-engineer: do what the task needs, no speculative abstractions. - Verify your work (run it, test it) before declaring it done. - Report outcomes honestly: if something fails, say so with the error.
Forge comes with the other seven.
One download, eight specialists, the brain vault and the honest autonomy layer. Reskin the lot to your business.