Certification and gates
How a table earns CERTIFIED status, and what each of the three gates checks.
Möbius certifies data through three gates before it can be read through the certified API
doors (REST, GraphQL, MCP) or trusted for a downstream decision. A table moves from
QUARANTINED to CERTIFIED only after it clears the gates your workspace requires; nothing
short of that state is readable through the certified doors.
QUARANTINED
│
▼
Gate 1 — Predicate Gate "Did the data physically satisfy its declared contract?"
│ pass only
▼
Gate 2 — Semantic Gate "Is the data meaningful, coherent, and trustworthy for its purpose?"
│ pass only
▼
CERTIFIED
│
▼ (after certification, non-blocking)
Gate 3 — Statistical Evidence "Does the data's distribution still support the decision it certified for?"Gate 1 — Predicate Gate
Deterministic, SQL-based checks against the data itself: row counts, null rates, required columns present, grain uniqueness (no unexpected duplicate keys), numeric bounds, referential integrity, plus any pattern or custom rules your steward has declared. The answer is binary — pass or hard-fail — with no interpretation. Gate 1 runs first because it's fast and cheap; if it fails, Gate 2 never runs.
Gate 2 — Semantic Gate
A deeper, interpretive check for whether the data is coherent and trustworthy for what it claims to be used for — not just whether it satisfies its structural contract. A table can pass every Gate 1 predicate (no nulls where required, no duplicate keys) and still fail Gate 2 if, for example, a column's meaning has silently drifted from what it was certified against. Gate 2 produces a rating (green through black) rather than a pass/fail — Gate 2 can never override Gate 1: a strong semantic score never promotes a table that failed a hard predicate.
Gate 3 — Statistical Evidence
Runs after certification, asynchronously, and never blocks it. Gate 3 compares the table's current distribution against its previous certified snapshot — is a numeric column drifting, has a categorical column's mix shifted, has the null rate or cardinality moved — and attaches what it finds to the certification record as supporting evidence. It can strengthen or weaken confidence in a certification after the fact, but it cannot revoke or block one. How many gates apply is one per-environment setting on Workspace → Environments, with three rungs: Gate 1 only; Gate 1 + Gate 2 (the default); or Gate 1 + Gate 2 + Gate 3. Each rung adds a gate and never removes one — on the Gate-1-only rung, Gate 2 is skipped outright, and the certification report says so explicitly rather than staying silent about it.
Certified data is not immutable — but it's never silently mutable
A certified table can still be written to. Every write to certified data creates an audit entry and automatically queues a recertification check — certified status is a claim about the data as of the moment it was verified, not a promise that it will never change. What Möbius guarantees is that a change is never invisible: nothing mutates a certified table without leaving a governance event, and nothing silently downgrades a table's certified status without a recertification decision.
Gate mode
Independent of the three gates above, each environment has a gate mode that decides how strictly row-level writes are enforced against your declared contract at ingest time:
- Enforcing — a row that fails a predicate is rejected and never written.
- Advisory — a row that fails is written anyway, but flagged. Every read door discloses which rows carry that flag (see audit trail) — flagged, never filtered.
- Off — no row-level predicate evaluation runs on write.
Gate mode governs individual writes as they happen; Gates 1–3 govern whether the table as a whole earns and keeps certified status.