Memory #147 CURRENT
V2.2 Hardening Gate Status V2.2 axis (Lab-to-Node Stabilization) status — 1 of 4 core deliverables landed, 5 of 8 gate requirements ❌; audit of 2026-04-23 revealed fabricated and inflated claims in V2.1-era §3.7 that V2.2 inherited Established 2026-04-23 during internal Lydian Stack audit. **Umbrella:** `D:/GitHub/lydian-node-specs/TTI_ARCH_LYDIAN-STACK-001_V2_2.md` **Delta:** `D:/GitHub/lydian-node-specs/TTI_ARCH_LYDIAN-STACK-001_deltas/V2_2.md` ## V2.2 gate — 8 requirements | # | Requirement | Status | |---|---|---| | 1 | TRIVA-Go shipped + frame-class validated | ✅ (118 tests, 4-class parametrised test added `7657444`) | | 2 | Constants match pip to 15 decimals | ✅ (within 1e-15 tolerance; 12 ULPs between Go literal and Python runtime) | | 3 | Test harnesses frozen | ✅ UNIFIED 2026-04-24 — all 13 Genesis files under pytest (736 tests, single invocation) | | 4 | Repo layout frozen | ✅ V2.2 SCOPE COMPLETE 2026-04-24 — §9.1/9.2 C renames landed; §9.4 ACO→WRF wallet rename landed (spec V3.0 + pria_core.wrf + wrf_sign + 8 callers updated; schema_version 0x21→0x30; wire strings aco_issue→wrf_issue). §9.3 pria_core.* restructure remains for V2.6 per §9.6. | | 5 | CustodyProvider interface locked | ✅ CLEARED 2026-04-24 — GCD.SPEC.CUSTODY-PROVIDER-001 V1.0 published; pria_core.custody package landed (ABC + ProviderId enum + ProviderCaps flags + PRootHandle + SoftwareCustodyProvider); wallet.py migrated off KeyStore; 55 tests | | 6 | build.sh + CI orchestration | ✅ CLEARED 2026-04-24 — `build.sh` at repo root (Python ≥3.10 gate, editable pip install, full pytest); `.github/workflows/ci.yml` matrix (Ubuntu × 3.10/3.11/3.12). Fixed broken `setuptools.backends._legacy:_Backend` build-backend to `setuptools.build_meta` | | 7 | Node observability (health/version/logs) | ✅ CLEARED 2026-04-24 — `pria_core.observability` package (health builder per NODE-001 §8.1; startup banner §8.2; `ScopedLogger` JSON-lines with scope/tier/node_id §8.3); 38 tests | | 8 | Cross-platform repro (Linux + macOS) | ✅ CLEARED 2026-04-24 — GitHub Actions matrix (ubuntu-latest × py3.10/3.11/3.12 + macos-latest × py3.11/3.12). All 5 jobs green on commit 5cd8d98 (829 tests identical on both platforms). Run ID 24896510494 | Gate status: **✅ CLEARED 2026-04-24** (8 of 8 ✅). The V2.2 Lab-to-Node Stabilization axis is fully closed. V2.3 Security and Identity Hardening axis is now unblocked per umbrella §8.1. ## Audit findings (2026-04-23) — corrected in V2.2 umbrella §3.7 - `clock_peer`: 172 (claimed) → **124** (custom-harness, measured) - `pria-core` Docker container: "64 passing" (claimed) → **NO DOCKERFILE EXISTS** (row replaced with "Planned") - Memory Layer: 50+ (claimed) → **~455 vitest tests** (244 `Tribernachi-Memory-Layer/` + 211 `tce/`) - Test-harness bifurcation acknowledged in new §3.7.1 **Why this matters:** V2.1 had several aspirational-stated-as-shipped claims that were carried into V2.2 unchanged. Direct audit revealed the gaps. Delta V2_2.md is now axis-progress-snapshot, not milestone close-out. ## How to apply - **Do not trust memory entries** that cite `pria-core` Docker container, or 172 `clock_peer` tests, or "50+ memory tests" — those figures are corrected in V2.2 §3.7. - For accurate running-deployment numbers, read V2.2 §3.7 directly (it reflects measured state). - V2.2 gate close-out requires landing items 5–8 above plus resolving 3 (harness unification) and 4 (rename migration). Tracked as tasks #15–#20 in the originating session. - V2.2 close-out is the precondition for starting V2.3 (Security and Identity Hardening axis per umbrella §8.1). — [project_v22_gate_status.md]
| Composite | 45693A6A507CD013F |
| Project prime | 13 |
| Domain prime | 17 |
| Type prime | 67 |
| Importance | 0.343295 (ACTIVE) |
| Decay epoch | 0 |
| Created | 2026-05-04 15:46:49 |
| Valid from | (unset) |
| Valid to | NULL — still believed true |
Outgoing Edges
No outgoing edges.