SUPERSEDED by docs/marketing/MIZOKI_MARKETING_AUTOMATION_WHITEPAPER_r2.0_SEP2026.md

MIZ OKI 3.5 — MARKETING AUTOMATION WHITEPAPER · AMENDMENT r1.3

Nine capabilities present in the platform and now formally documented

Amends: MIZOKI_MARKETING_AUTOMATION_WHITEPAPER_r1.2_AUG2026.md (base stands; this adds §13). Status vocabulary unchanged: LIVE · PARTIAL · IN BUILD · PROPOSED. Sources: build reports through F4 go-live (2026-08-24); Completeness Audit v1.0. Nothing here upgrades a label; every surface passes the standard content gates.

§13 — EXTENDED CAPABILITIES (U1–U9)

U1 · Passport Chaining — Decision Lineage [PARTIAL]

Business purpose: answer "why did the system believe this?" not just "what did it decide?" Regulators, boards, and CFOs ask for the chain, not the node. How it works: each ValidationPassport carries references to the passports and realized outcomes that fed it, forming a traversable lineage graph over the decision store, exercised end-to-end by the SIG-042 harness. Customer benefit: a dispute, audit, or post-mortem reconstructs the full ancestry of any spend action in minutes — the audit trail becomes an audit graph.

U2 · Governed-Vertical Generalization (Counsel Room) [PARTIAL — roadmap framing only]

Business purpose: proof the decision architecture is not a marketing trick: the same Sense→…→Learn loop and gates run a legal-domain scenario lane. How it works: identical Decision Control Plane, passports, and WITHHOLD semantics over a different evidence domain. Customer benefit: enterprise buyers see an architecture, not a point tool — the governance you approve once generalizes. Presented on the About/roadmap surface, never as a marketing-product claim.

U3 · GraphRAG / CausalRAG Explanation Retrieval [PARTIAL]

Business purpose: explanations that cite structure, not vibes. How it works: retrieval over the intent/decision graph respecting causal edges; powers the explanation payloads that accompany every score — an inference the system cannot explain is not surfaced. Customer benefit: every recommendation arrives with its evidence neighborhood attached; analysts verify instead of trusting.

U4 · MarketSignal External Knowledge Graph (Cell 37 lane) [PARTIAL]

Business purpose: context without new PII — demand shifts, market events, external signals as corroboration. How it works: brownfield Cell 37 ingests external market signal joined to first-party evidence strictly as corroboration; it never substitutes for consented behavioral data and never enters causal credit on its own. Customer benefit: fewer false alarms — "your CPA rose because the market moved" is distinguishable from "because your site slowed."

U5 · Geo-SCM Scheduler — the Always-On Half of F4 [LIVE with F4]

Business purpose: continuous calibration without blackout tests. How it works: synthetic-control donor selection plus perturbation-window scheduling feed F4's approval-gated reservations; clean cycles update MMM priors, never before. Customer benefit: incrementality stays current every week at small, capped cost — no quarterly "turn it all off" experiments, no stale lift assumptions.

U6 · Stockout DEL Veto [PARTIAL]

Business purpose: inventory reality as a hard constraint, not a suggestion. How it works: stock state enters the decision-eligibility evaluation itself: a proposal to scale spend into a stockout is vetoed with the constraint named in the passport — upstream of any adapter, regardless of model confidence. Customer benefit: the embarrassing failure mode — paid traffic to sold-out SKUs — becomes structurally impossible to authorize.

U7 · Governed Build Fleet [LIVE — engineering surface]

Business purpose: credibility you cannot fake: the AI fleet that builds the platform obeys the same gates the platform sells. How it works: claim-first coordination ledger, skill parity checks, canon linter, adversarial verifiers, typed approval strings — the platform's own governance applied to its makers. Customer benefit: the vendor's development process is itself evidence of the product thesis. Documented on the engineering/About page.

U8 · Deploy-Time Canon Correction [LIVE]

Business purpose: documents cannot drift from reality. How it works: every doc pushes through content QA and canon transforms at deploy; stale technical claims are corrected or blocked — this pipeline corrected this whitepaper's own §3 datastore reference on publication. Customer benefit: what you read on our surfaces has passed the same truth gate as our code — including this amendment.

U9 · Intent Tool Surface + Deterministic Scenario Replay [PARTIAL]

Business purpose: the integration story for technical buyers. How it works: eight shipped intent tools expose evidence programmatically; demo scenarios replay deterministically — same input, same trace, same passport. Customer benefit: your engineers integrate against evidence APIs and reproduce any demonstrated behavior exactly; evaluation becomes verification.

§13.1 Placement and discipline

U1, U3, U4, U5, U6, U8 are platform capabilities within this whitepaper's scope. U2, U7, U9 are credibility/integration surfaces documented on About and launch pages, referenced here for completeness. All nine carry citation markers in the Feature Coverage Matrix; no status flips outside the standard gates; anticipatory-intent framing governs throughout.

All capability claims carry status labels. Illustrative figures are not production telemetry or customer results. Targets are stated goals, not measured outcomes, until verified pilot numbers enter the claim ledger.