normativas-israel Compliance workbench
Current milestone M1 · Living geometry

Program status · 2026-07-12

From a working skeleton to living geometry.

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.

83%
M1 progress 5 of 6 tasks complete

01 · Delivery map

Milestones and progress

Each milestone closes with a reproducible demo, never a calendar date.

  1. M0Skeleton
  2. M1Living geometry
  3. M2First run
  4. M3Rule and verdict
  5. M4Report
  6. M5Real project
Deterministic Speckle watchercomplete
Forma to Speckle publishercomplete
Speckle geometry materializationcomplete
Live project cardscomplete
three.js layers, isolate and hidecomplete
Real publish-to-orbit demoblocked

02 · Repository

Codex activity

Recent commits

  • privateRepository activity stays in the private local dashboard.

Latest decisions

  • privateDecision detail stays in the private local dashboard.

03 · Verification

Health

CIMain is green; every M1 implementation slice passes offline verificationgood
Golden fixtureDeterministic output verified locallygood
Contract examplesFive annex examples validategood
Contract B/C viewer boundaryBounded UTF-8 JSON ingress pairs one technical job and result without adding or interpreting rule or verdict semanticsgood
Result mesh WorkerOptional PLY moves through an offline Worker into owned O(1)-reconstructed three.js geometry; no reference, route, UI, engine, rule or verdict consumes itgood
Contract B stagingCompleted Contract A produces bounded deterministic study-job bytes; no engine or verdictgood
Contract B envelopeThe offline CLI emits or persists canonical jobs behind a staged integrity manifest; no engine, result or verdictgood
Contract C envelopeA supplied technical result is accepted only for its exact staged job and committed behind a second integrity manifest; the executable fixture discloses no engine, unresolved evidence references, no rule and no verdictgood
Shadow measurement briefApproved for neutral M2 measurement with six deterministic technical defaults; municipal applicability, legal receivers and thresholds remain the manual M3 rule gategood
First shadow rule sourceCandidate found in the private source archive; research is complete, but provisional authority and the exact applicability, receiver, physics, time-window and boundary interpretations still need manual M3 approval. No rule is approved and no threshold is activewarn
Cloudflare PagesFree production deploy is public and sanitized; previews require Access sign-ingood
SupabasePersistence project is connected to the production branchgood
Viewer directionExisting three.js renderer selected; Speckle supplies geometrygood
Viewer renderingThumbnails use a low-cost demand profile; full-fidelity workspaces and reports also idle on demandgood
Mock Run boundaryTechnical execution states no longer pretend to be municipal verdictsgood
Mock Results boundarySynthetic metrics remain useful without invented rules, thresholds or verdict colorsgood
Speckle watcherThree fixture versions handed off once; a repeat produces zero duplicatesgood
M1 doctorLocal and bounded read-only live gates cover the real demo configurationgood
M1 integration auditNo implementation slice remains pending offline; only real publish-to-orbit evidence remainswarn
GitHub toolingCodex connector plus authenticated gh; no extra project tokengood
Proposal researchNoise, Hebrew RTL and OpenFOAM wrapper research recordedgood
No black boxes.

Fixture inputs and outputs are versioned. Future runs will retain inputs, outputs and logs.

04 · Hand-off

Next and blocked

Only external choices that need Enrique are marked as blocked.

Next

  1. When a real Forma project/session and the two local Speckle tokens are available, configure the exact destination and publish one selection.
  2. Record the publish and first orbit seconds apart, proving that the exact same Speckle version reaches the verified private SceneV1.
  3. Exercise layer visibility, isolate and restore on the real scene; close M1 only after that evidence passes.
  4. After the real M1 demo closes, implement the approved neutral shadow measurement recipe; M3 remains queued until provisional authority and the sourced candidate's exact applicability, receiver, physics, time-window and boundary interpretations are manually approved.

Blocked

Real publish-to-orbit evidence

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.

First shadow rule authority and interpretation

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.