Fig 1A moment on my Mac, all the way to the glass
Claude CodeBridgeMindLinkBoardhooks: settingshooksevery ~4 sPOST /hook20 µs, p95 27Turn Mac awake off✓00the mood onlytests failed5 acts, weighted✓0done4 acts, weighted✓060 s apartholds its last act✓010 min apartholds its last act✓0an act?or nothing✓00nothing0mark goneheartbeatevery 15 slines down0.52-2.74 mslines down: settings✓00not sent0clock setplays itan act, 2 to 9 s✓00played0droppeda tapevery 60-240 smood onlytestsdonemarkmarkheldheldlatelye <act>taphhello
Click a step to read it, open the ones with a window, click a dot to follow it.

A quarter of an hour of one Claude Code session at work, simulated: 224 hooks reach the bridge, and only 10 of them are news for Sage's mind (a test run that finished, or Claude stopping); the rest only keep the mood. The mind plays 3 of those 10: it celebrates at most once in ten minutes and reacts to a failing test at most once a minute, however often they come, so 7 of the 9 finishes play nothing. An act's line is on the link 8.1 ms after its hook fired, almost all of it the hook command starting curl (97 ms over Wi-Fi, whose wait for the next beacon is assumed); then the board walks to idle and plays it, 4.6 s at the median. Put Claude in a fix loop and 37 failing test runs play 10 acts. Put my Mac to sleep for two minutes and 7 heartbeats are never sent. The heartbeat that waited finds the board more than a minute alone, and it plays hello. Click hooks to choose what Claude is doing, the switch on POST /hook to put my Mac to sleep, and lines down to change the link.
tool callstests failedfinishesheartbeatstapsmarkscame out failedthe one you follow