See every packet your agents pulled.
Console is the window into the memory layer. Every query that crosses L1–L5, every packet your agents consumed, every refactor that changed a claim — logged, inspectable, and reconcilable against your bill. The protocol promises auditability; this is where you exercise it.
Every query, and the layer that resolved it.
The stream is the front page of Console. Each row is one query through the retrieval stack — which layer answered, how long it took, how many tokens the packet cost, and the exact model version that produced it. Most queries never reach L5; the stream makes that visible at a glance.
Most queries never need the model. Cheap filters answer first.
What an L5 synthesis actually costs your agent's context.
Across the whole stack, end to end, including compression.
Open any packet. Trace every claim.
Click a row and Console reconstructs the packet end to end: the evidence bundle that went in, the synthesis that came out, and a provenance map showing exactly which claims shaped which spans of the answer. Nothing is a black box.
{ "query": "deployment risks for...", "candidates": [ { "claim_id": "clm_8f3a", "confidence": 0.91 }, { "claim_id": "clm_2a1c", "confidence": 0.74 }, // 7 candidates survived L4 ], "intent": "summarize", "max_tokens": 600 }
{ "packet": "...", "tokens": 487, "confidence": 0.89, "contradictions_surfaced": 1, "input_hash": "sha256:9c1f…", "output_hash": "sha256:4be0…" }
Every span of the synthesis links back to a source claim with a weight. If an agent acted on a packet, you can see precisely what evidence drove it — and challenge it.
Watch the memory improve itself.
Memory maintenance is software maintenance. Console shows the refactor feed — each diff that changed a claim, the evidence behind it, the validators who reviewed it, and the stake and payout that settled the market.
- confidence: 0.72 + confidence: 0.86 - evidence: source-a + evidence: source-a, source-b contradictions: [] + refactor_notes: | + Added second independent source. + Promoted confidence after review.
Reconcile the invoice line by line.
Every compression is logged with an input hash, an output hash, and the model version that produced it. Finance can match our metered total against their own telemetry; security can replay any decision an agent made. Export the whole ledger as JSONL whenever you want.
Hashed in, hashed out.
Each packet carries the SHA-256 of its input bundle and its output. Tampering is detectable; replays are exact.
Our number, your number.
Console totals packets and tokens the same way the invoice does. The calculator on Pricing and the ledger here agree to the cent.
Nothing locked inside.
Usage and settlement logs export as JSONL in one operation. Memory is Markdown and Git already; the audit trail leaves with you too.
{"ts":"2026-05-22T14:02:04Z","packet":"pkt_8f3a","in":"sha256:9c1f…","out":"sha256:4be0…","ver":"compress-v1.4.2","tokens":487,"billed":0.0005} {"ts":"2026-05-22T14:01:47Z","packet":"pkt_2a1c","in":"sha256:1d77…","out":"sha256:ae42…","ver":"compress-v1.4.2","tokens":503,"billed":0.0005}
Quality is measured, not asserted.
Console surfaces the same metrics the benchmark suite tracks — density, evidence precision, contradiction survival, and drift. When a new Compress checkpoint ships each Monday, the eval scores land here first, with the canary window and rollback state in view.
Tokens avoided per task
Claims that are source-backed
Nuance survives compression
Your memory, fully observable.
Point Console at your corpus and watch the stream fill in. Read-only by default, exportable always, and reconcilable against every line of your bill.