dos-goal-gatelisted

# dos-goal-gate — gate "I'm done" on a witness, not on self-report > **A completion condition the agent checks against its own narration is the > exact failure DOS exists to fix.** When an agent decides "the goal is met" by > re-reading what it just wrote, the part deciding ground truth *is* the part > being judged — that is **consistency, not grounding** (docs/138). This skill > never decides done-ness by re-reading the transcript. It turns the goal into a > set of checkable EFFECT claims, then wires the Stop decision so the agent > cannot stop until a read-back whose **byte-author is not the agent** (git > ancestry, an OS exit code, a fresh state read) corroborates each effect. The > kernel decides; the skill narrates. The shape is domain-free: **state the goal as effects → wire the Stop gate → on each stop, witness every effect → stop only when all are corroborated.** The *policy* (which plan grammar, which lanes, where state lives) is data read from `dos doctor --json`, never literals this screenplay hardcodes. **Why this is not just "ask the model if it's done."** A harness stop-condition ("keep going until X") is evaluated by a model reading the session — so a confident, fluent narration of an X that the world does not corroborate ends the work early (the silent fail of docs/177). The gate below replaces that judgment with a verdict over evidence the agent did not write: a phase is done when *git* says a commit backs it, not when the agent says it committed; a file e