About & publication

I developed this method from my own practice: taking one product from a folder of scattered documents to something running in production, alone, with coding and design agents doing the work they are briefed for. What holds it together is one person accountable for the outcome front and back, a second session whose only job is to challenge the first, and an agent sent back to the organization's own starter and conventions before it touches the code. The timings quoted on this site come from that practice, not from a study.

Processes and examples specific to organizations I've worked with stay in their internal materials.

Vocabulary

Term	Meaning on the site
Product Builder	The person accountable for one product outcome, end to end, front and back.
Ops	The horizontal services a Product Builder draws on — Design, Frontend, Backend and API, Data, access, delivery and review.
Ops owner	The named person who owns one of those services and answers requests for it. "Ask someone" is not a route.
Gate	One of the seven steps of the method, numbered 0 to 6. Each one says what you do and what you have in hand before you move on.
Control session	The second session, open beside the main one, whose job is to challenge it. It reads, checks and challenges; it changes no code and decides no scope.
Standing guardrail	The rule that sends the agent back to the organization's frontend starter and backend conventions before every change to the code.
Project memory and journal	The two files opened at the first gate: the memory holds decisions and trade-offs, the journal the dated record of what happened.

Term

Meaning on the site

Product Builder

The person accountable for one product outcome, end to end, front and back.

Ops

The horizontal services a Product Builder draws on — Design, Frontend, Backend and API, Data, access, delivery and review.

Ops owner

The named person who owns one of those services and answers requests for it. "Ask someone" is not a route.

Gate

One of the seven steps of the method, numbered 0 to 6. Each one says what you do and what you have in hand before you move on.

Control session

The second session, open beside the main one, whose job is to challenge it. It reads, checks and challenges; it changes no code and decides no scope.

Standing guardrail

The rule that sends the agent back to the organization's frontend starter and backend conventions before every change to the code.

Project memory and journal

The two files opened at the first gate: the memory holds decisions and trade-offs, the journal the dated record of what happened.

Publication details