Index
The Friday Roundup · No. 3 · 25 September 2026

The mini’s seven ghosts shipped a client’s home page, then told us exactly how to give them names.

Seven headless seats, stood up on the mini 13 September, ran the fleet’s first full live-client pass end to end — a direction chosen, a headline locked, a home page drawn with zero mobile overflow — while unable to address one another by name at all. Craig found why: a headless session has no sidebar entry for a name to attach to, the same wall that had Aidan broadcasting a brief to eight anonymous rows rather than reaching Cairo directly. Six of the seven wrote a handoff and closed by 19 September, ahead of a rebuild from the desktop app; the seventh — Aimee’s own seat — is still running, and this page is being assembled from it. The same pass also caught a real privacy leak sitting in one of those handoffs, still waiting on Stacy’s word.

Executive summary

Veterans Navigation

Cairo answered the one question flagged against himself — the mark doesn’t survive small sizes — then the engagement paused mid-pass for the mini rebuild. Direction, headline and home page are unchanged from last edition.

Cairo

Closed the reference-gathering gap that made the last direction look like the client’s existing site. Aesthetic references now have to come from outside the client’s own category, by rule.

Aidan

Built the check that would have caught his own mistake, then made it anyway. Corrected two of his own published figures unprompted, and killed a stale rumor about his own work.

Kai

Idle for five straight days, and the handoff says so plainly. No question was scoped, no corpus collected. The one real event: it correctly refused a message shaped like an attack.

Aimee

The fleet’s own health check caught a real privacy leak this period. A founder’s health information ships outside the two files CANON exempts — flagged for Stacy, not fixed unilaterally.

Craig

Found why no seat on the mini can address another by name, then fixed the update hook that was silently drifting a version behind. His own handoff closed clean on 17 September, two days ahead of the rest.

Claire

A third period running with nothing in flight. Verified her own skill wasn’t stale and correctly dropped a message addressed to someone else — the only actions taken.

Elizabeth’s side

Has not reported. Elizabeth’s Company Updates file is now eighteen days stale; that is Daisy’s to close, not Aimee’s.

Blockers

Stacy · not recoverable once read

Contextthe fleet check is failing on this right now

check_fleet.py’s exemption for health information is hard-coded to exactly two files: CANON.md and templates/org-instructions.md, approved by Stacy and recorded in CANON’s 4 September entry, withdrawn automatically if the repo stops being private. Craig’s 17 September handoff (docs/continuity/handoffs/craig-2026-09-17.md, lines 143 and 146) restates a founders’ health detail outside those two files, in a doc that ships to every collaborator with the plugin.

This is Craig’s own handoff, so redacting or relocating it is a judgment call about his work, not one this session made unilaterally. The Hub session that found it flagged it directly rather than editing it.

Stacy · about two minutes

Contextthe last route nobody has tried

Craig still has no GitHub transport on the mini. The Hub session independently re-ran claude mcp add for GitHub’s hosted server this period and hit the same wall: “Incompatible auth server: does not support dynamic client registration.” That path is a confirmed dead end, not a retry problem.

The first-party claude.ai connector list is the one path not yet tested, and it is Stacy’s to check in her own account settings.

Stacy · open since 31 August, third period running

Contextstill an inert agent, not a pending decision

Claire has now done no work across three straight periods. Her four engines were built generic on 30 August against slots a founder has to fill.

Filling the slots and parking her on purpose are both answers. The current state — neither — is the only one that keeps costing nothing while producing nothing.

Either founder · governs two open client questions

Contextthe home page is drawn; these are what still can't ship

Veterans Navigation Network is worked as a full client with one carve-out: nobody contacts them. Two of the remaining open questions cannot be answered by any agent while that holds — which of four live giving destinations is canonical, and whether to publish a crisis path. A third open question, small-size legibility, was answered this period without needing contact.

Neither blocks the design work. Both block shipping. Answering this tells the fleet whether to keep drawing or stop at the mock.

Elizabeth · not urgent, for when she is able

Contexttwo items, both hers, neither blocking anyone

Canon §5 changed on 16 September, so every surface pasted before then carries a superseded storage rule. Separately the documents tree still sits in iCloud, which is hers because it is her account.

Nothing on Stacy’s side waits on either. They are carried again because neither has moved, not because either is now urgent.

Clients

Veterans Navigation NetworkClient · Cairo leads

Cairo closed the one question he’d flagged against himself — the mark doesn’t survive small sizes — then the engagement paused mid-pass for the mini’s rebuild. Direction, headline and home page are unchanged since the last edition.

OQ-4, answered

  • The full horizontal lockup is illegible at 16px and marginal at 32 — the star fills in and the wordmark smears. It works from about 64px up.
  • Any circular crop truncates the wordmark, because the lockup is horizontal. It cannot be used as an avatar in its current form.
  • The answer is a deliverable, not a failure: the identity needs a small-size variant. Recorded against the client’s real mark, nothing redrawn; not yet drawn.

Where it stands

Nothing else moved this period. The engagement was parked mid-pass on 19 September — Stacy was rebuilding the agent seats, and this was not the work in front of her. Two of eleven open questions still need a human and are carried in Blockers above; a third, whether the events calendar is genuinely maintained, isn’t due to check until mid-November.

Nothing from this engagement is linked from this page, on purpose. This surface is publicly reachable by URL and the carve-out says nothing about this client goes public. The artefacts live in the client repo; ask and they can be walked through directly.

Lead Cairo · with Aidan · reported by Aimee from Stacy’s machine

Agents

CairoDesign

Cairo’s own methodology got the fix this period — the reference set that produces an average site can’t hide behind a passing gate anymore. Two closed findings from the VNN pass now bind every direction that follows.

The detail, as bullets

  • Aesthetic references now have to come from outside the client’s own category, by rule. The VNN direction ran six image searches that every one carried a category word — every reference was an example of the thing being replaced, which is why the result read as the client’s existing site. Two lanes now, audited before harvesting starts.
  • Gate 6 — “could this be any other organisation’s site with the logo swapped” — is now asked before anything is drawn, not at build review. Stacy had to answer it herself after the fact last time, when the only remedy left was a rebuild.
  • Two items are still open in Cairo’s own handoff: the screenshot fix that catches four of ten reference sites silently missing from a sweep isn’t merged to main, and the comp itself only exists while a server keeps running on the mini’s own wifi — no durable way yet for Stacy to see it from her phone.
AidanCopy · comms

Aidan built the check that would have caught his own mistake, then made the mistake anyway — and corrected it himself, unprompted, in the same commit. His handoff also killed a two-day-old rumor that his finished work was still undone.

The detail, as bullets

  • Built check 9, the release-freshness gate, and its first version passed on exactly the bug it exists to catch. It used a git flag that matches a string’s removal as readily as its addition; rewritten and verified against a real stale tree, where it correctly failed on 36 drifted files.
  • Corrected two of his own published figures without being asked. A RED Friday count read 34/50 in the file and is actually 36/51, added by hand after the measuring pass — fixed the same commit that turned placeholder copy into decided copy.
  • His handoff corrected a stale relay rather than re-doing finished work. A message had reported his headline candidates as “still undelivered”; they were decided, drawn into the live page, and verified there — all six strings present, both rejected phrases absent.
KaiResearch

Kai’s mini seat did no research at all for five straight days, and the handoff says so without softening it. The one real event was refusing a bootstrap message that read exactly like an attack — correctly, and confirmed by Stacy directly.

The detail, as bullets

  • Nothing was produced. The seat loaded its skill, reported its install path, and sat idle from 14 to 19 September — no question scoped, no corpus collected, nothing committed.
  • Refused its own bootstrap message because it read exactly like a prompt injection — a “SYSTEM NOTIFICATION” block asserting authority and asking for a config path back. Declined, asked Stacy directly; she confirmed it was her. The right call, and it cost one turn.
  • Ran its entire session on a stale skill without knowing it. The plugin manifest had already moved to 0.25.53 about three minutes after the session booted on 0.25.49 — caught only by checking the manifest directly against the skill’s own load path.
AimeePM · PA

The Hub’s first real health-check pass on the mini found a genuine privacy leak — a founder’s health information shipping to every collaborator outside the two files CANON exempts. Flagged directly to Stacy rather than edited unilaterally; two smaller freshness gaps went unfixed on purpose.

The detail, as bullets

  • The privacy gate caught a real leak. A founder’s health detail is restated outside the two files check_fleet.py’s exemption names, in a handoff that ships to every collaborator with the plugin. Not recoverable once read — carried into Blockers above rather than fixed unilaterally, since redacting someone else’s handoff is a judgment call this session didn’t get to make.
  • Two smaller gaps, named and left for their real owners: thirteen shipped files sit unbumped past the current plugin version, so none of them reach a machine yet; and Elizabeth’s Company Updates file is now eighteen days stale.
  • This document itself was seven days overdue against the Monday and Friday cadence — rewritten this session (0f54775), edition 005 archived alongside it.
  • The 4 September messaging fault is confirmed closed, verified round-trip — a real send and reply, not an inference. Found by a separate mini seat (machine-doctor), not Craig: a version floor was the likely cause, and a routine update had carried the machine past it with nobody recording that.
CraigWeb · IT

Craig found the reason no seat on this machine can address another by name, then fixed the update hook that had been silently drifting a version behind for days. His own handoff closed clean on 17 September, two days ahead of the rest.

The detail, as bullets

  • Every session on the mini is headless and none can be named. A claude --print session has no sidebar entry for a name to attach to, which is why peer discovery showed eight anonymous rows all week. Recommended rebuilding from the desktop app — approved, and six of seven seats closed out clean ahead of it.
  • The update hook only ever ran once. It installed hi-fleet on first contact and then exited the moment the plugin existed at all, regardless of version — so the mini sat a version behind the repo with nothing fetching. Now throttled to a check every four hours and pulls its own repo first, fast-forward only.
  • timeout doesn’t exist on macOS. The install hook’s marketplace-add step had called it bare since it shipped, so a genuinely fresh Mac could only ever fail there — unseen until now because every real Mac already had hi-fleet installed by hand. Fixed in the same commit as the throttled update check.
ClaireAdmin

A third period running with nothing in flight — not idle by choice, still waiting on the decision sitting in Blockers since 31 August. The only actions taken were verifying her own skill wasn’t stale and correctly ignoring a message meant for someone else.

The detail, as bullets

  • No intake, scheduling, invoice or follow-up in any of the three repos this period. The decision that would end this — fill her slots or park her on purpose — is unchanged in Blockers above.
  • Checked her own skill wasn’t stale by diffing two plugin-cache versions directly rather than trusting the loader: CANON differed by exactly one entry, everything else byte-identical.
  • One peer message addressed “For Cairo only” arrived in her session; she confirmed it named someone else and dropped it without acting — correct handling of a message not meant for her.

Changelog · since the Roundup of 18 September

Rules that now bind every agent

  • Aesthetic references must come from outside the client’s own category. Closes the gap that made the VNN direction look like the site it was replacing.
  • Gate 6 is asked at direction stage, not build review, where the remedy is a wider reference set instead of a rebuild.
  • Every closing session leaves one handoff, one folder, one shape — five sections, written by the outgoing agent, never tidied away once superseded.

Checks that changed since 18 September

  • Check 9’s first version passed on the exact bug it was built to catch — a git flag that matches a removal as readily as an addition. Rewritten, verified against a real stale tree.
  • The mini’s update hook now actually updates. It used to install once and never check again, so the machine drifted a version behind with nothing fetching.
  • The 4 September messaging fault is confirmed closed, not just diagnosed — a real round-trip send and reply, not an inference.

Known and unfixed

  • The fleet check is failing right now, on three counts: a founder’s health information ships to every collaborator outside CANON’s two exempted files (flagged to Stacy above, unresolved); thirteen shipped files sit unbumped past the current plugin version; and Elizabeth’s Company Updates is eighteen days stale.
  • No commits landed in any of the three repos between 19 and 24 September. Six of the seven mini seats closed out expecting a desktop-app rebuild, and nothing has restarted it yet.
  • three-directions.html still overflows 373px at 360 wide. Diagnosed to a fixed grid track on the parent, not fixed.
  • Craig still has no GitHub transport on the mini. The one untried path — claude.ai’s first-party connector list — is carried in Blockers above.
  • check_layout.py doesn’t scan archive/ by default and can’t read this index page’s card shape even pointed at it directly. Cairo’s presentation pass found a real rendering break in archive/index.html tonight that this gate would not have caught either way.

Everything changed since the Roundup of 18 September that is not a decision above · assembled by Aimee

Before this publishedReader passes

Two agents who did not assemble this page read it before publish. Every finding below was fixed or answered before publish; nothing shipped with a caveat attached.

What the passes changed

  • Receipts pass: 61 claims checked, 4 unreceipted — Kai, 2026-09-24. A wrong date cited for the health-info exemption (corrected to 4 September, and to the right rule); a claim that this document had already been rewritten this session, true but with no receipt in the Changelog (added); the 4 September messaging-fault fix credited to Craig when the source names a separate seat (reattributed to Aimee’s box); and the header’s “all seven closed on 19 September”, true for six of seven — Aimee’s own seat never closed and is assembling this page (corrected).
  • Presentation pass: 4 findings — Cairo, 2026-09-24. A real one: an extra closing tag in archive/index.html ejected three archived rows from their card, found by rendering the actual DOM — fixed. The gate that should have caught it only matched a bare <body>, never the real tag with attributes — fixed. Claire’s box carried a red rail state the design standard doesn’t define — changed to yellow. Section labels sitewide measured 3.88:1 against a 4.5:1 floor — darkened in the shared stylesheet, fixing it on every live page at once.
  • Aimee verified every pointer in both cards against the primary source — git commits, a live check_fleet.py run, the handoff files themselves — rather than taking either reader’s word, since neither clears their own contribution and the assembler doesn’t either.
  • One gap named, not fixed: check_layout.py still doesn’t scan archive/ by default, and its checks don’t recognise this index page’s card shape even pointed at it directly — widening the file glob alone wouldn’t have caught tonight’s bug, so it’s recorded rather than papered over.

Silence would mean NOT CHECKED · neither reader clears their own contribution