ClickHouse governs data exhaust.
Cosmocrat governs decision exhaust.
The control plane that enforces, records, and replays every AI and human decision—by policy, not convention.
Runs in your environment. Your keys. Your data.
What is decision exhaust?
Data exhaust captures what happened—logs, metrics, and traces of system events. Decision exhaust captures why it happened—the reasoning, policy evaluation, authority checks, and state transitions that led to an action.
Decision exhaust is the audit-grade record of every AI and human decision — including intent, policy evaluation, authority, execution, and outcome — produced at runtime.
For deterministic software, logs are sufficient. For probabilistic AI agents that reason and act autonomously, data exhaust is blind to intent. You cannot audit an AI's decision to refund a customer by looking at a database transaction log alone; you need the governance record of the decision itself.
Agents don't just chat.
They execute.
Decision exhaust exists whenever an agent reasons, calls tools, touches data, or executes actions. Without a control plane, these distinct events are ungoverned, unrecorded, and risky.
"Experimental AI creates hallucinations; enterprise agents require audit trails."
The Architecture of Governance
A dedicated control plane for decisions, sitting alongside your data plane.
ClickHouse
Observability Speed Layer
Cosmocrat
Decision Authority Plane
The Governance Cycle
A single runtime path for every action.
Policy
Evaluate authority, limits, and context before execution.
Enforce
Permit, block, retry, or escalate—across every tool and lane.
Receipt
Produce an audit-grade record bound to inputs, policy, and outputs.
Rollback + Replay
Reconstruct the full decision path and tighten policy from outcomes.
Receipts you can audit (and replay)
Every governed action produces an execution receipt: who/what/why, what policy evaluated, what state transitions occurred, and what actually happened.
Receipts establish intent, authority, and outcome—independent of system state.
Frequently asked questions
Data exhaust is the byproduct of system operation (logs, traces). Decision exhaust is the byproduct of governance (reasoning, policy checks, authority grants).
One captures what happened. The other captures why it was allowed.