02 · Repository
Codex activity
Recent commits
privateRepository activity stays in the private local dashboard.
Latest decisions
privateDecision detail stays in the private local dashboard.
Program status · 2026-07-12
M1 remains active at 5 of 6 tasks complete. Every implementation slice passes offline verification: the Forma publisher, bounded watcher, geometry-prep and Contract A, private Supabase publication, authenticated project cards, and the existing three.js scene with layers, isolate and hide. All non-spinning three.js views now stop drawing while idle; workspaces and reports keep their full-fidelity effects. Mock Run keeps technical execution separate from the future sourced verdict, and mock Results keeps useful synthetic metrics without invented rules, thresholds or PASS/FAIL decoration. The viewer now has an offline Worker boundary that preflights and decodes one bounded caller-supplied optional PLY, transfers owned attribute and index buffers, and reconstructs three.js geometry in O(1); no result reference or route consumes it. The generic orchestrator can emit or persist deterministic Contract B in a write-once envelope with an integrity manifest. It can also record caller-supplied Contract C only after that exact job verifies, with a second write-once integrity manifest binding both contracts; no engine is run and no evidence reference is resolved. A versioned CLI fixture now demonstrates that B-to-C persistence while identifying itself both in the JSON and terminal as no engine, unresolved evidence, no rule and no verdict. This preparation does not start M2. The first shadow-rule source audit found a precise candidate in the private source archive, but M3 still requires explicit provisional-authority and interpretation approval; no rule is approved and no threshold is active. Cloudflare and Supabase are connected; the real publish-to-orbit demo still needs a real Forma project/session plus the two local gitignored Speckle tokens and destination ids. Compliance screens remain visibly mock; M1 produces geometry, not a compliance result.
01 · Delivery map
Each milestone closes with a reproducible demo, never a calendar date.
02 · Repository
privateRepository activity stays in the private local dashboard.privateDecision detail stays in the private local dashboard.03 · Verification
Fixture inputs and outputs are versioned. Future runs will retain inputs, outputs and logs.
04 · Hand-off
Only external choices that need Enrique are marked as blocked.
No implementation slice remains pending offline. M1 stays active until a real Forma project/session, the two local gitignored Speckle tokens and exact destination ids are available; one selection must then be published, materialized and opened from the live project card as the exact same Speckle version within seconds, with layers, isolate and hide demonstrated. No secret belongs in the evidence.
Research found a precise candidate in the private source archive, but current authority is not established. M3 remains queued until Enrique explicitly approves provisional authority and the applicability, legal receiver, irradiation physics, evaluation-window, equality, baseline and combined-verdict interpretations. No rule is approved and no threshold is active.