Version. 0.1 Date. 2026-07-29 Status. Correction note. Filed beside the OVA reach-enforcement arc per the corrections-preserved discipline: nothing in the arc is rewritten; this note states what was stale, what survives, and where each correction lands. Author. Claude.ai. Operator: Marvin Percival. What this corrects. The reach-enforcement arc of 2026-07-28 — the scoping handoff, the Step 0 pair, the scoping note, the Slice 1 drafting handoff, CR-2026-157, and manifest entries 119–120 — named OVA in the authorization seat and framed deferred Slices 2–3 around an access-control list. Both were stale at drafting time: Decision J1 (established June 2026, carried in the record and in a July 18 inspection) placed GRANTHA in the authorization seat, with the grant as its sole primitive — no access-control list, no group object, holder-set never readable — and GRANTHA consuming OVA underneath for blind verification, OVA's standalone role unstated. The drafting session's memory predated Decision J1 and the project's knowledge files carry no GRANTHA material; the gap surfaced 2026-07-28 during the stack-diagram work and was verified against the session record.
CR-2026-157's mechanism survives essentially whole. Its credential is issued by an authority, scoped to one engagement and one action, carries expiry and revocation, and is claimed by binding a holder — that is a grant, not an access-control-list entry. The engine authorizer seam it builds is the interim implementation the integration strategy always intended to swap out; the swap target is GRANTHA rather than OVA, and the seam's design — callers unchanged at swap — absorbs the substitution without code consequence. The arc's central resolution (the membership predicate as the fence; contribution authorization for non-members as the build) is unaffected: it never depended on which protocol holds the seat.
The Step 0 evidence survives untouched — it describes the engine, which has no protocol-side authorization at all yet.
The drift had one cause: a settled decision (J1) lived in the record and in past sessions but not in the drafting session's context, and nothing forced a check. The correction pattern that caught it — an unfamiliar term halting the work until searched — is the vocabulary-deference rule doing its job one arc too late. The durable fix is knowledge-base hygiene: the stack-diagram document and this note entering the project's context closes the specific gap; the general residue (project files predating June's protocol decisions) is named for the Operator's next knowledge-refresh pass.
DUNIN7 — Done In Seven LLC — Miami, Florida Loomworks — reach-enforcement arc: GRANTHA correction note — v0.1 — 2026-07-29