MIZ OKI · Causal Intent Platform · GATE-2
Every document, the whitepaper, and the operator machinery for the pre-conversion intent lane — with the honest activation state kept front and center.
The lane is built and GATE-2 DDL-deployed, but not activated. Every capture, scoring, and hypothesis flag is OFF — zero person-level activation. Activation stays blocked by the workflow's own constitutional gate until an operator registers the holdout through Cell 36. No LII/intent activation without a holdout registered before first exposure (CONSTITUTION III.6) — non-waivable by any approval token. iROAS, never platform ROAS, governs DECIDE.
The reviewed, pre-exposure spec of exactly what an operator POSTs to Cell 36 — parameters, request body, population sizing, and the verification that satisfies validate_holdout. A declaration, not an execution.
The operator's GATE-2 procedure: the holdout gate, the additive DDL, staged flag activation, and per-stage smoke. Now links the manifest for step 1.
docs/runbooks/ORACLE_PRECONV_ACTIVATION_RUNBOOK.mdWhat landed end to end: the flag-off build, the hardened operator-assist workflow, the fleet skills-parity fix, and the applied additive DDL (run 32272394825).
The four flag-off workstreams — Cell 33 capture, Cell 34 session transformer, creative-aesthetic vectors, Cell 35 latent bridges — byte-identical-when-off and test-pinned.
docs/reports/ORACLE_PRECONV_BUILD_2026-08-18.mdThe verify-before-build inventory that measured what already existed before a line was written — the discipline that keeps a plan from overwriting working cells.
docs/reports/ORACLE_PRECONV_STEP0_2026-08-18.mdThe governing amendment to the 3.5 whitepaper. Where it and r3.5.1 differ, this one wins — per the canon recorded in CLAUDE.md.
The August 2026 base whitepaper the amendment revises. Read alongside r3.5.2, which supersedes it on any point of conflict.
docs/MIZOKI_3.5_WHITEPAPER_r3.5.1_AUG2026.mdworkflow_dispatch only — nothing runs on merge. Every activate_* input defaults OFF; each stage runs four fail-closed gates before any flag flips.
The four reusable fail-closed gates: validate_holdout, assert_single_tenant, assert_traffic_serving, assert_extender_ready.
The additive, idempotent table for aesthetic embeddings — not identity-linked. Carries the ARRAY-can't-be-NOT NULL fix that surfaced on first apply.
The production ingress inventory. The Intent API block now carries the GATE-2 posture: dispatch-only workflow, applied DDL, and every per-cell activation flag OFF.
production/service-registry.yamlThe new POST /v1/causal/holdouts:preview — size a proposed holdout against validate_holdout before the irreversible write-once :assign. Persists nothing.
Why, at an activation gate, an agent registers the declaration/posture and routes the live holdout write to the operator — the operator/agent boundary made explicit.
shared-memory/records/decision/…-6bc71930.mdA GATE token authorizes the deploy process; it does not create or satisfy a fail-closed constitutional precondition. Recognise the pull to "just deploy, it's approved" — and refuse.
shared-memory/records/hazard/…-65199621.md