Principles

Control is a feature, not a footnote.

The useful question is not only “can this run?” but “what should remain visible, reviewable, and owned by a person?”

01

Start with one bounded problem

A narrow scope makes failure and ownership visible.

02

Read before write

First versions prefer observation, draft output, or human-reviewed actions.

03

Gate consequential actions

Sending, publishing, changing records, destructive actions, and financial steps remain behind explicit approval.

04

Make the system legible

Inputs, outputs, dependencies, tests, and limits belong in the handoff.

05

Separate draft from approved

Generated or proposed material is not official guidance until reviewed.

06

Leave a receipt

Record what ran, what changed, what failed, and what remains unverified.