Skip to content
← All insights
Orchestration

Agents draft. People decide.

The single rule behind every system we have put into production this year, and why it makes automation safer to adopt, not slower.

Drafts travel along a line into a gate valve turned by a person. Before the gate the line is the agents' work; after it, the released signal is the person's decision. AGENTS DRAFT PEOPLE DECIDE DRAFTS · REVERSIBLE DECIDE SENT · IRREVERSIBLE DIGI-DNA · NOTES 2026-10-24 THE GATE PLATE

Every operating system we shipped in 2026 runs on one rule: software prepares, a person approves. Agents draft the proposal, the follow-up email, the article, the lead dispute. Nothing prices, sends, or publishes until someone with authority says yes.

This sounds like a brake. In practice it is the accelerator. An owner who knows nothing leaves the building without a signature will let software do far more of the preparation, because the downside of a bad draft is a rejected draft, not a lost client.

Where the boundary sits

The approval point belongs at the irreversible step. Reading a mailbox, scoring a lead, assembling a quote, drafting a reply: all reversible, all delegated. Sending the email, issuing the price, merging the article: irreversible, all approved. In the contractor's operating system we built, that rule is written down as a standing constraint: agents never send mail and never write to the codebase.

Four reversible tasks (read mailbox, score lead, assemble quote, draft reply) feed one draft. The draft meets a gate valve turned by a person at the boundary between reversible and irreversible work. Past the gate the signal reaches send email, issue price and merge article, and every approval drops into a record of who, what, when and which draft. REVERSIBLE · DELEGATED IRREVERSIBLE · APPROVED READ MAILBOX SCORE LEAD ASSEMBLE QUOTE DRAFT REPLY DRAFT APPROVER APPROVE = SEND SEND EMAIL ISSUE PRICE MERGE ARTICLE FROM THE PERSON'S OWN MAILBOX WHO WHAT WHEN WHICH DRAFT RECORD 1 2 3 4 DIGI-DNA · NOTES 2026-10-24 APPROVAL GATE FIG. 1
Fig. 1The approval gate. (1) Agents prepare drafts; everything left of the boundary is reversible. (2) The gate sits at the irreversible step. (3) Approval sends from the person's own mailbox. (4) Every approval is written to the record.Full-size drawing for Fig. 1 (SVG)

Make approval cheap

A gate only works if passing it is fast. In the operations console we built for two separate companies, a person reads the draft in place and approval sends it from their own mailbox with their own signature. Revisions are picked up hourly through the working day. The friction is a tap, not a context switch.

Agent console with a queue of drafts waiting on the person, one draft reply opened with Approve and Close controls.
Fig. 2The gate in practice: drafts wait in a queue, are read in place, and approve means send.Screenshot of the running system on synthetic demo data; no client records shown.

Write it down

Every approval is a record. Who approved what, when, against which draft. That audit trail is what lets a business trust the system enough to hand it more work next quarter.

The downside of a bad draft is a rejected draft, not a lost client.

This is the fifth primitive of the Digi-DNA Kernal in its simplest form: verification, with a human at the point where verification matters most.

Build the system behind the outcome.

Start a Strategic Build →