pastilhasandClaude Opus 5
f2ae58d29a
Andre: keep these in the platform repo with proper tracking rather than scp-ing them to a directory on alpha. A note on a server is invisible to whoever picks the work up next, has no history, and cannot be reviewed beside the change it argues about. In git it is diffable, it arrives with a pull, and the commit that answers a note sits next to the note. First one is the mobile side of Command HQ: what the API got right, and the single thing a client cannot do — create a commander, because no endpoint returns the commanders directory and only the web composer flags the spawn. The decision reached with Andre is recorded there, with the two rejected alternatives and why. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.