Version. 0.20
Date. 2026-08-03
Charter. standing-notes/dunin7-standing-authorization-charter-v0_1.
Author. Claude Code (execution session). Operator: Marvin Percival.
Supersedes. v0.19 at record cd46421. All earlier versions stand as siblings; v0.3 remains deliberately absent.
Changes from v0.19. CR-2026-165 filed and execution begun; halted at Step 3 (the acceptance run). No merge, no tag, no push to loomworks-engine's main. One decision queued.
CR-2026-165 v0.1, filed at change-requests/cr-2026-165-stand-up-sequence-v0_1.md, record cd46421.
CR-2026-165 Step 3 halt report, filed at current-status/cr-2026-165-step-3-halt-report-v0_1.md, copy in ~/Downloads.
On loomworks-engine, branch cr-2026-165-stand-up-sequence (off main ffc29af, NOT merged, NOT pushed):
07dd8e3 — scripts/bootstrap_engagements.py, the standalone entry point for the four ensure_* bootstrap calls, callable without a web server. Smoke-tested for idempotency (first run: 4× created; second run against the same throwaway: 4× already present).296f7f8 — README ## Database section, carrying the five-command stand-up sequence, prerequisites, and traps.
Suite re-run after both commits matched the Step 0 baseline exactly (1 failed, 3467 passed, 68 skipped — the same long-standing test_stele_router_mount.py failure, no new failure).
The acceptance run (§6, the CR's own gate) failed at step 4. Following only the committed README's ## Database section, on a fresh throwaway: steps 1–3 (engine to 0033, the bootstrap, engine to head) all worked exactly as written. Step 4's command — uv run --project /path/to/stele alembic stamp 0001_baseline, run from loomworks-engine's own directory — failed: ModuleNotFoundError: No module named 'loomworks'.
Root cause: uv run --project <dir> swaps the Python environment, not Alembic's working-directory-based config discovery. The command ran loomworks-engine's own alembic.ini/migrations/env.py using Stele's venv. The README's step 4, as drafted, does not match what the B-41 verification actually ran (which cd'd into Stele's checkout first) — a drafting error introduced when translating the verification's proven command into the README.
Per C-3, this halts rather than being patched in-flight — the correction is CR-scope text this execution session drafted incorrectly; fixing it and re-running the acceptance inside the same session would be exactly the kind of in-flight scope absorption the charter forbids, and the pattern this whole build-list item (B-41) exists to correct against (B-9's workarounds).
Clean halt, no partial state. The acceptance throwaway reached engine head (0102) cleanly; Stele's stamp never wrote anything (stele_alembic_version was never created). Throwaway dropped, confirmed absent. playground_dev/playground_test never connected to.
Q — correct the README's step 4 command; how.
| | |
|---|---|
| Question | Replace uv run --project /path/to/stele alembic ... with a cd-based form (proven, matches the verification), an explicit -c form (untested, prepend_sys_path may not resolve), or something else? |
| Default | The cd-based form — already proven to work. |
| Blocks | The acceptance run and everything after it (Step 4/implementation notes, Checkpoint A, Checkpoint B). |
| Proceeds regardless | Nothing merges until the acceptance run completes clean — that is gate item 2. Steps 1–2 stand, committed to the unmerged branch, suite-clean, ready to carry forward once step 4's command is corrected. |
R-2 (CR execution) held to its checkpoints. Auto-proceed steps (0–2) ran unattended, per-step commits, suite green at each against the Step 0 baseline. The acceptance-run failure is one of Checkpoint A's own named halt conditions — halted and queued exactly as specified, not pushed through.
Branch discipline held. Current branch checked before the first commit; a feature branch was created before any write. main untouched throughout, on both repositories.
R-1 for two filings, each on a clean pre-flight: the halt report and this status brief.
Discipline clause / C-3 held. The command that failed was named exactly, quoted with its traceback; the root cause was diagnosed after stopping, not used to push through mid-run; the correction was queued rather than absorbed in-flight.
DUNIN7 — Done In Seven LLC — Miami, Florida DUNIN7 — status brief — v0.20 — 2026-08-03 The gate caught exactly what it was built to catch.