The conversation
You author the product spec, the architecture and the phase plan in a guided conversation that asks you the same questions the installed version asks in your terminal. You approve the plan before anything is built.
Halfcycle with the work taken off your desk
You describe the product in a guided conversation. The method runs behind it: spec, architecture, phases, feature specs, build. You approve at the gates and watch the phases land.
What it will be
Your whole vocabulary: a conversation, a dashboard, and a pull request
The dashboard
Phases in flight, gates passed and held, what a check caught and which class of failure it belongs to. Every gate the method's own rules can decide will run silently. The only interruptions you see will be the decisions that genuinely need you, each arriving with a recommendation and the cost of deciding late.
The pull request
Shipped code and a Build Record per phase, landing in your repository. Evidence an auditor, a board or a client can read, rather than a claim that it went well.
Glass box, not black box. You will run nothing and host nothing, and you will still be able to see why every gate passed.
Meanwhile
Two things you can do today
Available now
Run it yourself
The same method, installed into your own Claude Code, on your own seats. Free for solo developers.
Available now
Have us run it with you
We come in and run the method on your live product with your engineers. The phase that ships is real, and the deliverable is a team that can run it without us.