clodex-audit

clodex-audit — investigate, tag every claim, route the follow-ons

Overview

This lane earns its existence from usage evidence: two major audit asks ran manually in one weekend, both excellent, and their report shape is encoded here. It owes the run exactly three things:

1. A report file in the repo, at the profile's plans directory (or a reports/ sibling when the repo has one), in the §5 shape.
2. Every claim in it tagged — VERIFIED (<method>) or HYPOTHESIS (<what would confirm it>) — with the load-bearing ones also recorded as findings (finding:recorded, source: "audit") and the artifacts that prove them as evidence (verification:evidence).
3. The run closed with release.state untouched at not-started — an audit releases nothing, and its manifest must say so without ceremony.

The manifest's stage stays open for the life of an audit. The lane's operational shape — open → investigate → report → closed — lives in this document's sections, not in stage events: the vocabulary is frozen at 23 names, stage:plan:entered would be a lie, and a run at stage open with lane audit is exactly how the router and the runs index recognize an audit in flight. No build, no verify, no ship, ever; the follow-on work an audit surfaces is routed per item (§5) into new runs.

You arrive here from clodex, which owns preflight, the profile, and the run directory. Invoked without an absolute run dir → stop and invoke clodex.

0. Paths and commands

CLODEX_HOME="${CLODEX_HOME:-$HOME/.claude/skills/clodex}"
STATE="$CLODEX_HOME/state/clodex_state.py"
RUN_DIR="<the absolute run dir the router handed you>"
SNAP="$(python3 "$STATE" rebuild "$RUN_DIR")"
REPO="$(printf '%s' "$SNAP" | python3 -c 'import json,sys;print(json.load(sys.stdin)["repo"])')"
cd "$REPO"
PROFILE="$REPO/.clodex/profile.json"

Engine verbs, exit codes, and the lock rules are the clodex skill's §"Paths and commands" and §2. Events are written to files and piped on stdin, or passed inline with append -e for small ones.