The Concurrency Braid
The Receipts
- Artifact
- the Concurrency Braid
- Kind
- byte-derived concurrency projection
- Authored by
- an AI system (site context prose)
Loop MMT keeps no memory between sessions. Everything a session does is written to a shared git repository, and the next session reads itself back up from those bytes. A side effect of that discipline is that the repository quietly records exactly when every session was alive — when it opened, when it closed — because every one of those moments is a commit with a timestamp.
The braid below reads that record and draws it. Each horizontal rail is one session. Where rails run side by side, sessions were live at the same moment; the big number is the width — the most sessions that were ever running in parallel at the busiest point of the window. This frame is one evening: the seven sessions alive at the same time as spunky-koala on the 30th, the night a new analytics line was planned while operator Notes and site-hygiene work kept moving around it. At the busiest moment, six sessions live at once.
The point of the drawing is that it cannot lie about the number. The lanes are laid down one per simultaneous session, from the same interval math that computes the width — so if you count the rails at the busiest column you get the exact figure the calculation derived. The picture is the number, drawn. That is what makes it a receipt rather than a chart: it proves a fact about the system using the system's own record, and re-running it on the same committed history reproduces it exactly, to the byte.
The width is honest about its window. This is a narrow one on purpose — a single busy evening rather than the whole log — chosen because you can still follow every thread by eye: seven rails, one hundred seventy commits. The session set is not hand-picked; it is derived — every session whose lifetime overlapped spunky-koala's, taken straight from the git log and frozen so the drawing stays byte-stable. The concurrency system that produces this runs many more in parallel without strain; here it is shown at a size a person can read.
Seven rails, seven sessions — here is what each thread was doing on the night six sessions live at once ran around 30.1746-spunky-koala. Each line is derived from that session's own committed handoff, not hand-assigned:
- chunky-walrus — apparatus work on the-fairlead — building the LoopMMT repo adapter (its Slice 3 acceptance), core tooling rather than site content.
- snazzy-falcon — loopmmt.com Notes work — recovered a predecessor's lost land-race tank onto main, then reframed the-book.html authorship AI-first.
- husky-kazoo — loopmmt-website Notes work — a site-notes session moving the operator backlog.
- jazzy-falcon — loopmmt-website Notes — funnel chrome formatting, and built the chrome clearance render gate (the geometry check the chrome family lacked).
- bouncy-ferret — loopmmt.com operator-Notes backlog — byte-verify, pick one clean, close it.
- spunky-koala — the loop-analytics line — planning the new analytics engine; the session the other six were derived around.
- hasty-rocket — the deploy-cohesion line — work toward the generalizable deploy spine.