Loomworks C5 scoping note v0.2 → v0.3 — amendment instructions — v0.1

Version. 0.1 Date. 2026-08-06 Author. Claude.ai (drafting session). Operator: Marvin Percival. Applies to. scoping-notes/loomworks-c5-scoping-note-domain-reference-model-v0_2.md. Produces. loomworks-c5-scoping-note-domain-reference-model-v0_3.md. v0.2 and v0.1 are not edited and stand as siblings.

Why v0.2 was a partial fix, and whose error that was. v0.2 corrected one line, because the amendment that produced it was scoped from a single quoted line in a correction note rather than from reading the document. The document carries the superseded mechanism in at least seven further places. A corrected line in a document that says the old thing six more times is worse than an uncorrected one, because it reads as done.

And a second staleness, found while sweeping for the first. §3.4 recommends that the contribution-authority model land as a seed v0.11 amendment before C5 can specify under it. That amendment landed. The seed has carried the write-access axis since v0.11 and is now at v0.14. The note's central gate is satisfied and the note does not know it — which matters more to anyone picking up C5 than the vocabulary does.

Splice 1 — Version block

Replace Version: 0.2 with Version: 0.3, Document: loomworks-c5-scoping-note-domain-reference-model-v0_2 with …-v0_3, and insert after the existing v0.2 amendment note:

> Amendment note (v0.3). v0.2 corrected one occurrence of the superseded access mechanism and the document carried seven more. All are corrected here: the plain-language summary, the settled-commitments list, the manifest orientation, both Companion-surfacing disciplines, the contribution-axis finding, and the out-of-scope section. Restriction is by grant, with GRANTHA governing; OVA sits beneath it, and how either works is its own specification's to govern. Separately, §3.4's gate is satisfied — it recommends a seed v0.11 amendment for the contribution-authority model, and that amendment landed; the seed has carried the write-access axis since v0.11 and is now at v0.14. The seven specification items, the contribution-authority finding, and every recommendation are otherwise unchanged.

Splice 2 — Plain-language summary, the settled commitments

Replace:

> the two read-access modes (open by default; restricted via OVA)

With:

> the two read-access modes (open by default; restricted by grant)

Splice 3 — Plain-language summary, out of scope

Replace:

> Out of scope: OVA enforcement itself (parked — Kaspa vProgs not ready);

With:

> Out of scope: reach enforcement itself (parked);

**[EXECUTING SESSION: the Kaspa vProgs clause is removed rather than reassigned. It named what blocked OVA's readiness. What blocks GRANTHA enforcement is unread by this drafting session and must not be asserted. If the removal leaves the sentence reading oddly, report it rather than substituting a reason.]**

Splice 4 — §1.1, commitment 4

Replace:

> While OVA is not enforcing, every scope is effectively open, but the seam is declared.

With:

> While enforcement is not built, every scope is effectively open, but the seam is declared.

Splice 5 — §1.3, the manifest residues

Replace:

> OVA parked.

With:

> reach enforcement parked.

Splice 6 — §2.6, discipline 3

Replace:

> The Companion surfaces open scopes freely and restricted scopes only to Operators whose OVA check passes — never surfacing a restricted scope as available to an Operator who cannot reach it ("only show what is available"). Permissive until OVA enforces; the seam is there now.

With:

> The Companion surfaces open scopes freely and restricted scopes only to Operators whose authorization check passes — never surfacing a restricted scope as available to an Operator who cannot reach it ("only show what is available"). Permissive until enforcement is built; the seam is there now.

Splice 7 — §3.1, the two-axes framing

Replace:

> The seed's two access modes (open / restricted via OVA — §1.1.4) govern who may reach a scope — read access.

With:

> The seed's two access modes (open / restricted by grant — §1.1.4) govern who may reach a scope — read access.

And replace:

> - Reach (read) — open-by-default / restricted-via-OVA. Settled in seed v0.10.

With:

> - Reach (read) — open-by-default / restricted-by-grant. Settled in seed v0.10; mechanism corrected by Decision J1 and absorbed at seed v0.13.

Splice 8 — §5, out of scope

Replace:

> - OVA enforcement itself — parked; Kaspa vProgs not ready. The reach axis is seam-declared, not enforced. C5 declares the seam; it does not build OVA.

With:

> - Reach enforcement itself — parked. The reach axis is seam-declared, not enforced. C5 declares the seam; it does not build the enforcement.

[EXECUTING SESSION: same instruction as Splice 3 — the Kaspa vProgs clause goes rather than being reassigned to GRANTHA, because what blocks GRANTHA enforcement is unread.]

Splice 9 — §3.4 and §6, the satisfied gate

Append to §3.4, after its numbered list:

> [Amended v0.3] This gate is satisfied. The seed v0.11 amendment this section recommends landed, and the seed has carried the write-access axis — the trusted core writing directly, outside contributions held until admitted — since that version. The seed is now at v0.14. So C5's first change request is no longer waiting on a seed amendment; it specifies under a seed that already carries the axis. (The v0.11 language uses "trusted core" where this note proposes "Domain Steward"; whether those are the same role under two names, or whether the Steward is a narrower thing, is a real question this note did not have to answer and the change request now does.)

And in §6, replace decision 2:

> 2. Decide the seed v0.11 path (§3.4): does the contribution-authority model proceed as a seed v0.11 amendment now, or hold? C5's first CR depends on this — C5 specifies under the amended seed.

With:

> 2. ~~Decide the seed v0.11 path~~ — satisfied. The amendment landed; the seed carries the write-access axis and is now at v0.14. What replaces this decision: whether the seed's trusted core and this note's Domain Steward name the same role. (See §3.4's amendment note.)

Verification checklist after applying

1. Version block, document line and footer all read v0.3.
2. …-v0_2.md and …-v0_1.md are unmodified.
3. No live sentence names OVA as the authorization seat, an access-control list as the mechanism, or OVA as the thing that enforces. Sweep for OVA, ACL, access-control list. Every remaining occurrence must be inside an amendment note. Report the count you find — this document expects the sweep to come back with amendment-note occurrences only.
4. No Kaspa vProgs clause survives, and no substitute reason for enforcement being parked has been invented.
5. The seven specification items at §2 are otherwise unchanged, including their proposed shapes and their CR must decide lines. Diff to confirm.
6. §3's contribution-authority finding is unchanged except for the appended note at §3.4.
7. Count the corrected occurrences yourself. This document specifies seven splices covering the mechanism — Splices 2 through 8 — plus a version block and one covering the satisfied gate, nine in all. If you find a mechanism occurrence no splice reaches, that is a miss and this document is wrong again.

DUNIN7 — Done In Seven LLC — Miami, Florida Loomworks C5 scoping note v0.2 → v0.3 — amendment instructions — v0.1 — 2026-08-06 v0.2 corrected one line in a document that said the same thing seven more times. This is what reading it first would have produced.