a self-guided walkthrough · scroll at your own pace

Four requests. One question: how careful should I be?

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.

dial one
Risk

How much proof the change carries: planning, reviews, evidence, a rollback point. Set by hard gates and a 10-flag checklist.

dial two
Ambiguity

Whether you get interrupted. Used only for unclear intent or a dangerous boundary, never to judge risk.

four runs, two dials

The same harness, four different answers

Risk moves you down, ambiguity moves you right. Nothing in the left column interrupted a human, including the auth change.

intent is clear
intent is ambiguous
low risk
tiny · ran alone
Fix the wrong copyright year in the footer
Branch, edit, commit. No plan, no research, no review, no human. Four steps end to end.
tiny · asked first
“Clean up the old config handling”
One file, no gate — but clean up has several plausible readings. Low confidence stops for confirmation regardless of how small the change is.
high risk
high-risk · ran alone
Change how JWT auth validates expired tokens
Full chain, adversarial review, PR opened for a human to merge — and it never once stopped to ask. Heavy proof, zero interruption.
high-risk · stopped
Migration to drop the legacy_sessions table
Whether anything still reads that table is unverified. Destructive and ambiguous → a recorded escalation, and silence keeps it blocked.

The 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

Drop it into a repo

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 -- --yes

Then start any change request the same way the four runs above did:

/feature-intake