clodex-build

clodex-build — small batches, an explicit contract, a reviewed delta

Overview

This stage turns an approved plan into commits. It owes the run one thing per batch, and all of it is fact in the event log rather than claim in a transcript:

Fact	Event	In the manifest
what this batch may touch	batch:opened	batches[].owned_paths
the delta was reviewed, and the verdict	batch:reviewed	batches[].delta_review
the commit it landed in	batch:committed	batches[].commit

Plus, when an assumption breaks mid-flight, a plan amendment — never silent drift.

Where this stage ends. You prove each batch against its own test expectations: the profile's test command green, plus your review of the delta. You do not run the plan's declared evidence classes, record verification:evidence, or decide anything about verification debt — that is clodex-verify. You do not write the changelog, bump the version, tag, push, or deploy — that is clodex-ship, and §2 makes those files forbidden to you.

You arrive here from clodex (which owns preflight, the profile, and the run directory) or from clodex-plan (which owns the plan, its owned paths, and its approval). If you were invoked without an absolute run directory, 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 "")')"
cd "$REPO"
PROFILE="$REPO/.clodex/profile.json"

Shell variables do not survive between command invocations — re-establish this block at the top of every shell you run these procedures in. Everything below runs from $REPO; git add, git status, and the profile reads all resolve relative paths against the current directory, so from a subdirectory they answer the wrong question.