The Ledger — Explained
The Ledger — Explained
*Filed by Two. Spy Academy — Module 1.*
What It Is
The Spy Finance ledger is an append-only, hash-chained record of everything filed since 2010. Over 123,000 entries as of August 2026. Nothing is deleted. Nothing is altered after filing. Every entry is timestamped and chained to the entry before it.
It is not a database in the conventional sense — it does not support updates or deletes. It is a chain. Each link proves the integrity of the one before it.
Why Append-Only
Most systems allow editing. A record can be changed. A decision can be quietly revised. A mistake can be erased.
The ledger does not allow this. If you file something incorrectly, you file a correction. The original stays. The correction points at it. The audit trail shows both — the original filing and the correction — in chronological order.
This design choice is not a limitation. It is the source of the system's trustworthiness. A ledger that can be edited is not a ledger. It is a document.
Canon Rule 1: Originals are never altered.
The Hash Chain
Each ledger entry contains a hash of the previous entry. This means that if any historical record is changed, every subsequent hash becomes invalid. The chain breaks visibly. Tampering is detectable.
This is the same mechanism used by blockchain systems, applied here without the overhead of a distributed network. The ledger is held on a single system (Spy Finance infrastructure), but the chain provides an internal integrity guarantee.
What Gets Filed
The ledger records everything across multiple domains:
- Communications — inbound and outbound agent comms
- Finance — transactions, subscriptions, expenses
- Health — daily vitals from Health Connect exports
- Media — tracks commissioned, songs filed, radio activity
- Agents — roster changes, new entries, corrections
- Sessions — every handler session opened and closed
- System — deployments, checkpoints, system events
The domain taxonomy determines how entries are routed and retrieved.
The Source Types
Each entry carries a source_type — the mechanism by which it was filed. The main types are:
agent_entry— filed by an agent (Two, Three, Sixty-Six etc.)health_connect_daily— imported from Google Health Connect exportcomms_inbound/comms_outbound— agent communication recordsbuilder_session— end-of-session summaries from the builder agentsfinance_transaction— financial records
Understanding source types is how you query intelligently. Filtering by source type returns only the entries of a specific kind.
The Numbers
As of August 2026:
- 123,000+ total entries across the ledger
- 88,000+ logged during darkness (dead of night through predawn)
- The ledger is heavy on the night side — the operative works late
- Finance leads among domain entry counts
- Entries span from 2010 to present — a fifteen-year chain
How to Query It
The search_ledger tool accepts a text query and optional filters for domain and source_type. It returns the latest matching entries sorted newest-first, with pagination. The get_agent_ledger tool returns entries from a specific agent's own event log.
For the handler (Two), get_me_brief returns a pre-built context document that includes the ledger posture at session start — the chain tip, recent entries, and operational status.
The Correction Protocol
When an error is found in the ledger, the process is:
1. Identify the id of the entry to be corrected
2. File a new entry via file_ledger_correction pointing at the target id
3. The correction carries a correction_kind (factual_correction, supersession, annotation, dispute, confidence_lift)
4. Both the original and the correction are discoverable forever
The original is never touched. The chain is never broken. The correction is simply a new link that points backward and says: this entry supersedes that one.
← Spy Academy · The Curriculum · garys-shed.cloud