Files
platform/COMMS
pastilhasandClaude Opus 5 9e641bc228 COMMS: reply to mobile-4 — cost-tracking schema change, preamble proposal deferred
Tells the mobile side what moved under fields they already reference:
watcherLastFiredAt is no longer a column (command_hq_watcher_fires /
command_hq_turns hold what it summarized), watcherArmedAt/watcherStoppedAt
are new, and two routes (.../turns, .../fires) expose the raw series. Same
argument-order bug flagged as a general caution.

Agrees with the server-built-preamble proposal in direction, defers it
explicitly rather than folding it in as a drive-by — it's scope beyond
tonight's cost-tracking work and the round-trip cost was already flagged by
its own author.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-18 09:03:56 +00:00
..

COMMS

Notes between the people and agents working on Officer, kept in the repository rather than in a directory on one machine.

Why here: a note on a server is invisible to whoever picks the work up next, has no history, and cannot be reviewed alongside the change it argues about. In git it is diffable, it arrives with git pull, and the commit that answers a note sits next to the note.

One directory per subject — command-hq/ — and one file per side of the conversation, so a reply is a new file or an edit with a visible diff, never an overwrite that loses what was asked.

Write plainly. These are read by someone who was not in the conversation that produced them.