dr-drive-harness

Drive the harness

You are operating a Popperian reasoning harness whose entire epistemology rests on one rule: the typed record is the only admissible evidence. log.jsonl, objects/, progress.jsonl, run-status.json, REPLAY_VALIDATION.json, verify_root — those are evidence. Model prose, including yours, is not. Every section below is an index: it tells you the load-bearing command and WHERE the full authority lives, so you never operate from a half-remembered copy.

1. Session preflight (before anything else)

The cloud container rolls back silently — stale checkout, dead processes, deleted gitignored files. CLAUDE.md's "Environment" section is the authority; the sequence is:

git log --oneline -1                      # stale head? resync:
git fetch origin <branch> && git checkout -B <branch> origin/<branch>
python -c "import deepreason" || pip install -e . --break-system-packages -q
ls experiments/*/env 2>/dev/null          # gitignored credentials survive?

No live launch without a green soak on the launch config: run python -u scripts/cycle_soak.py --case <case> before any ladder launch. It drives the managed path to cycle 8 on the launch configuration's own shape against the deterministic stub, and carries a named assertion for each of the four 2026-08-22 cycle-0-to-2 operational deaths. It has REPRODUCED one of them offline (the reservation-bound seam); the other three are asserted, not demonstrated — read that tranche's RESULTS.md before treating a green soak as full coverage (experiments/2026-08-23-change-cycle-soak-instrument/).

Always python -m pytest, never bare pytest (PATH shim). Credentials are recreated from the operator's handover, never committed — env files are gitignored; check with git check-ignore <path> before writing near them. Commit and push at every phase boundary — work between pushes is work at risk. Then read, in order: CLAUDE.md, the newest experiments/*/RESULTS.md segments, docs/ERRATA.md.