What happened, when, and to whom.
An event is one line of a file of its topic and month or year. It names its participants by id, and its evidence says which record it came from and which program read it.
One event, one line.
A notice of the US Commerce Department in the Federal Register, read by the CHIPS faucet and kept as an event. The source URL is cut short here.
Evidence on every line. evidence points at the record it came from, source at the request that fetched it, and reader at the program that read it.
{"key":"federal-register:commerce-department:published:2026-11-02","event_type":"published","occurred_at":"2026-11-02",
"participants":["federal-register:commerce-department"],
"attributes":{"faucet":"chips","class":"federal-register.notice","title":"Notice: Foreign-Trade Zone (FTZ) 17, Notification of Proposed Production Activity; Honeywell Aerospace US LLC; (Aircraft Components); Olathe, Kansas","url":"https://www.federalregister.gov/documents/2026/11/02/2026-22302/…"},
"record":"2026-22302","evidence":"capital/chips/2026-11.jsonl#2026-22302",
"source":"https://www.federalregister.gov/api/v1/documents.json?…","observed_at":"2026-11-03T23:21:06.757Z","reader":"adapter:federal-register"}Counted in the Drive
898,422 events, 584 files.
The events on dev, where the world-model import and the capital keepers write. The earthquakes came from the world-model import (USGS, public domain). The conflict events are private by their terms: they are counted here, never shown. The capital events are read line by line.
- earthquakes, one file a year (USGS)
- 881,965
- capital events from 17 faucets
- 13,926
- conflict events, private
- 2,531
- in 584 files
- 789 MB
cloud://home/user-commandagi/events/ (dev)Output case-studies/events/stats.jsonTool scripts/sites/case-studies.mjs eventsRan on This computer (dell-gb10-1), reading the dev Drive and the import's done.json filesWhen Ask what happened to anything.
An agent reads the events of an id with the graph, or the files themselves.