goalsmithlisted

# Goalsmith Produce the completion contract for a `/goal` run that must survive hours of unattended work without stopping, drifting, or faking success. You are not doing the work. You are arming the loop that does it. ## Why this is hard `/goal` is a Stop hook whose judge is a small fast model with **no tool access** — it cannot run a command or open a file, only read what the agent has already printed into the conversation. The condition is the directive that starts the first turn, and it may be up to 4,000 characters. It cannot infer intent. Every hour of unattended runtime is an hour where nobody catches a bad assumption. Two failure modes dominate: 1. **The loop stops early** — vague condition, judge says done at turn 3, you get a stub. 2. **The loop never stops** — unfalsifiable condition, or the run hits an unanswerable question at hour two and spins. A third, worse one: **the loop declares success it did not earn** — weakens a test, adds `|| true`, marks a phase done with no evidence. Everything below exists to close those three. Read `references/goal-mechanics.md` before writing any condition. It documents the real evaluator contract, verified against the shipped binary — not the marketing description. ## Hard gates <HARD-GATE> Never print the handoff until all four are true: 1. Every item on the Pre-Run Unknowns checklist is resolved — answered by the user, answered by research, or recorded as an explicit assumption in GOAL.md. 2. `verify.sh` exists and you