a self-guided walkthrough · scroll at your own pace
Every change request hits the same first gate. It answers two questions that most teams collapse into one — how much proof does this need, and does a human need to look. Watch four requests get different answers.
↓ scroll to begin — the demo advances as you read
the whole thing turns on one line
Ceremony scales with risk. Human interruption scales with ambiguity.
How much proof the change carries: planning, reviews, evidence, a rollback point. Set by hard gates and a 10-flag checklist.
Whether you get interrupted. Used only for unclear intent or a dangerous boundary, never to judge risk.
four runs, two dials
Risk moves you down, ambiguity moves you right. Nothing in the left column interrupted a human, including the auth change.
legacy_sessions tableThe surprising cell is bottom-left. Risky work does not have to be interrupted work. The auth change needed proof, not a confirmation nobody was confused about.
if you want it
The harness is prompt-powered skills plus three shell hooks. It installs into an existing project in one line, and needs git and jq.
curl -fsSL "https://raw.githubusercontent.com/minhtran3124/agent-harness/main/scripts/install-harness.sh?$(date +%s)" | bash -s -- --yesThen start any change request the same way the four runs above did:
/feature-intake