People ask how we build things. They expect an answer involving sprints, standups, and retrospectives. They expect a workflow diagram with swimlanes and approval gates.
The answer is simpler than that, and weirder.
Intent → Specification → Artifact
That’s it. Three stages. No ceremonies.
Intent is the raw material. It’s the 3 AM thought that won’t let you sleep. It’s the frustration with every existing tarot app being either a subscription trap or an ad delivery mechanism with a mystical wallpaper. Intent is the thing you can’t not build.
Specification is the compression of intent into executable instructions. Not a requirements document — those are bureaucratic artifacts designed to protect managers from accountability. A specification is a contract between the builder and the machine. It says: here is exactly what this thing does, and here is exactly what it doesn’t do.
Artifact is the output. The shipping software. The thing that exists in the world and does what it was specified to do, nothing more and nothing less.
The Machine Behind the Machine
The forge itself is a recursive system. It uses AI not as a replacement for thought but as an amplifier. The human provides intent and judgment. The machine provides velocity and precision. Neither works without the other.
Every artifact ships through the same pipeline:
- Specification written in structured format
- Architecture decomposed into sessions
- Each session executed, verified, committed
- Final artifact built, tested, deployed
- No step skipped. No shortcut taken.
The process is rigid because the output demands it. You can’t ship something clean if the process that built it is chaotic.
Why This Matters
It doesn’t, to most people. And that’s fine. The forge doesn’t build for most people. It builds for the ones who notice. The ones who pull a tarot card and realize the app isn’t trying to sell them a subscription to self-knowledge. The ones who feel the absence of ads like a breath of clean air.
Those people know. And the forge builds for them.