Perseus Ledger

Perseus Ledger is the verifiable event and provenance layer for autonomous systems. It records what happened, under what authority and evidence, and whether the history can be independently verified.

It is deliberately not an AI-spend dashboard. Ledger provides an append-only, hash-chained record that ties activity to its actor, boundary, evidence, configuration, action, result, and optional resource allocation. It works independently with any agent runtime, application, internal tool, or offline deployment.

What Ledger establishes For each recorded event, the stable ledger captures the operational facts already available to the system:

Actor and boundary — organization, workspace, user/agent, and task type Execution configuration — provider, model, and event metadata Action and result — the event itself plus its immutable record hash Resource allocation — optional token and cost attribution Evidence linkage — external references and retained checkpoints where supplied Integrity — an append-only cryptographic hash chain that can be verified independently The current ingestion contract is deliberately stable during the product transition: ledger_agent, the ledger CLI, /v1/usage, existing database paths, and deployed integrations remain supported compatibility surfaces. Stripe is an optional settlement adapter, not the product boundary.

Why it matters AI systems need more than observability. They need a defensible answer to:

What did the system know, what did it do, under which model and policy, what did it consume, and can we prove it later?

Perseus Ledger provides the evidentiary layer for that answer. It can work beside any agent framework, application, internal tool, offline environment, or federated deployment.