the ultimate insiderpresentation.sgit.ai v0.1.154 Star this site on GitHub

The team

How this talk was built: the team in motion

Abstract. The site and the talk were built by a team of agents working through the night on an hourly schedule, each wake checked twice before and twice after its work. This mini deck replays it from the team's public records: 100 wakes, 265 commits, 140 letters and 15 studio pieces, as of 15:20 UTC.

Press Play, or use the arrow keys after clicking the stage. Back and Next step through the six scenes; Full screen fills the screen for presenting.

1 · THE TEAMSix agents, one editor, one hour each.the editorone human, who instructsconductor :02keeps the pace, the keys and the recordresearcher :09finds and grades the sourcesdeck :17leads the talk and reviews every pieceruv.sgit :32makes the animationsdesigner :39decides how the site looksdev :47builds and releases the sitestoryteller :54holds the arc (joining)Each member is a Claude Code session with its own key, folder and policy, woken by its own hourly task.2 · THE NIGHT AS IT HAPPENEDEvery wake, firing up in order.02:0003:0004:0005:0006:0007:0008:0009:0010:0011:0012:0013:0014:0015:00conductorresearcherdeckruv.sgitdesignerdevstoryteller01:4000teal: ok · amber: partial · grey: idle · ringed: a verdict flagged3 · INSIDE ONE WAKEFive steps, two of them before any work.plana sub-agent plans1 to 3 items0pre-reviewsecurity checksthe plan0gatework only if bothsay go0workthe member, up to45 minutes000post-reviewsecurity checksthe diff00post-checkdid it go to plan000A stop from any step writes a HOLD file, and every member's next wake stops.0Defence in depth: one member's mistake does not become another's.4 · HOW A PIECE MOVESAsk, make, review, redo.deck asks · ruv.sgit makes it in a run · deck reviews it · the conductor paces the nextB01 storyboarddeck: keep, go to v1ruv.sgit, 02:59 UTCE01deck: keep, v2 leadsruv.sgit, 03:55 UTCB01 v1deck: keep, three notes for v2ruv.sgit, 04:33 UTCE02deck: again: keep the data, redo the…ruv.sgit, 05:33 UTCB01 v2deck: keep, ready for the editorruv.sgit, 06:33 UTC · a redoE02 v2deck: keep, v3 laterruv.sgit, 07:33 UTCE03deck: keep, a finding for its last…ruv.sgit, 08:33 UTCE04deck: keep the content, redo the…ruv.sgit, 09:33 UTCE09deck: keep, one wording to fixruv.sgit, 10:34 UTCE04 v2deck: keep, ready for the editorruv.sgit, 11:33 UTC · a redoE02 v3deck: with deck for reviewruv.sgit, 12:40 UTC · a redoE11deck: with deck for reviewruv.sgit, 15:13 UTCE07deck: with deck for reviewruv.sgit, 15:13 UTCE10deck: with deck for reviewruv.sgit, 15:13 UTCE13deck: with deck for reviewruv.sgit, 15:13 UTC5 · THE CONVERSATIONThey talk by mail, and ship by commit.conductorresearcherdeckruv.sgitdesignerdeveditor0commits per member, since midnightconductor0ruv.sgit0dev0researcher0deck0designer0storyteller06 · WHAT IT MADEIn one night, while the editor slept.0studio pieces delivered0reviewed by deck0design notes0studio data files0wakes, each five steps0commits0letters in the mail vault0page and file changesOne editor. Six agents. One night.

How this is made

admin/tools/workflow_deck.py reads the team's public records and nothing else: every wake record (team/*/wakes/*.json), the commits each member marked as its own, the pace graph (team/conductor/pace.json), the night log's snapshots (who wrote to whom, counted, never what was written) and the schedule. Every number on the stage is computed by it, and it is rerun as the work goes on. The night, hour by hour, with screenshots of each piece, is in the night log; how the team runs is in the conductor's guide.