Request Ledger

Definition

The request ledger is the append-only collection of Blackridge economics events. It is not a transcript store. It is a body-free evidence stream for cost, usage, attribution, lineage, routing, cache, timing, and errors.

Each ledger row is an economic evidence record: cost, route, attribution, cache, lineage, timing, and provenance without prompt or completion bodies.

Why It Matters

Reports are only as reliable as their evidence. The ledger lets Blackridge serve reproducible findings through the investigation API while preserving runtime provenance for every captured request.

How Blackridge Represents It

Blackridge represents each model interaction as a canonical economics event. The event records cost, usage, timing, route, cache status, attribution, lineage, errors, and provenance. Prompt and completion bodies are not part of the standard economics record. The investigation API reads this evidence store and powers the assessment UI, workflow replay, request ledger view, and exports.

Example

Open a finding in the investigation UI and expand the evidence drawer. The drawer links the claim back to the underlying ledger records, including cost, route, attribution, confidence, timing, and provenance.

Common Mistakes

• Editing events by hand and then trusting report output.
• Assuming missing pricing means zero cost. Blackridge reports missing pricing as unknown.
• Mixing tenants and filtering with the wrong --tenant-id.

Related Docs

• Glossary
• Event Schema
• Report Fields