Governance audit trail
What a governance event records, and what you can see about who did what, when.
Every governance-relevant action in Möbius — a row gate decision, a certification, a workspace config change, a connector edit, a token mint, a lifecycle transition — writes exactly one record to Möbius's audit trail. There is a single channel for this: an action either happened and was recorded, or it didn't happen. There is no separate, quieter log that only some actions reach.
What one audit record tells you
Each entry answers the same set of questions regardless of what kind of action it describes:
- What happened — a named action (for example, a table was certified, a row was rejected, a connector's credentials were rotated).
- Who or what did it — a real person acting in the dashboard, a person acting through an AI agent on their behalf, an automated system process (like the certification engine reacting to a schedule-free trigger), or — recorded explicitly, never silently dropped — the absence of any identified actor, for a request that reached Möbius with no verifiable identity.
- Where it happened — which environment the action applies to, and that environment's rank in your promotion ladder.
- Under what governance posture — for actions tied to a gate decision, the gate mode ( Enforcing / Advisory / Off) in force at the moment the decision was made — not the mode in force now, which may have changed since.
Reading the trail
The audit trail is browsable from your workspace's audit log (linked from the dashboard sidebar), filterable by scope. A representative sample of the filter values you'll see, and what each covers:
| Filter value | What it covers |
|---|---|
ROW_GATE | A row was accepted, rejected, or admitted with an advisory flag |
RECORD_MUTATION | A specific row was created, updated, or deleted |
TABLE_LIFECYCLE | A table moved between lifecycle states — quarantined, certified, and so on |
WAREHOUSE_CONNECTOR | A warehouse connector was created, edited, or re-verified |
WORKSPACE_CONFIG | A workspace-level governance setting changed |
INTEGRATION_TOKEN | A token was minted, rotated, or revoked |
WEBHOOK | An outbound webhook was dispatched |
WORKSPACE_MEMBER | A member's role or environment access changed |
The full filter list has more values than shown here — new ones are added only when an existing value genuinely doesn't fit, so the list doesn't drift into synonyms for the same thing.
Why this matters for a certified read
The Governance Envelope every API response carries (see the GraphQL and MCP references) is the real-time summary of a table's governance state. The audit trail is its history — the record of how that state was reached, and by whom, that lets you answer "why is this table certified" or "who approved this write" after the fact rather than only at the moment it happened.