Version. 0.1
Date. 2026-07-31
Charter. Operating under standing-notes/dunin7-standing-authorization-charter-v0_1, ratified 2026-07-30.
Author. Claude.ai (drafting session). Operator: Marvin Percival.
What this is. The document the charter's §7 requires and which did not exist until now. Every session appends its outcome here. The Operator reads this at cadence — twenty to thirty minutes, every day or two — answers Section 7's queue, performs the batched acts that are only his, and spot-audits anything at will.
Why v0.1 exists on 2026-07-31 rather than 2026-07-30. The charter was ratified on 2026-07-30 and its §5 interruption-replacement mechanism depends on this brief's Section 7. The brief was never created. For one working day the queue had no home, so forks defaulted back to interrupting the Operator — four of them, all of which belonged here or in the drafting session's own judgment. Recorded as a defect in the charter's rollout, not smoothed.
loomworks-record at e037a37, pushed and origin-verified.
| Artifact | Path | Commit |
|---|---|---|
| Combined engine inspection brief — B-29, B-27, B-5 | inspection-briefs/loomworks-b29-b27-b5-engine-inspection-brief-v0_1.md | 8d79e91 |
| Combined engine inspection findings | inspection-briefs/loomworks-b29-b27-b5-engine-inspection-findings-v0_1.md | e037a37 |
loomworks-engine at a317051 — untouched. No commit, no branch, no push. M uv.lock unstaged, as found before the session.
stele at 689de41, tag v0.4.0, clean.
B-27 — RESOLVED. The uncallable terminal commit route for creation doors 1 and 2 no longer exists; CR-2026-158's rider (a425ecd) unmounted it, and the live path calls the handler in process with all parameters explicit. The verdict rests on static source reads, not on the browser pass. The acceptance gate is no longer blocked by it.
W-16 — OVERTURNED, strike rather than schedule. Version-pinned Manifestation retrieval exists as a query parameter (manifestations.py:502) and was present identically at 1aac815, the walk-audit engine. W-16 was wrong when filed. This removes one of CR-B's four items.
B-5's staleness marker — a wire, not a build. GET /engagements/{eid}/memory-status returns both the derivation version and the source's current version in one call. The engine gap for the Manifestation room is small and implicates no migration.
B-29 — resized in shape, not in count. 83 sites confirmed, across 37 files not 36. "It is one seam" is wrong: three raw-SQL paths bypass append_event, two of which need one-line repairs no seam change reaches. The three personal_engagement.py sites are confirmed correct — the prior position stands and this brief's own doubt about them is withdrawn.
Recorded so they are auditable, not queued. Per charter §7 the Operator may overturn any of these at cadence; the cost of reversal is noted.
D-1 — B-29 takes seam option B: append_event stamps the field itself before serialising.
Reasoning. Both options are correct and neither can break a consumer, since nothing reads the field and nothing hashes it. Option A touches all 83 sites, three of which are the same Provenance(...) expression as B-25's fix on consecutive lines — it guarantees a line-level collision and holds the engine for a large mechanical diff. Option B touches one file B-25 never opens. Under the one-engine-front ruling, B releases the engine fastest.
Consequence, forced. wasGeneratedBy is required with no default (memory/base.py:150, read directly). Option B therefore cannot delete the 83 dead stampers without first making the field optional. B's honest shape is three steps: the seam now; B-25 unblocked; then the sweep with the declaration change, by which time it collides with nothing.
Reversal cost. One CR redraft before build starts. After build, a revert plus redraft.
D-2 — the bookkeeping pass runs before the B-29 change request is drafted. Reasoning. Six documents carry positions the read overturned. A change request drafted against an uncorrected record inherits them. Charter §2 R-3 pre-authorizes correction notes filed beside what they correct. Reversal cost. None; ordering only.
D-3 — the two backfill one-line repairs ride with B-29 regardless of seam option.
engagement/wasderivedfrom_backfill.py:75 and engagement/redirect_edge_backfill.py:148. Neither calls append_event, so no seam change reaches them.
B-29 lands before FORAY integration opens. foray/reserved_emit.py:26 is a no-op today and the emit payload carries only event_id and anchor_priority — provenance is not in it and nothing hashes the JSONB columns. When integration opens, whatever is in payload and provenance at that moment becomes the anchored composition. Fabricated provenance inside an anchored history is materially worse than fabricated provenance in an unanchored one.
B-29 lands before B-25 and before CR-B. Unchanged from the Operator's 2026-07-31 ruling, now with line-level evidence at three sites.
Nothing. Both repositories clean and pushed. No session in flight.
In order. All within charter §2 and §3; none requires the Operator.
api/routers/assertions.py:405); walk-audit report (W-16 struck); completion scoping note (§5 sequencing diagram superseded, CR-B loses W-16); manifest (tag position at c4014d6, partial numeric refresh, alembic head 0102); build list to v0.9 (B-27 done, B-29 shaped, new item for the deps.py:271 dependency trap).RoomView.tsx vocabulary wall.Per charter §5: each entry carries the question, the default with its reasoning, what it blocks, and what proceeds regardless. Silence is never consent — an unanswered entry stays open and its dependents stay parked. Everything not blocked continues.
| # | Question | Default | Blocks | Proceeds regardless | |---|---|---|---|---| | Q-1 | B-16 — seed v0.13. Drafting was authorized 2026-07-30. Committing a seed version is an Operator act (charter F-3). The draft awaits your reading. | Commit as drafted once read. | Seed v0.13 only. | Everything. |
That is the whole queue. One entry, and it was already known.
Batched Operator acts pending: none. No deployment is due (F-1), no passkey or presence ceremony is outstanding on current work (F-2), no external communication is queued (F-5).
Followed. R-5 inspection run, read-only, evidence-cited. R-1 filing conventions: explicit paths, versioned filenames, siblings not overwrites, destination checked against the repository's existing layout rather than assumed. Two-role discipline held — the drafting session did not execute its own brief.
Breached, and corrected here. §2 R-1 converts halt-before-push to halt-on-anomaly for record filing; this session halted before both pushes and asked the Operator to run them. §5 requires forks to file to this queue rather than interrupt; four decisions were put to the Operator directly. §7 requires every session to append its outcome to a status brief; no such brief existed to append to. The third breach caused the first two.
Standing correction. Record filing proceeds and pushes under R-1. Decisions inside an authorized build item are the session's, recorded in Section 3 and auditable. Only charter §4 forks reach Section 7.
DUNIN7 — Done In Seven LLC — Miami, Florida DUNIN7 — status brief — v0.1 — 2026-07-31 The document the charter required and did not have. One queue entry.