Document: current-status-manifest-v0_73-amendment-v0_1
Version: v0.1
Date: 2026-07-28
Recipe: Apply these splices to current-status-manifest-v0_72.md and save the result as current-status-manifest-v0_73.md (add-new-file sibling — never git mv; v0.72 stays a standing sibling, byte-for-byte untouched). Update header/footer/version to v0.73 throughout. If CC has already drafted its own v0.73 from the Operator's direct instruction, discard that draft and apply this document instead, so the manifest content is authored on the Claude.ai side and the application stays mechanical per the two-role discipline.
What v0.73 records: the venture-diligence vertical arc — Claude.ai-side document work plus one read-only engine inspection; no engine or Operator Layer code changed. An 18-file vertical set filed under a new verticals/venture-diligence/ record area across four pushed commits; a five-verification engine inspection whose verdicts corrected two commercial claims; the Operator's two-vertical structure decision (deal vertical + fund record vertical, related by reference not containment); queued-directions bumped to v0.30 (§18.2 recall priority raised, no-live-recall-demonstration rule recorded); and the OVA reach-enforcement scoping arc commissioned with its handoff filed.
Replace the H1:
# Loomworks Current-Status Manifest — v0.72
with:
# Loomworks Current-Status Manifest — v0.73
And Version: 0.72 → Version: 0.73; Date: 2026-06-28 → Date: 2026-07-28.
The Status block's v0.72-era text ends with the v0.71 create-stage sentence "...See Entry 117 and the §5/§2 updates." and the v0.72 addition inserted before any correction lines. Append at the end of the Status block's running additions, before any Correction line if one exists, this paragraph:**
> v0.73 (2026-07-28): the venture-diligence vertical arc — the first vertical filed as a record area, grounded by engine inspection, restructured by Operator decision into a two-vertical pair. Claude.ai-side document work plus one read-only engine inspection; engine main untouched (inspection read at 1aac815), Operator Layer untouched. A new record area verticals/venture-diligence/ holds 18 files: the deal walkthrough at v0.1/v0.2/v0.3, the deal candidate-seed template at v0.1/v0.2, the fund record candidate-seed template at v0.1, the two-vertical structure note, the pain-points mapping, and the CC inspection brief + report. The inspection (V1–V5) returned two load-bearing corrections: V1 BREAKS — no read endpoint consults designations; membership alone grants read (deps.py:1160-1179) — reframed from a designation gap to the engine-side truth of seed v0.12's "OVA not yet enforcing," and the OVA reach-enforcement scoping arc is commissioned (session-handoffs/loomworks-ova-reach-enforcement-scoping-handoff-v0_1, central question: can reach be withheld below membership); V5 — recall is wholesale (_PAST_INPUT_LIMIT = 50, no search index has ever existed, silent failure on the ask-about-something-early probe) — folded into queued-directions v0.30 §18.2 with priority raised and a standing conduct rule recorded: no live recall demonstration in front of a prospect until it lands. V2/V3 sharpened the ingestion gap (two upload pathways with inconsistent rules; spreadsheet/presentation absent with no extraction skill — the cap table, the model, the deck); V4 found the cross-deal gap smaller than assumed (workspaces exist and filter; the dashboard routes lack only the parameter — bears on the pending aggregating-scope decision). The Operator's two-vertical decision dissolved the granularity binary: the deal vertical (one engagement per candidate company; external contributors held-until-admitted; OVA-dependent for demonstrable isolation) pairs with the fund record vertical (one engagement per fund, life of the vehicle, no external contributors by design, OVA-independent; the across-tenure success test — a partner who was not there reconstructs any decision from the record alone). The pair relates by reference, not containment (seed v0.12's membership-versus-reference distinction); the limited partner reporting extract was corrected from deal-level to fund-level (deal seed v0.2 drops it; fund seed v0.1 declares it; misplacement preserved in the sibling). Record main advanced across four pushed commits fa7c8c1(pre-existing) → 5ff1b95 → 13b4d7c → 2b775ab → 5587149; two Finder-duplicate seed HTML files deleted from candidate-seeds/loomworks/ (untracked, cleanup recorded in the 13b4d7c commit message). See Entry 119.
Entry 118 ends before ### 4.A Carryover from v0.41. Insert after Entry 118's closing text and its --- (if present), and before ### 4.A:
### Entry 119 — Venture-diligence vertical arc: inspection-grounded, two-vertical restructure (new v0.73; 2026-07-28)
The first vertical filed as a first-class record area, and the session that produced it ran the full discipline loop: draft → inspect against the live engine → correct against the verdicts → restructure on Operator synthesis → version-bump with every prior position standing.
**The document set.** `verticals/venture-diligence/` (new area, 18 files at close): deal walkthrough v0.1 → v0.2 (inspection verdicts absorbed; three-door create stage; recall caveat added) → v0.3 (two-vertical restructure); deal candidate-seed template v0.1 → v0.2 (limited partner consumer/shape-type/render-type removed; external-contributor clause converted from "requires verification" to verified-state-with-commissioned-arc; disclosure-permission-attributes constraint added for the fund record's reference shaping); fund record candidate-seed template v0.1 (no external contributors by design; across-tenure success test; reference-persistence tension named); the two-vertical structure note (trajectory preserved: binary → Option A with residue → Operator synthesis); the pain-points mapping (twelve pain points bucketed substrate-today / method-work / genuine-gap; the source material's five "highest-leverage problems" match seed commitments four of five, fifth honestly qualified); the CC inspection brief + report.
**The inspection (engine main `1aac815`, read-only).** V1 contribute-without-read: BREAKS — no read endpoint consults designations, membership grants read, Manifestation/Memory-status reads gate on the contributor-flavoured dependency; reframed as OVA-not-yet-enforcing per seed v0.12's reach axis, arc commissioned. V2 upload types: PARTIALLY HOLDS — two pathways, inconsistent rules (`.docx` accepted by one, rejected by the other); best case 3 of 6 data-room types. V3 skills: 4 + 9 across two registries; no spreadsheet/presentation extraction. V4 aggregation: PARTIALLY HOLDS — workspaces built/owned/filtering `GET /engagements?workspace_id=`; `/me/dashboard/*` routes take only limit+cursor; the CTE looks parameter-ready. V5 recall: wholesale window of 50, no search index in schema history (`to_tsvector`/`tsquery`/`ILIKE`/`pg_trgm`: zero hits repo-wide and in every migration); silent failure on the natural skeptical probe. Report at `verticals/venture-diligence/loomworks-vertical-vc-diligence-cc-inspection-report-v0_1.md`; Appendix A carries the Operator's FORAY-as-term-sheet-condition motion as marked commentary, its investigation commissioned and sequenced after the OVA arc.
**The two-vertical decision (Operator, 2026-07-28).** The granularity binary (per-deal vs per-fund) resolved by synthesis, not selection: two engagements meaning two verticals, licensed as one package. Deal vertical carries diligence weeks; fund record vertical carries the decade — thesis trajectory, pass reasoning, entry beliefs, partner-turnover-proof institutional memory. Reference-not-containment preserves external-contributor isolation structurally; the fund engagement never touches the OVA question and can lead commercially while the deal vertical's isolation dependency clears. The critical paths are disjoint (structure note §5 table). Commercial posture: annual license anchored to the fund's life — the legacy-knowledge pricing posture arriving on its own merits.
**Cross-cutting outputs.** Queued-directions v0.30 (sibling of v0.29; §18.2 priority raised with V5 evidence; the no-live-recall-demonstration rule recorded as product-wide). OVA reach-enforcement scoping handoff filed at `session-handoffs/` (per the non-phase-scoped precedent); the arc is commissioned and parked at Operator discretion — it gates deal-walkthrough v0.4 and sequences the Appendix A investigation. The V4 workspace finding is flagged into the pending aggregating-scope decision: if workspaces are the nominated-set mechanism, the contemplated seed amendment may shrink or dissolve. Ingestion findings (pathway-rule inconsistency; spreadsheet/presentation absence) passed to the ingestion-interfaces arc.
**Record commits (all pushed, `origin/main` = `5587149`):** `5ff1b95` queued-directions v0.30; `13b4d7c` initial vertical set + OVA handoff + Finder-duplicate cleanup (deletions untracked, recorded in message); `2b775ab` structure note + fund seed; `5587149` deal v0.3 + deal seed v0.2. The first push also carried pre-existing unpushed `fa7c8c1` (CR-2026-156 + orientation-pack grounding pair) — a fourth push-discipline instance: a prior session's commit stranded on local main until the next session's push.
In Section 1 (Current document authority), locate the line or block carrying the record repo's current main SHA (the Status block references record main 461f09a; §1 may carry its own). Append, per the section's established update pattern:
> Updated for v0.73 (2026-07-28): record main advanced to 5587149 (four commits this arc plus the pre-existing fa7c8c1 carried in the first push). New record area: verticals/venture-diligence/ (18 files). Queued-directions authority: v0.30 (highest present; v0.22–v0.29 live in the directory, v0.5–v0.21 archived; .html companions stopped at v0.26). Engine and Operator Layer unchanged this arc.
If §1 carries no record-SHA line, add this as a new line in §1's repo-state block per its layout.
Add two items to Section 5 (Open questions and known issues), after the most recent v0.72-era item:
**OVA reach-enforcement scoping arc — commissioned, not yet run (2026-07-28).** Handoff filed at `session-handoffs/loomworks-ova-reach-enforcement-scoping-handoff-v0_1`. Central design question: can a reach access-control list exclude an engagement's own contributor from reading the engagement they contribute to (seed v0.12 commits the reach axis; the engine's membership-grants-read is the not-yet-enforcing state, `deps.py:1160-1179` at `1aac815`). Gates: the deal vertical's demonstrable isolation (walkthrough v0.4 trigger) and the Appendix A FORAY-as-term-sheet-condition investigation, sequenced after it. Parked at Operator discretion.
**No-live-recall-demonstration rule — standing conduct (2026-07-28).** Until queued-directions §18.2 (topic-filtered, relevance-ranked recall) lands, no live recall demonstration in front of a prospect: recall is wholesale (50-most-recent window, no search index has ever existed) and fails silently on the ask-about-something-early probe. Product-wide; every vertical inherits it, the fund record vertical hardest.
Insert above the - v0.72 changelog entry:
- **v0.73** (2026-07-28): **The venture-diligence vertical arc — first vertical filed as a record area (`verticals/venture-diligence/`, 18 files), grounded by a read-only engine inspection, restructured by the Operator's two-vertical decision.** Inspection at engine `1aac815`: V1 contribute-without-read BREAKS (membership grants read; reframed as OVA-not-yet-enforcing per seed v0.12; scoping arc commissioned, handoff at `session-handoffs/`); V5 recall wholesale (50-window, no search index ever; queued-directions → v0.30 with §18.2 priority raised and the no-live-recall-demonstration rule recorded); V2/V3 ingestion sharpened (two pathways, inconsistent rules; no spreadsheet/presentation path); V4 cross-deal gap smaller than assumed (workspaces near-ready; bears on the aggregating-scope decision). Two-vertical structure: deal vertical (per candidate company, external contributors held-until-admitted, OVA-dependent) + fund record vertical (per fund, life of the vehicle, no external contributors, OVA-independent), related by reference not containment; the limited partner reporting extract corrected from deal-level to fund-level with the misplacement preserved in siblings. Document trajectory: deal walkthrough v0.1→v0.2→v0.3; deal seed v0.1→v0.2; fund seed v0.1; structure note; pain-points mapping; inspection pair. Record `main` `461f09a`-era → `5587149` across four pushed commits (plus pre-existing `fa7c8c1` carried — a fourth push-discipline instance). Engine and Operator Layer untouched. Adds §3 Entry 119; §1 record-authority update; §5 the OVA-arc and no-recall-demo items. Otherwise carries v0.72 forward.
Replace:
*Loomworks Current-Status Manifest — v0.72 — 2026-06-28*
with:
*Loomworks Current-Status Manifest — v0.73 — 2026-07-28*
fa7c8c1.main 5587149, new verticals area, queued-directions v0.30 authority.1aac815 and record SHAs 5ff1b95/13b4d7c/2b775ab/5587149 appear verbatim..md-only (the manifest's .html companions are not maintained at current versions).
DUNIN7 — Done In Seven LLC — Miami, Florida
Current-Status Manifest v0.73 — amendment instructions — v0.1 — 2026-07-28
Splice-list against v0.72: the venture-diligence vertical arc — 18-file record area, five-verification inspection at engine 1aac815 (V1 BREAKS → OVA arc commissioned; V5 → queued-directions v0.30 + no-recall-demo rule), the Operator's two-vertical decision (deal + fund record, reference not containment, LP reporting corrected to fund level), record main → 5587149. Engine and Operator Layer untouched. Add-new-file sibling; v0.72 untouched.