clodex-verify

clodex-verify — evidence per class, debt for the rest, no gate

Overview

This stage turns "the batches are committed" into proof, and it owes the run exactly two kinds of fact — both in the event log, neither in a transcript:

Fact	Event	In the run manifest
a declared class was produced, and what showed it	verification:evidence	verification.evidence[]
a declared class was not produced, why, and what that risks	verification:debt	verification.debt[]

Every class clodex-plan declared ends in exactly one of those two states. Never neither, never both. §10 checks that property mechanically.

This stage has no gate

Verify records debt. It never accepts, waives, or blocks on it. There is no "is this debt OK?" question in this document, and you must not invent one: a run with three debt entries and a run with none both leave this stage the same way — handed to clodex-ship.

Debt is accepted in exactly one place: clodex-ship's release authorization, once, by the user, alongside the exact external actions they are authorizing. That is the design's single binding debt gate. Asking the user to approve debt here would double the gate and leave ship approving something already half-approved — so you do not ask. You write it down, plainly, and you say it out loud in the handoff.

Where this stage ends

You do not commit, you do not edit tracked files, and you do not fix code (§2). You do not write the changelog, bump the version, tag, push, or deploy — that is clodex-ship. You read the deploy block of the repo's committed profile (<repo>/.clodex/profile.json) only to know what ship will do, never to do any of it.

You arrive here from clodex or from clodex-build, which hands you an absolute run directory. If you were invoked without one, stop and invoke clodex — do not go looking for a run yourself.

---

0. Paths and commands

CLODEX_HOME="${CLODEX_HOME:-$HOME/.claude/skills/clodex}"   # the router's dir, not this one
STATE="$CLODEX_HOME/state/clodex_state.py"
RUNNER="$CLODEX_HOME/runner/run-codex.sh"
RUN_DIR="<the absolute run dir you were handed>"
SNAP="$(python3 "$STATE" rebuild "$RUN_DIR")"
REPO="$(printf '%s' "$SNAP" | python3 -c 'import json,sys;print(json.load(sys.stdin)["repo"])')"
PLAN="$(printf '%s' "$SNAP" | python3 -c 'import json,sys;print(json.load(sys.stdin)["plan"]["path"] or "")')"
LANE="$(printf '%s' "$SNAP" | python3 -c 'import json,sys;l=json.load(sys.stdin).get("lane") or "standard";print("standard" if l=="feature" else l)')"   # a pre-0.6 run (feature) takes the standard table
cd "$REPO"
PROFILE="$REPO/.clodex/profile.json"