Document: current-status-manifest-v0_74-amendment-v0_1
Version: v0.1
Date: 2026-07-28
Recipe: Apply these splices to current-status-manifest-v0_73.md and save the result as current-status-manifest-v0_74.md (add-new-file sibling — never git mv; v0.73 stays a standing sibling, byte-for-byte untouched). Update header/footer/version to v0.74 throughout.
What v0.74 records: the OVA reach-enforcement scoping arc ran to completion in the same session that commissioned it — Step 0 (six verifications, engine 1aac815, zero drift from the venture-diligence inspection), the scoping note resolving the central question by inversion, three Operator decisions settled (D1–D3), and the Slice 1 change-request drafting handoff filed. The v0.73 §5 item that recorded the arc as commissioned-not-run is superseded in part, with the supersession appended not overwritten. Engine untouched; record main advanced one commit to 4e2299d.
Replace the H1:
# Loomworks Current-Status Manifest — v0.73
with:
# Loomworks Current-Status Manifest — v0.74
And Version: 0.73 → Version: 0.74 (date stays 2026-07-28 — same day).
Locate the v0.73 Status paragraph (begins "v0.73 (2026-07-28): the venture-diligence vertical arc..."). Append immediately after it:**
> v0.74 (2026-07-28, later same session): the OVA reach-enforcement scoping arc RAN — commissioned, Step-0-verified, and resolved in one session; Slice 1 is ready for change-request drafting. Step 0 (six verifications at engine 1aac815, zero drift — this report and the venture-diligence report describe an identical tree): V1 the declared access-mode seam BREAKS (no access-mode/ACL/reach element exists anywhere in schema or migrations; visibility is a false friend by its own migration's "Schema-only — no behavior" documentation, read at two dashboard lines); V2 all 63 engagement-scoped reads converge on the membership-existence predicate with no bypass found; V3 held-as-admission BREAKS (the commit check never compares committer to contributor — a member self-admits; "trusted core" appears nowhere in any authorization sense); V4 the OVA seam PARTIALLY HOLDS (Phase 45's verify_companion_authorization is delegation-fixed; the right ancestor is _alpha_authorizer_stub at credit/cross_engagement_memory.py:65-85 — right shape, wrong scope); V5 attribution-membership coupling HOLDS (embedded ActorRef, snapshotted display name, memory_events FKs only the engagement — non-member attribution is substrate-feasible today); V6 engagement is the only Memory scope in schema. The scoping note resolves the central question by inversion: the membership predicate is not the blocker, it is the fence — a contributor who is never a member is excluded from all 63 reads by the predicate that already holds, and their contribution stays fully attributed. The build is a non-member contribution pathway, not a read-side rework; the admission gate assembles free (a non-member structurally cannot reach the commit transition). Operator decisions settled (2026-07-28): D1 candidate C confirmed (contribution authorization for non-members; candidate A's read-side rework deferred to Slice 3 with the three-enforcement-paths consolidation constraint recorded — no middleware exists; resolver deps, in-body verify_project_membership, and dashboard CTEs are three separate paths, and a resolver-only check would miss the seven orchestration routes); D2 the two seed findings (held-gate extension to engagements; "seam is in place" as posture until Slice 2) ride the queued seed v0.13 alongside provenance-threads; D3 Slice 1 holds to the pathway alone (no declaration, no ACL, no read changes). Slice 1 CR drafting handoff filed (cr-drafting-handoffs/loomworks-ova-slice-1-cr-drafting-handoff-v0_1): five surfaces (Option E authorizer generalized from the stub; credential issuance; credential-gated non-member entry writing held assertions; own-submission surface; FORAY anchoring), eight Step 0 pre-flight items, one design point resolved at drafting (person-required lean, composing with seed v0.12's recorded account-creation-invitation lean; halt-to-Operator if sign-up mechanism work threatens the slice). Consequence: the deal vertical unblocks at Slice 1, not Slice 3 — walkthrough v0.4 and deal seed v0.3 trigger on the Slice 1 CR landing; the Appendix A investigation is unblocked for drafting now. Arc filed into existing type directories (inspection-briefs/, scoping-notes/, cr-drafting-handoffs/, alongside the session-handoffs/ parent) — the graph-stage-2 twin was decisive precedent; arc-grouped directories remain for large multi-document bodies. Record main 5587149-era → 4e2299d (one commit, pushed). Engine untouched. See Entry 120.
Entry 119 ends before ### 4.A Carryover from v0.41. Insert after Entry 119's closing text and before ### 4.A:
### Entry 120 — OVA reach-enforcement scoping arc: run and resolved by inversion (new v0.74; 2026-07-28, later same session)
The arc Entry 119 recorded as commissioned ran to completion the same day — the fastest commission-to-resolution scoping arc on record, and the resolution reverses the framing the commission carried.
**Step 0 (engine `1aac815`, zero drift; report at `inspection-briefs/loomworks-ova-reach-enforcement-step-0-report-v0_1.md`).** Six verifications, none repeating the venture-diligence V1 evidence. V1 declared-seam BREAKS: `access_mode`/`acl`/`reach` zero hits across src/ and migrations/; `visibility` (migration 0030, "Schema-only — no behavior in Phase 14") is a false friend read at exactly two dashboard lines; seed v0.12's "the seam is in place" is posture. V2 descriptive: 63 engagement-scoped reads, all converging on membership existence, no bypass found — but enforcement runs through three separate code paths (resolver dependencies, in-body `verify_project_membership`, dashboard SQL CTEs) with no auth middleware; a resolver-only reach check would silently miss the seven orchestration routes where partner-facing reads live. V3 held-as-admission BREAKS: `commit_assertion` checks only not-agent + state-held, never committer-vs-contributor; a contributor-designated member drafts and self-admits; held today is a save-before-submit cycle reusing the seed's word. V4 PARTIALLY HOLDS: Phase 45's `verify_companion_authorization` is a genuine seam but delegation-fixed; `_alpha_authorizer_stub` (`credit/cross_engagement_memory.py:65-85`, `(requesting_person, requesting_engagement, target_engagement) → bool`, deny path written, unconditionally true, one caller) is the right ancestor — generalizing it beats inventing an interface. V5 HOLDS: attribution is an embedded ActorRef with snapshotted display_name; `memory_events` has exactly one FK (engagements.id); no attribution path targets memberships. V6: engagement is the only Memory scope in schema; workspaces are person-owned grouping, not Memory scope.
**The inversion (scoping note at `scoping-notes/loomworks-ova-reach-enforcement-scoping-note-v0_1.{md,html}`).** V5 + V2 compose: a person who contributes without ever holding a membership gets contribute-without-read from the substrate as it stands — the two-rung ladder the venture-diligence inspection read as the blocker is the fence. The missing piece is not keeping non-members out of reads; it is letting non-members in to contribution. Candidate C (participation-without-membership) is confirmed as delivering exactly, not under-delivering: both commercial motions (deal vertical: externals contribute, deal team reads; Appendix A: target's people contribute, investor reads) are the same shape and both are served. The admission gate assembles free — non-members structurally cannot reach the commit transition, so held-until-admitted-by-the-deal-team falls out of composition with no new admission logic. The member self-admission looseness (V3) is accepted semantics for trusted-core members, named as a residue for future shared-scope/domain work where trusted-core-proper is the real subject.
**Slice structure.** Slice 1 (now): non-member contribution pathway — Option E authorizer generalized from the stub with the non-member contribution question as the OVA contract's first real caller (deliberate: it exercises issuance, scoping, expiry, revocation — the capability semantics OVA-proper answers); credential issuance with FORAY-anchored events; credential-gated entry writing held assertions with embedded-ActorRef attribution; own-submission surface (credential-gated, touches none of the 63 reads); zero read-side changes; substrate-chokepoint discipline on the write path. Slice 2 (deferred, no consumer): the access-mode declaration + ACL structure, making the seed's sentence true. Slice 3 (deferred, design constraint recorded): reach enforcement proper for member/cross-engagement restriction — consolidate the three enforcement paths into one authorizer consultation before routing any guarantee through it. Authorizer contract written scope-shaped per V6 so the N-scope model slots in without a second contract.
**Operator decisions (2026-07-28).** D1 candidate C confirmed. D2 seed riders: held-gate-extension-to-engagements + seam-is-posture both ride the queued seed v0.13 alongside provenance-threads — one amendment event; this arc's CRs do not touch the seed. D3 Slice 1 holds to the pathway alone.
**Downstream triggers, corrected.** Entry 119 recorded the OVA arc as gating deal walkthrough v0.4 — that gate is now precisely located: v0.4 and deal seed v0.3 trigger on the Slice 1 CR landing, not on reach enforcement proper. The Appendix A investigation (FORAY-as-term-sheet-condition) is unblocked for drafting now — the enforcement shape it needed to cite exists as the scoping note §§1–4. The fund record vertical was never blocked.
**Filing.** Type directories over a new arc directory — CC's placement investigation found the graph-stage-2 arc (Step 0 pair + scoping note + CR) split across inspection-briefs/ / scoping-notes/ / change-requests/ as decisive structural precedent, with inspection-briefs/ already holding reports alongside briefs and the arc's own parent handoff already typed into session-handoffs/. Arc-grouped directories (phases/, substrate/cleanup/, verticals/venture-diligence/) remain the pattern for large multi-document bodies. Record commit `4e2299d` (pushed; six files).
**Next artifact.** The Slice 1 change request, drafted in a fresh session from `cr-drafting-handoffs/loomworks-ova-slice-1-cr-drafting-handoff-v0_1` — CR number assigned from `docs/phase-crs/` at drafting; eight Step 0 pre-flight items; the person-required-vs-credential-only design point resolved against claim-token evidence with a halt-to-Operator if sign-up mechanism work threatens the slice boundary.
Locate the §5 item beginning "OVA reach-enforcement scoping arc — commissioned, not yet run (2026-07-28)." Append to the end of that item's paragraph:
> Updated for v0.74 (2026-07-28, later same session): the arc RAN and resolved. The central question is answered by inversion (the membership predicate is the fence; the build is a non-member contribution pathway — Entry 120); D1–D3 settled; the gate on deal walkthrough v0.4 relocates from "the arc" to "the Slice 1 CR landing." What remains open: the Slice 1 CR drafting session (handoff filed at cr-drafting-handoffs/), Slice 2 (declaration — no consumer, unscheduled), Slice 3 (reach enforcement proper — waits on domain layer or a restricted-engagement need; three-paths consolidation constraint recorded), and the seed v0.13 riders per D2.
Locate the v0.73 record-authority line in §1 ("Updated for v0.73 (2026-07-28): record main advanced to 5587149..."). Append after it, per the same pattern:
> Updated for v0.74 (2026-07-28, later same session): record main advanced to 4e2299d (one commit — the OVA scoping arc set, six files across inspection-briefs/, scoping-notes/, cr-drafting-handoffs/). Engine and Operator Layer unchanged.
Insert above the - v0.73 changelog entry:
- **v0.74** (2026-07-28, later same session): **The OVA reach-enforcement scoping arc ran to completion — Step 0 (six verifications at `1aac815`, zero drift), scoping note resolving the central question by inversion (the membership predicate is the fence; the build is a non-member contribution pathway; the admission gate assembles free), D1–D3 settled (candidate C; seed v0.13 riders; Slice 1 pathway-only), Slice 1 CR drafting handoff filed.** Key evidence: no declared access-mode element exists (seed's "seam is in place" is posture — Slice 2 makes it true); 63 reads converge on membership with no bypass but across three enforcement paths with no middleware (Slice 3 consolidation constraint); held is save-before-submit, not an admission gate (trusted-core-proper deferred to shared-scope work); `_alpha_authorizer_stub` is the Option E ancestor; attribution is membership-free (embedded ActorRef, one FK). Deal vertical unblock relocates to the Slice 1 CR landing; Appendix A investigation unblocked for drafting. Arc filed into type directories per the graph-stage-2 precedent. Adds §3 Entry 120; §5 OVA-item update (appended, not overwritten); §1 record `main` → `4e2299d`. Otherwise carries v0.73 forward.
Replace:
*Loomworks Current-Status Manifest — v0.73 — 2026-07-28*
with:
*Loomworks Current-Status Manifest — v0.74 — 2026-07-28*
main 4e2299d.1aac815 and 4e2299d verbatim; the "63 reads" figure and the stub path credit/cross_engagement_memory.py:65-85 match the Step 0 report verbatim..md-only.
DUNIN7 — Done In Seven LLC — Miami, Florida
Current-Status Manifest v0.74 — amendment instructions — v0.1 — 2026-07-28
Splice-list against v0.73: the OVA reach-enforcement scoping arc ran and resolved same-session — inversion resolution (membership predicate as fence; non-member contribution pathway as the build), D1–D3 settled, Slice 1 CR drafting handoff filed, deal-vertical gate relocated to the Slice 1 CR landing. §5 correction appended not overwritten. Record main → 4e2299d; engine untouched. Add-new-file sibling; v0.73 untouched.