Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.
| Email verification, password reset, and Git for AI scale positioning | 1 | -- Append-only log of every event published on the bus. Ids are |
| 2 | -- time-sortable, so ordering by id is ordering by time. | |
| 3 | CREATE TABLE events ( | |
| 4 | id TEXT PRIMARY KEY, | |
| 5 | type TEXT NOT NULL, | |
| 6 | source TEXT NOT NULL, | |
| Events service in Rust, with RFC 3339 times and accurate push events | 7 | -- RFC 3339 UTC. |
| 8 | time TEXT NOT NULL, | |
| Email verification, password reset, and Git for AI scale positioning | 9 | repo_id TEXT, |
| 10 | actor TEXT, | |
| Events service in Rust, with RFC 3339 times and accurate push events | 11 | -- JSON. |
| Email verification, password reset, and Git for AI scale positioning | 12 | data TEXT NOT NULL |
| 13 | ); | |
| 14 | CREATE INDEX events_repo ON events (repo_id, id); |
This file's history is long; its oldest lines are credited to the oldest commit read.