A working drawing set

Five plates that carry the whole design.

Each plate is one sheet from a working set. Move between them, then break a dependency to see which record still stands.

Bounded automation

The loop, field note

The agent came last. It uses the same typed operations a person already trusts. Policy decides. Live verification closes the record.

Select a dependency to see what still holds when it breaks.

Plate 05, The loop, field noteThe agent came last. It uses the same typed operations a person already trusts. Policy decides. Live verification closes the record. A workshop bench diagram. On the left, a stack of typed tool cards lists the name, input, preview mode, and risk class of the operations an agent may propose. In the middle, a rectangular pipeline runs from observe to reconcile, preview, constrain, verify, and record. A policy gate diamond sits in the middle of the pipeline, stamped human or policy. On the right, a ruled ledger page shows the invariant columns of an audit record: timestamp, operation class, target class, preview delta, decision, and verification. The ledger is marked example record synthetic. A first-person field note runs above.PLATE 05Bounded automationThe loop, field noteREV 2026-07FIELD NOTEI did not give a model shell access on day one.I gave it read-only observation, then the same typed operations I already trusted.The ledger below is the shape of that trust, not a record of any real system.THE OWNER, 2026 REVIEWTYPED TOOLSRISK-CLASSIFIEDsvc.statusREADask a service how it is doingpreview n/asvc.logs.tailREADread recent lines from one service logpreview n/asvc.restartREVERSIBLErestart one service with a previewpreview requiredbackup.verifyREVERSIBLEask the repo to prove a snapshot restorespreview alwaysnet.route.addDESTRUCTIVEadd one documented route with approvalpreview alwaysTHE LOOPREAD BROAD, CHANGE NARROW01OBSERVE02RECONCILE03PREVIEW04CONSTRAIN05VERIFY06RECORDPOLICY GATEHUMAN or POLICYdecides what runsEACH STEP, ONE JOB01 OBSERVEread authoritative and live sources02 RECONCILEname the difference between them03 PREVIEWreturn the exact proposed change04 CONSTRAINpolicy and typed tools decide05 VERIFYprove the live outcome06 RECORDwrite the durable evidenceAUDIT LEDGEREXAMPLE RECORD, SYNTHETICCOLUMNS OF THE RECORDTIMESTAMPYYYY-MM-DD HH:MM:SSA time a person can find, not just an id.OPERATIONsvc.restartThe name of the typed tool, not free text.TARGET CLASSWEB TIER, 1 OF 3A role and count, never a hostname.PREVIEW DELTA+1 unit, 0 config driftThe exact change the preview promised.DECISIONHUMAN or POLICY idWho or which policy said yes, and why.VERIFICATIONsmoke: passThe smoke test that closed the record.next record readyModels propose. Policy decides. Typed tools constrain. Verified live state closes the record.

Plate 05, Bounded automation

The loop, field note

The agent came last. It uses the same typed operations a person already trusts. Policy decides. Live verification closes the record.

  1. FIELD NOTE

    I did not give a model shell access on day one. I gave it read-only observation, then the same typed operations I already trusted.

  2. TYPED TOOLS

    Each tool has a name, a small input, a preview mode, and a risk class. Read, reversible, destructive, or physical.

  3. THE LOOP

    Observe, reconcile, preview, constrain, verify, record. Read broad, change narrow, then close the record on the live outcome.

  4. POLICY GATE

    A human or a policy decides what runs. Sensitive changes go through the same gate whether the model or a person proposes them.

  5. AUDIT LEDGER

    Timestamp, operation, target class, preview delta, decision, verification. A role and a count, never a hostname.

  1. 09-automation
  2. 10-ai-agentic
  • ● verified or healthy
  • ▲ degraded or needs attention
  • ■ failed dependency

Plate 05

The loop, field note

Scroll or drag to move across the drawing. Pinch to zoom on touch devices.