How the factory works

One sentence per lane. Scroll to follow one change from an idea to production. Nothing below asks you to know the vocabulary first.

A conversation becomes a Jira issue, the issue becomes an Order pinned to one workflow release. Autonomous or HITL decides who answers the Order’s questions.

The plan is a set of items; each item becomes a track. Prerequisites order them. Decision points are asks on the Order’s board; machinery never waits for the model to remember.

The process is a workflow: an orchestrator, tracks, an acceptance and an accept decision. Its agents are prompt releases, each running on one session resolved once at admission. Change a prompt, a node, a bound or an agent, and the next order runs the new version.

The branch lives only as long as the track. The box runs the turns; the host runs the checks; a fresh review reads the exact head; the queue lands it on trunk.

The train drains the boxes that could be mid-turn, deploys, reopens. The acceptance then checks the change on the floor, behind a flag when it is flagged, and a person accepts. Shipping is observed, not declared.

People answer asks on the board. The orchestrator hears agents through an inbox and answers through doors. GitHub speaks in webhooks and checks; sbx in boxes and grants. Nothing is a chat log.

A repair round, a budget hold, a person’s Stop, a lost box regenerated. Every non-terminal state has an owner, a deadline and an exit. The twelve invariants, each one sentence.

Staging takes every trunk hourly. Production takes one digest that soaked on staging, after a person approves. The qualification tiers are the proof the page ends on.