looking back

The live board answers what is happening right now, and the moment you look away the answer is gone. Two more pages read the same events after the fact, over a window you pick: 1 hour, 8 hours, 24 hours, or 7 days — the ceiling being the 7 days the server keeps.

History — what happened while I was out. The unit is not the tool call. Twenty edits to one file under one prompt is one thing that happened, so events are grouped into work blocks: one session, working on one task, uninterrupted. A block ends when the session goes quiet for longer than AGENTMASH_IDLE_MIN — the same silence after which the board stops claiming someone is working — or when a new prompt asks for something else. Blocks are cut into days — under the day the work started, so a block that ran to 00:24 doesn't print its times under the following morning; it is marked +1 instead. Opening a block shows the files it touched and how often. A busy week collapses roughly eighty-fold this way — 20,160 events became 240 blocks in the test that measures it — and only forty rows are in the page at once, with the rest behind show more. A 6,000-event week is 376 DOM nodes at rest, about 3,300 with every block on the page opened, and still under 7,500 with the whole week paged in and every one of the 120 blocks open: the timeline stays in the low thousands of nodes even in use, and the test asserts each of those three numbers rather than only the friendly one.

Collisions by place — where we keep landing on each other. The subject of this page is the place, not the people: rows are directories, ranked by collisions. A handoff is two adjacent edits to one file by different people; a handoff is a collision when the two edits fall inside AGENTMASH_IDLE_MIN of each other — that is, the second person arrived while the board still considered the first to be working. A file qualifies as contested on the weekly digest's clauses (the digest in digest/) but its volume floor: at least two people, and at least one collision among their edits. One edit each, a minute apart, is the collision an advisory warns about before the second edit, so it counts here however few edits it took; the digest, a week's report, still wants four. The sidebar's collisions badge counts the same files for the last hour, and collisions → right now lists them, so it never says there is a collision the page does not show. Time is the clause that carries the meaning. Forty edits by one person then forty by another is one handoff and no collision; two agents alternating thirty seconds apart for forty minutes is seventy-nine collisions. The same two people taking turns on that file across a week is also seventy-nine handoffs and no collisions — that is a shared module working as intended, and the view says so by leaving it out. Each row shows the typical gap between the colliding edits, so the number can be checked rather than believed. A zone that stays hot week after week is usually saying something about a seam in the code, not about the people who keep meeting in it.

The digest calls a collision anything inside 48 hours, because a report written once a week over a fixed seven days cannot honestly claim finer resolution. The dashboard is read against a window you pick, from an hour to a week, and has to rank inside it, so it uses the threshold the product already publishes for still at the keyboard. Same words, resolution set by the surface. The window you pick decides what you are looking at; it never decides what counts as a collision.

Both pages are read-only and fed by the same socket as the board, so switching between them never drops the live connection. Where a window can't be read in full — a very large room, or a server too old to have GET /events — the view says so rather than showing half a week as if it were all of it.