docs(runtime): close J3.5 and plan J3.6

Record the canonical entity/object delta cutover, full Release and exact-binary connected evidence, rollback, and the adversarial zero-owner J3.6 execution contract. Synchronize architecture, roadmap, milestones, and agent guidance.

Co-authored-by: Codex <codex@openai.com>
This commit is contained in:
Erik 2026-07-26 06:54:47 +02:00
parent ce3ac310d9
commit 84954c8b77
12 changed files with 405 additions and 54 deletions

View file

@ -2,14 +2,15 @@
**Date:** 2026-07-24
**Status:** Slices AI and J0J3.4 are complete. Flat-authoritative collision, zero-
**Status:** Slices AI and J0J3.5 are complete. Flat-authoritative collision, zero-
allocation resolve scratch, parsed-graph removal, connected correctness/
lifetime acceptance, and Slice-I closeout landed 2026-07-25. Slices FL were
explicitly approved 2026-07-24. Slice J0J1 established the enforced Runtime
boundary and borrowed contract seam; J2 moved canonical session/transport
lifetime and ordered inbound routing; J3.1J3.4 moved canonical entity identity
and object-table lifetime to Runtime and exact graphical projection identity
to App. J3.5 is the active execution point.
lifetime and ordered inbound routing; J3.1J3.5 moved canonical entity identity
and object-table lifetime to Runtime, exact graphical projection identity to
App, and one ordered canonical entity/object stream plus direct views to all
hosts. J3.6 adversarial lifetime closeout is the active execution point.
**Scope:** Reconcile and sequence the existing Modern Pipeline (`MP`) and
Linux/headless (`LH`) tracks using the 2026-07-24 connected performance audit.
@ -1250,13 +1251,16 @@ gameplay before removing every production parsed collision graph. Slice I7
passes 8,413 Release tests / 5 skips plus both exact-binary connected routes;
every stable checkpoint reports zero retained parsed collision graphs. J1 is
complete with borrowed contracts, and J2 owns canonical session/transport
lifetime plus ordered inbound routing in Runtime. J3.1J3.4 are complete:
lifetime plus ordered inbound routing in Runtime. J3.1J3.5 are complete:
Runtime owns the only entity GUID/incarnation/local-ID directory, and App's
materialized sidecars plus spatial/presentation worksets carry exact
`RuntimeEntityKey`. One `RuntimeEntityObjectLifetime` also owns the exact live
`ClientObjectTable`; App is a synchronous borrower. J3.5's ordered canonical
entity/object delta stream and direct borrowed views are the current execution
point.
`ClientObjectTable`; App is a synchronous borrower. Exact `ce3ac310` adds the
one per-generation canonical entity/object delta stream, issues Runtime
identity before App hydration, and gives graphical/no-window hosts the same
direct borrowed views. Its 8,472-test / 5-skip Release suite and exact-binary
seven-checkpoint connected route pass. J3.6 adversarial failure and zero-owner
closeout is the current execution point.
Evidence:
[`../research/2026-07-25-slice-g5-production-profile.md`](../research/2026-07-25-slice-g5-production-profile.md)
and
@ -1272,6 +1276,8 @@ and
and
[`../research/2026-07-25-slice-j3-3-exact-projection-store.md`](../research/2026-07-25-slice-j3-3-exact-projection-store.md)
and
[`../research/2026-07-26-slice-j3-5-canonical-delta-stream.md`](../research/2026-07-26-slice-j3-5-canonical-delta-stream.md)
and
[`2026-07-25-modern-runtime-slice-j.md`](2026-07-25-modern-runtime-slice-j.md).
The intended order is therefore:
@ -1286,7 +1292,7 @@ honest metrics + committed baselines (A — exit criteria block C)
-> delta GPU submission (G)
-> residual frame cleanup (H-a, H-b, H-c)
-> flat collision assets (I — COMPLETE)
-> presentation-independent runtime (J — CURRENT at J3.5)
-> presentation-independent runtime (J — CURRENT at J3.6)
-> Linux/headless/multi-session (K)
-> evidence-gated GPU jobs (L)
```