Version. 0.4
Date. 2026-07-31
Charter. standing-notes/dunin7-standing-authorization-charter-v0_1, ratified 2026-07-30.
Author. Claude.ai (drafting session). Operator: Marvin Percival.
Supersedes. v0.3, drafted and never filed — halted at pre-flight. v0.2 at record 40571cf and v0.1 at 602bd9c stand as siblings, unaltered. The record holds v0.1, v0.2 and v0.4; v0.3 is deliberately absent, not lost.
Changes from v0.2. Records everything filed since, closes the manifest v0.77 application, and replaces the running tally of drafting-session imprecisions with a diagnosis and a rule.
Why v0.3 was halted, and what v0.4 changes structurally. v0.3 carried a hand-written table of what landed at which commit. One row was wrong — it credited a commit with the manifest amendment instructions, which that commit did not contain; the instructions were unfiled at that moment and entered the record only with the application. The error traces back one step further, to a filing block that asked for two documents where one landed, and an accurate report saying one file that the drafting session did not reconcile against its own request. v0.4 does not correct the table. It removes the drafting session's ability to write one. §1 is now generated by the executing session from git log at filing time — because a drafting session cannot know what landed, only what it asked for, and at v0.3 those diverged silently.
This section is generated, not written. A drafting session has no reliable access to what actually landed — it has only its memory of what it asked for, and at v0.3 those diverged: the table credited c1a5908 with the manifest amendment instructions, which that commit did not contain. From v0.4 the executing session produces this section from git log at filing time.
| Commit | Subject | Files changed |
|---|---|---|
| 7f49eba | completion scoping note v0.1 — the ordered plan for B-5 through B-9, the governing rule, and the acceptance gate. | 2 — loomworks-completion-scoping-note-v0_1.html, loomworks-completion-scoping-note-v0_1.md |
| ba37528 | B-25 sized at eleven sites; build list v0.8; completion scoping note v0.2 — B-27, B-28, B-29 opened | 6 — dunin7-build-list-v0_8.html, dunin7-build-list-v0_8.md, loomworks-b25-sizing-sweeps-findings-v0_1.md, loomworks-b25-sizing-sweeps-inspection-brief-v0_1.md, loomworks-completion-scoping-note-v0_2.html, loomworks-completion-scoping-note-v0_2.md |
| 403790a | serve inspection-briefs — the section was never in the builder's list | 1 — build_site.py |
| 8d79e91 | file combined engine inspection brief — B-29 seam, B-27 status, B-5 Manifestation contract | 1 — loomworks-b29-b27-b5-engine-inspection-brief-v0_1.md |
| e037a37 | B-27 resolved; W-16 overturned; the seam is not one seam — combined engine inspection findings v0.1 | 1 — loomworks-b29-b27-b5-engine-inspection-findings-v0_1.md |
| 602bd9c | file status brief v0.1 — the charter section 7 mechanism, standing up | 1 — dunin7-status-brief-v0_1.md |
| 40571cf | bookkeeping pass: build list v0.9, status brief v0.2, inspection corrections note v0.1 | 3 — dunin7-build-list-v0_9.md, dunin7-status-brief-v0_2.md, loomworks-inspection-corrections-note-v0_1.md |
| b36a676 | file CR-2026-159 v0.1 — B-29, the provenance seam | 1 — cr-2026-159-provenance-seam-v0_1.md |
| d697187 | file CR-2026-159 v0.2 — closes the backfill-equivalence determination; corrects D-5 | 1 — cr-2026-159-provenance-seam-v0_2.md |
| 9c1766f | file CR-2026-159 v0.3 — remove the anchor count; flag the shared :142 as coincidence | 1 — cr-2026-159-provenance-seam-v0_3.md |
| c1a5908 | file Operator Layer inspection brief — change request A Step 0 | 1 — loomworks-operator-layer-cr-a-step-0-brief-v0_1.md |
| d662469 | file Operator Layer CR-A Step 0 brief v0.3 — remove the count from both places in the discipline clause | 1 — loomworks-operator-layer-cr-a-step-0-brief-v0_3.md |
| fa2204a | apply manifest v0.77 — first day under the charter; W-16 struck; partial numeric refresh | 2 — current-status-manifest-v0_77-amendment-v0_1.md, current-status-manifest-v0_77.md |
Engine (loomworks-engine). main at a317051, no commit on 2026-07-31. Working tree carries M uv.lock unstaged — present before the day began, left as found.
Operator Layer (loomworks). main at 99f7f64, working tree clean. Untouched this window.
stele. main at 689de41, tag v0.4.0 on HEAD, working tree clean.
What the drafting session can assert, because it is reported rather than recalled: no engine work has been built in this window. The engine has taken no commit, no branch and no push all day.
The manifest v0.77 amendment is applied. Eight splices, v0_76 → v0_77, all seven checklist items passing, v0_76 unmodified. The highest manifest present is v0.77. (Closed at v0.4; v0.3 recorded it as outstanding and was correct when written.)
Two things the application carried in, both owed to the next manifest bump.
An internal inconsistency, in the document that names ornamental counts as the defect. Splice 4's second methodology candidate says "with four instances" and enumerates four. Entry 130 says the two-role discipline "caught all five." Same class, two counts, now in the record at v0.77. The next bump removes both counts rather than reconciling them — neither number is a finding, and the candidate reads correctly with no tally at all.
The amendment instructions were not in the record when this brief's predecessor claimed they were. They existed only in ~/Downloads until the executing session filed them alongside the application. The gap traces to a filing block that asked for two documents where one landed, and a report that said one file which the drafting session did not reconcile against the request. Recorded because it is the root cause of v0.3's wrong attribution, not as a separate defect.
Auditable, not queued. Overturnable at cadence; reversal cost noted.
D-1 — B-29 takes seam option B. Unchanged from v0.2. append_event stamps the field before serialising; the 83 sites are untouched; two backfill bypasses get one line each. Reversal cost: one CR redraft, and the CR is unexecuted.
D-2 — bookkeeping before the change request. Executed. Closed.
D-3 — the two backfill repairs ride with B-29 regardless of seam option. Unchanged.
D-4 — no historical backfill of the fabricated field. The damage is structurally knowable, so the remediation is one recorded statement in CR-2026-159's implementation notes rather than a per-record pass.
D-5 — the Operator Layer brief went before the completion scoping note, reversing the order stated in v0.2 §6. B-5 is front of the queue and change request A cannot be drafted without its remaining Step 0 items; the corrections note is filed and authoritative, so the scoping note's absorption is tidying rather than a blocker. Reversal cost: none, ordering only.
D-6 — the CR-A vocabulary-wall question resolves without an Operator ruling. The completion scoping note raised the RoomView.tsx wall as a possible conflict with the seed's plain-terms discipline, to be settled by the Operator if the wall proved deliberate at the level of the methodology nouns. It is not. src/lib/room-labels.ts holds Memory, Manifestation, Shaping and Rendering as operator-surface labels in one sanctioned module precisely so the wall can forbid engine wire tokens everywhere else. The wall and the seed agree. What remains is verifying that the enforcement mechanism matches the stated intent, which is question two of the Operator Layer brief. This removes a queue entry rather than adding one.
Unchanged from v0.2. B-29 before FORAY integration opens — the emitter is a no-op today and nothing hashes the JSONB columns, so after integration the fabricated value would sit inside the anchored composition. B-29 before B-25 and before the completion arc's engine rider — at three sites the two items are the two arguments of one expression on consecutive lines.
Nothing. All repositories clean and pushed. No session in flight.
/Users/dunin7/loomworks. Read-only.| # | Question | Default | Blocks | Proceeds regardless | |---|---|---|---|---| | Q-1 | B-16 — seed v0.13. Drafting 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. |
One entry, unchanged across all three versions of this brief.
Batched Operator acts pending: none. No deployment due (F-1) — CR-2026-159 is filed but unbuilt, and its restart comes after Checkpoint B. No passkey ceremony outstanding (F-2). No external communication queued (F-5).
A-6 — name resolution failed on the host (2026-07-31). github.com would not resolve for ssh, curl or ping while nslookup answered from the configured resolver — a half-up VPN or split-DNS path. One commit sat local and unpushed across three attempts. Handled correctly: the executing session reported the boundary and did not paper over it, and did not stack a second commit on top. Resolved when the network returned; the commit that landed was the one audited before the failure, unchanged.
One halt at pre-flight, correctly judged. The Operator Layer brief v0.2 was caught before filing: its changes-line claimed a count had been removed while the count still stood elsewhere in the same section. The executing session halted rather than filing-and-reporting, on the reasoning that a document making false claims about itself belongs in the record less than a round trip costs. v0.2 was therefore never filed — the record holds v0.1 and v0.3 with a deliberate gap, noted in v0.3's header.
v0.2 §8 recorded these as a growing count. A count is the wrong instrument, and the last of them was itself a miscount, so this section states the pattern instead.
Every one was ornament, not analysis. No underlying reasoning failed. In each case a specific was added for rhetorical weight where the work needed none, and therefore where none had been verified: a line number that was never read, a commit identifier gestured at rather than looked up, a source characterised from memory rather than opened, a count of anchors standing beside the anchors themselves, a tally that split one instance into two.
All were caught by the executing session. None reached the work. That is the two-role discipline functioning exactly as designed — but each cost a round trip, and the Operator's time was spent on rounds that produced no build.
The test now in force: no number, identifier or characterisation in prose unless it is itself the finding. "83 sites across 37 files" is a finding and stays. "Six positions, five numerals" is a finding, because it prevents a skipped check, and stays. "Five imprecisions" is ornament and goes.
Two related candidates go to the manifest's §2.D with the v0.77 amendment: state only what you have read back, as a session discipline rather than only a surface one, at three instances; and do not state a specific the work does not need, at four.
In force and working. R-1 filing proceeds and pushes on clean pre-flight; the halt ceremony is gone and halt-on-anomaly has fired twice — once on A-6, once on a document's self-contradiction — both correctly. R-3 correction notes filed beside what they correct; the manifest bump drafted as splice instructions per the recipe. R-5 inspections read-only throughout. §1's two-role discipline held: no session executed what it drafted, and it caught every drafting imprecision.
Recorded at v0.1 and standing. The charter was ratified 2026-07-30 and its §7 status brief did not exist until 2026-07-31, so for one day forks defaulted back to interrupting the Operator. The general lesson: a governance document that replaces a behaviour must have its replacement built before the old behaviour stops being available, or the old behaviour returns by default.
DUNIN7 — Done In Seven LLC — Miami, Florida DUNIN7 — status brief — v0.4 — 2026-07-31 One queue entry. Section 1 generated, not written. No engine work built in this window.