TT Claude Memory

project_v2_build_repos_phase_0_hardening_state

Properties1
descriptionAll 5 v2 build repos at Phase-0 hardened minimum; 2 at full 5-step cycle (www + test-suite); 3 at 3-step (no /review-plan yet)

2 min read

As of 2026-04-28T19:45, the v2 build-repo Phase-0 hardening campaign is structurally complete:

  • code-inheritv2-test-suite (this repo): full 5-step cycle COMPLETE. Sprint S1 ready. Cross-cutting Apache 2.0 dual-stack TS+Python test pyramid; 72 leaf folders + 26 stub READMEs + 4 runners + coverage-floor + ci-gates + conformance + docs/ci-pipeline.md + examples/first-fixture/ + project-level CLAUDE.md.
  • code-inheritv2-www: 4-step (no second /review-plan verification). Tier-3 Apache 2.0 website; Astro 5.x + Tailwind v4 + Cloudflare Pages.
  • code-inherit-v2: 3-step (no /review-plan yet). Tier-3 Apache 2.0 standard; LinkML 1.10.0 + ROBOT 1.9.7 + Catala 1.1.0 + Mopsa-c v1.2.
  • code-inheritkit: 3-step (no /review-plan yet). Tier-2 AGPL+commercial dual SDK.
  • code-ias: 3-step (no /review-plan yet). Tier-1 commercial-proprietary IAS app.

Why: Multi-day arc Sun 27 Apr → Tue 29 Apr 2026 closed the structural-hardening campaign. ~65+ commits across 6 repos (5 build + docs-strategy). Pattern proven 5x. Path A funding CONFIRMED 2026-04-27; Phase-1 build runway green-lit. Sprint S1 (Stage 4 work begin) targeted Q3 2026.

MLP Law partner-pipeline accelerator (separate Rich-owned workstream landed concurrently same day): Touch #1 POSITIVE outcome 2026-04-28; Touch #2 Mon 11 May 2026 with Stephen Attree; MLP board Tue 19 May 2026 = potential pilot sign-off gate; pipeline state P-β → P-γ; 24+ months ahead of M3 expectation. Implications for v2 BUILD-PLANs: if MLP signs at 19 May board, P-ε Contracting could land May/June 2026 — ahead of M13-M15 cadence. Forward signal; not blocking.

How to apply:

When planning any forward work on the v2 build repos:

  1. Sprint S1 readiness: code-inheritv2-test-suite is ready; the other 4 are also ready (3-step minimum is enough for Sprint S1 to begin).
  2. Forward candidates for 5-step parity: code-inherit-v2 + code-inheritkit + code-ias each at 3-step. If Rich wants 5/5 parity through the full 5-step cycle, ~2-2.5 hours of /review-plan reconciliation passes cover all 3.
  3. Faith-tradition framing: scaffolding is correctly committed (per A-99 SYMMETRIC + EXPANDED 2026-04-26 lock); the MLP “did not resonate” signal is a partner-firm-pitch positioning concern, NOT a scaffolding/architectural change.
  4. MLP intel (Clio Manage + Clio Grow + Clio Draft + Lexis Protégé AI; POA in-house; Digital Assets log) informs InheritKit converter priority queue + IAS partner-firm-onboarding scope. Not in any current BUILD-PLAN; will land at Sprint-1+ partner-pipeline-driven planning.
  5. Doc-state version pins as of v3.8 lock: arch-state v3.8 (2026-04-28T19:45) + master-plan v1.8 (2026-04-28T19:30) + risk-register v1.1 (2026-04-28T19:00) + repo-topology v1.2 (2026-04-28T19:15) + test-suite BUILD-PLAN v1.2 (2026-04-28T17:55).

Graph View

Backlinks