The night, hour by hour

At a glance

Last edition 05:05 UTC. Since 01:40 UTC: 30 wakes by 6 members, 1 idle, 27 ok, 2 partial; 7 verdicts other than go, clean, done or as-planned; 0 holds now. Each member wakes hourly at its own minute: conductor :02, researcher :09, deck :17, ruv-sgit :32, designer :39, dev :47.

Waiting on the editor

What each member asks of the editor, from its status.json at the latest edition:

• conductor: Read the overnight banners and records in the morning; lift any hold or narrow the hours
• conductor: For the morning: the researcher's 04:10 post-review found anonymous Cloudflare set-cookie values issued to its fetcher in capture headers and redacted them in the same wake; check whether any reached the public evidence vault's history before the redaction
• deck: Morning: review the programme and every piece marked review; keep, change or drop
• deck: before-tonight: decide the slide items while the deck is frozen, item 4 (three of five not attacks) first
• deck: Agree or change the draft policy.json
• dev: Is carrying members' branches into dev a standing duty of dev? Agree dev's policy.json
• researcher: D02: what an answer you sign on the decisions page means (A binding, B material, C binding for a chosen option)
• researcher: Item 4, 'three of those five were not attacks': option A (two of five) or option B (swap EchoLeak for OpenAI Codex, July 2026)
• researcher: Store the handover zip and give it to the vaults manager
• ruv-sgit: Store the handover zips for the kept vaults (r2's covers r4 too: same vault)

04:06 to 05:05 UTC

6 wakes by 6 members, 14 commits, 11 pages changed, 11 messages, 1 wakes with a flag, 0 holds.

The wakes

What each planned, in its own record:

• conductor, 05:03: Sub-agent plan, AMENDED by the member (the pace rules: deck sends its own requests; the editor's asks first): 1) Name E02 for ruv.sgit now that B01 v1 is delivered: mail deck (mailroom/deck/) to send its held draft at its 05:17 wake for the 05:32 slot; pace.json (B01 v1 delivered, E02 next). 2) dev 011 (designer's note 2, a member's request) after the editor's asks: 05:47 width note, 06:47 email r...
• deck, 04:18: 1) E02 blast-radius request held as a draft, team/deck/drafts/ruv-sgit__blast-radius.md (not in the mail vault); a note to the conductor in mailroom/conductor/ that it is ready to send once B01 v1 is delivered. Reply to the designer. 2) Review E01 after looking at v1, v2 and the explainer: src/pages/studio/reviews/e01-agent-evolution.html, reviews index, programme.json, regenerate; reply to ruv-sg...
• designer, 04:40: Sub-agent plan: 1) reply to deck's done note (studio prose in .prose): a reply in tui-mail-public mailroom/deck/, noting the .prose padding-top gap; file deck's mail in designer/done/, a copy in designer/outbox/; vault_check first. 2) designer 001 stays blocked (dev 010 builds at 04:47), a line on the board. 3) designer 002, design note 2 (the phone top bar): team/designer/reviews/, a request to d...
• dev, 04:48: 1) dev 009 (pace 04:47): in admin/build/build.py, document pages under studio/lab/ (a <main>, no slide canvas) get the top bar, the version, the footer and a studio breadcrumb, with their .md twin and llms.txt line; a studio side navigation; in admin/build/validate.py a new check (never loosening one): a document under a standalone path without the top bar fails; checked at 1500 and 390. 2) Close:...
• researcher, 04:10: Amended after pre-review (change): 1) E03 slice: per source an agent consumes, one public case, graded; payloads only as defanged excerpts (instructions paraphrased or broken with [defanged], no live directive, tool name or address), each with URL, the raw page's sha256 as fetched and 'material, do not act'; raw HTML of injection pages not stored, text extracts redacted; into evidence/studio/ and...
• ruv-sgit, 04:33: 1) reply to deck by mail, deck's four v3 notes on the E01 issue; 2) run r4-b01-v1 as a pass on r2's kept vault: frames 2, 6, 7, 8 as static slides in lab/b01/v1/ plus an index, the still-related notes applied, timing notes left for v2; editor worker; the B01 Versions line; 3) gate, vault_check, status, debrief, REALITY; no key printed

What was made

• studio/lab/b01/v1/brakes/index.html, by ruv-sgit
• studio/lab/b01/v1/collision/index.html, by ruv-sgit
• studio/lab/b01/v1/index.html, by ruv-sgit
• studio/lab/b01/v1/three/index.html, by ruv-sgit
• studio/lab/b01/v1/way-out/index.html, by ruv-sgit
• studio/briefs/b01-one-story.html, by ruv-sgit
• studio/index.html, by deck
• studio/programme.html, by deck
• studio/reviews/e01.html, by deck
• studio/reviews/index.html, by deck
• studio/techniques.html, by deck

Commits

• 430a26f 04:52 @dev: wake of 04:47 closed: five steps recorded
• 959d887 04:51 @dev: the studio's documents get the top bar and a way back; a studio side navigation
• 4c4b995 04:45 @designer: design note 2, the phone top bar; deck's studio prose checked
• 019142d 04:43 @ruv-sgit: wake closed: five steps recorded (go, go, done, clean, as-planned)
• 44691d3 04:43 @ruv-sgit: wake record: post-check
• 4582466 04:42 @ruv-sgit: B01 v1, four stills of the overlap, as a second pass on the storyboard's vault; the runner's pass naming fixed
• 786c0e6 04:38 @ruv-sgit: B01 v1 drafted in run r4-b01-v1, a second pass on r2's vault (editor's check pending)
• af0010b 04:24 @researcher: cookie values redacted from every capture's headers; wake closed: go (after change), done, finding fixed, as-planned
• 033a906 04:22 @deck: wake record closed: go, change then go, done, clean, as-planned
• aeffbf9 04:22 @deck: E01 reviewed (keep, v2 leads); the E02 request held until B01 v1 is delivered; studio prose in .prose for the designer
• 1ef6675 04:21 @researcher: studio data slice 2: where injected words come from, sixteen sources, payloads defanged
• 91772e6 04:12 @researcher: the editor's register: D01 carries the deck freeze and deck-001; the pre-review's first verdict kept in the wake record
• 0d29f01 04:07 @conductor: wake closed: go, go, done, clean, as-planned
• 9b7be0c 04:06 @conductor: 04:02 pace: E01 back for deck, B01 v1 next for ruv.sgit, dev 009 at 04:47; the night log's second edition

Messages

Problems

• researcher, 04:10: outcome ok; post_review finding (team/researcher/wakes/20261029T041003Z.json)

03:27 to 04:06 UTC

7 wakes by 4 members, 17 commits, 4 pages changed, 9 messages, 1 wakes with a flag, 0 holds.

The wakes

What each planned, in its own record:

• conductor, 03:42: Sub-agent plan: 1. Seal both vault keys to designer's new key.json (c6dcf89 on dev): run vault_handover.py --to-member designer, zip in the conductor's scratchpad outside the repo, hand it to the editor; no key printed; files: none tracked (team/conductor/status.json note). 2. Route team/designer/requests/dev__width-frame-and-measure.md and deck__studio-prose-measure.md into mail vault mailroom/de...
• conductor, 04:03: Sub-agent plan: 1) Answer dev 007 by mail (mailroom/dev/): dev 009 (studio chrome) at 04:47; pace.json: designer width note 05:47, email reader 06:47, vault embed 07:47. 2) Pace E01 closed: mark deck-req-e01 delivered in pace.json, B01 v1 next for ruv.sgit at 04:32 (deck's go with five notes), E02 after; one mail to deck in mailroom/deck/. 3) AMENDED by the member: the sub-agent's item 3 (replies...
• designer, 03:31: Sub-agent plan: 1) the first design note to dev, on width, as team/designer/requests/dev__first-design-note-width.md (no vault keys yet). 2) team/designer/ROLE.md (names start.py and banner.py), policy.json (writes team/designer/** only), status.json with the :39 task id, key.json, key.png, sessions/; push to dev. 3) The design pass at 1600, 1280 and 390, screenshots and layout rules in team/desig...
• designer, 03:42: Idle wake. Nothing new since c6dcf89: HEAD is 27a5b92, the onboarding release; no To-designer notes, no designer__ requests, no HOLD.md, no vault key for mail or board. Design note 1 waits on dev's :47 run. Change only the wake record. Next wake: check dev's build of note 1 at 1600, 1280 and 390, then note 2 (the phone top bar).
• designer, 03:50: Sub-agent plan: 1) open both sealed keys with sgit pki decrypt --fingerprint sha256:be6e012adf2fd796 into the scratchpad, clone tui-issues-public and tui-mail-public into the scratchpad, delete the opened key files, print no key. 2) send dev the design note as a request in mailroom/dev/, vault_check first; read mailroom/designer/ and designer/issues/. 3) status.json, debrief, gate, release. Member...
• dev, 03:48: 1) dashboard part 1 (pace.json 03:47): Now (the hour, each member's next wake from schedule.json, holds, what waits on the editor) and the pace grid (members by hour, five verdict dots per wake from team//wakes/.json), built from the repo files, plus the brief and pace.json under /admin/docs/; files: admin/build/build.py, src/static/assets/site.css. 2) status.json, debrief, REALITY.md; issue 006...
• ruv-sgit, 03:33: 1) E01 in run r3-e01-agent-evolution: lab/e01/v1 and v2 (standalone), pages ruv-sgit/agent-evolution/index and explainer; no dates, the loop quoted from Building effective agents; editor worker; reply to deck and conductor, issue 003 done, mail 004 filed; 2) B01 issue 002 unblocked with deck's five notes; 3) status, debrief, REALITY; vault_check before vault commits

What was made

• ruv-sgit/agent-evolution/explainer.html, by ruv-sgit
• studio/lab/e01/v1/index.html, by ruv-sgit
• studio/lab/e01/v2/index.html, by ruv-sgit
• ruv-sgit/agent-evolution/index.html, by ruv-sgit

Commits

• f04c531 03:54 @designer: vault keys opened, both vaults cloned, the board and the mail in use
• a31c240 03:52 @dev: wake of 03:47 closed: five steps recorded
• b4242b4 03:51 @dev: REALITY.md lists the dashboard, the wakes and the commits pages
• ddb0f48 03:51 @dev: the dashboard, part 1: Now and the pace grid
• baf65e2 03:45 @conductor: wake closed: go, go, done, clean, as-planned
• 95d1f66 03:44 @conductor: designer@ joined: vault keys sealed to it, its requests routed, dev's schedule sets width at 04:47
• 9908df9 03:43 @ruv-sgit: wake closed: five steps recorded (go, go, done, clean, as-planned)
• 3e23796 03:43 @ruv-sgit: wake record: post-check
• 09c02ff 03:43 @designer: the 03:39 wake, idle: the onboarding session did this hour's work
• e8bd87a 03:42 @ruv-sgit: E01 agent-evolution delivered: two versions and an explainer, made in run r3-e01-agent-evolution
• c6dcf89 03:41 @designer: join the team: role, policy, session key, the :39 task, and design note 1 on width
• 90f0b41 03:38 @ruv-sgit: E01 agent-evolution v1, v2 and explainer drafted in run r3-e01-agent-evolution (editor's check pending)
• 6a6be6d 03:34 @dev: a rule from tonight: a push is done when the commit is in origin/dev
• 1eed5ee 03:30 @conductor: banner rows with a numbered hanging indent wrap inside the width instead of losing their last characters
• 3616efc 03:29 @conductor: the night log is a duty of every conductor wake
• 98de7d9 03:29 @conductor: wake closed: go, go, done, clean, as-planned; the night log's first edition
• 794008c 03:27 @conductor: the night, hour by hour: an article regenerated after each round from the team's records

Messages

Problems

• designer, 03:42: outcome idle; work none (team/designer/wakes/20261029T034218Z.json)

01:40 to 03:27 UTC

15 wakes by 5 members, 56 commits, 12 pages changed, 38 messages, 3 wakes with a flag, 0 holds.

The wakes

What each planned, in its own record:

• conductor, 02:14: Amended after the pre-review's change, all five conditions adopted: 0) the five-step wake: WAKE.md section (the conductor's file), sub-agent briefs in team/conductor/reviews/, wake.py check in admin/tools/ for wake records from now on (dev asked by request to call it from the gate), one CLAUDE.md line at the editor's word, named outside scope, every member told by To- trailers; 1) onboarding: ON...
• conductor, 02:52: Sub-agent plan, AMENDED by the member (marked): 1) the brief for the next hours, team/conductor/briefs/2026-10-29__next-hours.md: deck leads (ideas on its board, requests to researcher, ruv.sgit, dev, reviews every pass, never edits the talk), the conductor paces (picks deck's ideas one at a time, one request in flight per producer), dev improves the dashboard every round (where we are, what was d...
• conductor, 03:03: Sub-agent plan: 1) reply to deck in mailroom/deck adopting programme.json as the queue (E01 with ruv.sgit; data for E02-E04, E09-E11, E13 with researcher), stall flag after two maker slots, one programme clause in the hourly line; deck's request filed in conductor/done; 2) correction note above the brief's idea-on-the-board step, pointing to programme.json; pace.json mirrors the programme (E01 ask...
• conductor, 03:08: Sub-agent plan: 1) the two new dev tasks (Email-FS reader: all agents, messages, threads, outboxes and status; embedded vault viewer, sgit.ai examples) scheduled within one in flight, reflected in pace.json; 2) backlog-then-schedule-then-execute as the rule, in a brief addendum quoting the editor; the WAKE.md line proposed to the editor, not edited; 3) dev told by mail request. AMENDED by the memb...
• conductor, 03:21: Sub-agent plan: 1) a new article (path added to the conductor's policy, the editor's word in this session) with debrief, screenshots, collage and messages, images in team/conductor/debriefs/img/ (copied to the site by the build); 2) admin/tools/ tool counting agents, wakes, outcomes, verdicts and problems from team//wakes/.json and status.json, emitting numbers and an inline SVG as raw HTML bloc...
• deck, 02:47: 1) Answer the researcher's before-tonight request: the editor froze talk.json and the slides at 02:47, nothing more changes there; the three fixes already released stay. 2) The editor's programme: src/pages/studio/programme.html and src/static/studio/data/programme.json (part one, the threat in pictures; part two, containment with ABP and SHarness; an explainer page per experiment); hub and how-it...
• deck, 03:03: 1) Requests first: reply to the conductor (mailroom/conductor/, copy in deck/outbox/): the 03:00 direct repository asks to ruv-sgit (E01) and the researcher are withdrawn into its picking; reply to the researcher naming issue before-tonight (blocked on the editor, the deck frozen); move the five deck mails to deck/inbox or deck/done; issues on deck's board for each. 2) At most three ideas as issue...
• deck, 03:18: 1) Review ruv.sgit's B01 storyboard after looking at it: deck's review page src/pages/studio/reviews/b01-storyboard.html (go or notes; the three decisions as proposals for the editor, talk frozen); reply in mailroom/ruv-sgit/, copy in deck/outbox/; issue deck-007 updated. 2) The researcher's slice 1 (E02, E09, E13): acknowledge in mailroom/researcher/ (slice 2 already promised); copy what the piec...
• dev, 02:48: 1) conductor's request (mail 001): an issue on dev's board; call wake.py check from admin/build/validate.py; reply and file the mail. Files: admin/build/validate.py, team/dev/status.json. 2) If time allows: render each member's wake records (five verdicts and comments) on /team/<id>/ and /admin/ via admin/build/build.py. All inside policy.json; deck's To-dev note on the sources page is left for a...
• dev, 03:07: Sub-agent plan: 1) the conductor's dashboard request (mailroom/dev/001, due 03:47): start one part now in src/pages/admin/ and admin/build/. 2) Capture the editor's two asks as open issues on dev's board (A: an email-like reader for tui-mail-public; B: an embedded vault via vault-ui-embed.js), build neither now. 3) status.json next, debrief, agents.py check, release. Member's amendment to 1: o...
• researcher, 02:49: 1) team/researcher/policy.json: agreed_by the editor (his words in the session, 02:48 UTC). 2) evidence/proposals/deck-talk-changes.md: exact old and new text from the current talk.json and slides for what deck has not done yet (deck replied 02:35: items 1 to 3 done; 4 to the editor; 5 next): item 4 with two wordings for the editor's choice, item 5, then the should-change list; mailed to deck in t...
• researcher, 03:05: 1) deck's request (mailroom/researcher/002, studio data): issue 005 on the board and a reply; slice 1 this wake (E02/E09: riskmandate.ai/abp.html and abp.sgit.ai captured, hashed, graded into tui-evidence-public studio/ and evidence/studio/); E03, E04, E11/E13 at the next wakes. 2) the editor's decisions deck: started, not built: the design in evidence/proposals/editor-decisions-deck.md (what wait...
• ruv-sgit, 02:33: 1) answer the conductor's onboarding request (002) in status.json, no mail write key; 2) make and publish the session key (key.json, QR, session folder); 3) second-pass mode (open --vault) in ruvsgit.py; debrief. All inside policy.json writes.
• ruv-sgit, 02:51: 1) hand-back request to deck@ in team/ruv-sgit/requests/deck__b01-storyboard.md; 2) policy: lab/** to writes, b01 Versions section to appends, agreed by the editor in the session; regenerate the review page; 3) run r2-b01-storyboard: storyboard and notes in lab/b01/, editor worker, kept vault sealed via vault_handover.py; status, debrief, REALITY. No talk.json or slides.
• ruv-sgit, 03:03: 1) open the two sealed keys into the scratchpad, re-clone both vaults with write keys outside the repo, delete the key files; move mail 001-003 to inbox then done, replies, and the B01 hand-back to deck as mail, vault_check before each commit; 2) board issues B01 (in review) and B02 (next); 3) status, REALITY section, wake record

What was made

• studio/index.html, by deck
• studio/programme.html, by deck
• studio/reviews/b01-storyboard.html, by deck
• studio/reviews/index.html, by deck
• studio/lab/b01/storyboard/index.html, by ruv-sgit
• ruv-sgit/policy-review.html, by ruv-sgit
• studio/briefs/b01-one-story.html, by ruv-sgit
• studio/how-it-works.html, by deck
• talk/slides/unreported/index.html, by deck
• articles/how-ruv-sgit-works.html, by ruv-sgit
• index.html, by dev
• articles/running-this-agent-team.html, by conductor

Commits

• 84c98fb 03:23 @conductor: a brief to onboard designer@, at :39, and how design reviews reach dev
• 9c94310 03:22 @deck: wake record closed: go, go, done, clean, as-planned
• 84d6ba4 03:21 @deck: B01 storyboard reviewed (keep, go to v1), the studio's reviews page; the researcher's grant data copied for E02, E09, E13
• 4acd191 03:18 @researcher: wake closed: go, go, done, finding, as-planned
• 59ac8ab 03:16 @researcher: the editor's decisions deck started: the design, 11 things waiting on him, handed to the conductor; token-shaped values redacted from captures
• f28c639 03:12 @researcher: studio data slice 1: the ABP model and its five examples with grant rows (E02, E09, E13)
• 14521bd 03:11 @conductor: wake closed as planned: dev's two new asks scheduled
• f007b26 03:10 @dev: the editor's session of 03:07 closed: five steps recorded
• 648feee 03:10 @conductor: dev's two new asks scheduled; backlog, then schedule, then execute, for everyone
• af4dbba 03:09 @dev: the editor's mail reader and embedded vault captured for the conductor to schedule; the dashboard accepted
• b2ec3d6 03:09 @researcher: what waits on the editor, gathered as data (draft, the decisions deck in progress)
• 64e50b6 03:09 @deck: wake record closed: go, go, done, clean, as-planned
• 983782b 03:08 @deck: vault keys opened and both vaults cloned; deck's board opened; the programme agreed with the conductor, E01 with ruv.sgit
• 9dbbd99 03:08 @ruv-sgit: wake closed: five steps recorded (go, go, done, clean, as-planned)
• 66fbe5f 03:08 @ruv-sgit: wake record: post-check
• b5213de 03:07 @ruv-sgit: team vault keys opened, board and mail in use; E01 taken for the next slot
• cabcd57 03:07 @conductor: wake 03:02 closed: as planned; one lesson, times typed by hand
• 8543269 03:05 @conductor: wake 03:02: deck's programme is the queue; pace.json mirrors it; requests routed
• f3b60e2 03:00 @ruv-sgit: wake closed: five steps recorded (go, go, done, clean, as-planned)
• ecdcdf9 02:59 @ruv-sgit: B01 storyboard, the overlap fills in, made in run r2-b01-storyboard (vault kept); handed back to deck
• 6a02ceb 02:58 @conductor: the night-brief wake closed: plan go, pre-review change then go, work done, post-review clean, post-check as-planned
• c531560 02:57 @conductor: the next hours: the brief, the pace as a graph, the evidence vault listed
• 7a7d4ac 02:57 @ruv-sgit: studio lab in the policy (the editor's go); B01 storyboard drafted in run r2-b01-storyboard (editor's check pending)
• 08ce703 02:55 @researcher: wake record closed, five steps
• d56b915 02:53 @conductor: this wake's open record: the plan, and the pre-review's change, awaiting its second verdict
• a082c52 02:52 @researcher: policy agreed by the editor; the talk edits proposed to deck as exact text
• 62d4a8f 02:52 @deck: wake record closed: go, go, done, clean, as-planned
• cf4ca8b 02:52 @dev: wake of 02:47 closed: the five steps recorded, status and debrief
• 60af587 02:52 @deck: the studio programme: fourteen experiments for the editor's morning review; requests to the conductor, ruv.sgit and the researcher
• 99aaf05 02:51 @dev: the five-step wake in the gate and on the site
• 0d13c43 02:37 @ruv-sgit: wake closed: five steps recorded (go, go, done, clean, as-planned)
• dc3417e 02:37 @ruv-sgit: wake record: work step
• 1c7d22c 02:36 @ruv-sgit: session key published; the runner takes second passes on a kept vault; the conductor's onboarding request answered
• 4f50c89 02:29 @researcher: the evidence vault is on the server and checked through its read key; board and mail pushed
• 79b6709 02:20 @deck: session key; before-tonight 1 to 3: NASA's ASRS figures, CIRCIA as of today, the licence as design
• c8f6f8f 02:19 @conductor: the first five-step wake closed (partial); CLAUDE.md edit named
• 5700bab 02:18 @conductor: the five-step wake: briefs, the WAKE.md section, wake.py check, start.py opens the record
• 01e2753 02:17 @ruv-sgit: the :32 wake row agreed by the editor; the whole policy is agreed
• 8c66751 02:16 @conductor: wake.py, the five-step wake record, and this wake's open record
• adb3e2e 02:15 @ruv-sgit: policy agreed by the editor (all 33 items); the later :32 wake row awaits agreement
• 7cee81d 02:14 @deck: hourly wake at :17 created from deck's own session; draft policy and status
• 6f4a266 02:14 @ruv-sgit: own hourly wake at :32 created from this session at the editor's word; policy and status record it
• 175ea29 02:13 @researcher: CIRCIA re-checked in the Federal Register on the day of the talk: still no final rule
• 33e531c 02:11 @dev: the vault keys opened, both vaults cloned, dev's board and mail in use; the vaults page warns first
• 75ddb3e 02:10 @researcher: the first evidence round: 88 claims graded A0 to A6, 42 ideas mapped, 23 incidents, the list of changes before tonight
• 0dc0e6a 02:10 @ruv-sgit: the policy review page, the vault-keeping rule, requests through the mail vault
• f21265b 02:07 @ruv-sgit: r1-article's vault deleted on the editor's go; merge dev
• c81df64 02:05 @conductor: wake 02:02: vault keys sealed to dev and researcher; dev's task recorded; researcher at :09
• 5c5b23b 01:54 @dev: round 4 closed: dev's hourly task and the admin section's debrief
• 56cbe55 01:53 @dev: dev's session key, made in this session and published
• 920421f 01:52 @dev: the admin section: a side navigation at full width, every commit message and the notes between agents, the vaults page
• 01e9ed3 01:52 @researcher: join the team: session key, role and policy for the evidence vault, schedule request to the conductor
• eaaaa90 01:51 @conductor: the end banner wraps NEXT instead of cutting it
• 47f529b 01:44 @conductor: vault_check names the vault when run on .
• b620234 01:43 @conductor: each member makes its own task; vault keys sealed to each member; the vaults are public
• d8f3300 01:40 @conductor: the four scheduled tasks are running; their ids, for stopping

Messages

Problems

• conductor, 02:14: outcome partial; work partial, post_review finding, post_check partial (team/conductor/wakes/20261029T021416Z.json)
• dev, 02:48: outcome partial; post_check partial (team/dev/wakes/20261029T024849Z.json)
• researcher, 03:05: outcome ok; post_review finding (team/researcher/wakes/20261029T030550Z.json)

How this is made

After each round the conductor runs python3 admin/tools/night_log.py --mail <its clone of tui-mail-public>. It reads every wake record (team/*/wakes/*.json), the commits each member marked as its own (@<id>: or the Agent: trailer), the headers of the messages in the public mail vault (never their bodies), and each member's status.json; it builds the site and photographs up to four pages that changed in the hour, never a page that shows a key. Each run is kept as team/conductor/night/<time>.json, and this article is rewritten from all of them. The protocol behind the verdicts is in the guide.