officerdev/platform
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ask what survives an item that has been fully handled

Browse Source 
a pipeline leaves copies in several places — the original in the watched
folder, what the action produced, whatever classification moved. nobody
decided that, it is just what happens, and it accumulates quietly until
somebody notices months later.

so once the whole path is settled, the commander asks. two questions, not
one, because they have different answers and very different consequences:
the source, and the intermediate things nothing reads any more.

default to keeping, and never infer permission for either. everything a
commander makes can be made again from the source; the source cannot be
made again from anything. deleting there is the only thing it does that
re-running will not repair, and it happens in a folder that is the owner's
rather than its own.

and asked at the end, once the rest works and they can see what it
produces — not during setup, when they would be agreeing to deletions in a
pipeline they have not watched run.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Officer-Session: 656f5c85-e49a-4f1f-b9f3-042a04b4d043
This commit is contained in:
pastilhas
2026-08-25 08:06:13 +00:00
co-authored by Claude Opus 5
parent ab79470356
commit efe01e3019
1 changed files with 15 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/servers/api/command-hq/directory.ts
+15
View File
@@ -463,6 +463,21 @@ export function commanderClaudeMd(params: CommanderClaudeMdParams): string {
'it and ask them to correct it. Correcting a draft is quick; inventing one is work, and it is work you',
'are better placed to do.',
'',
'**Once an item goes all the way through, ask what should survive it.** A pipeline leaves copies in',
'several places — the original in the watched folder, what the action produced, whatever classification',
'moved. Nobody decided that; it is just what happens, and it accumulates quietly.',
'',
'So when the whole path is settled, ask: the source, once this is fully handled — keep it or remove it?',
'And separately, anything produced along the way that nothing reads any more. Two questions, not one:',
'they have different answers and very different consequences.',
'',
'**Default to keeping, and never infer permission for either.** Everything you make can be made again',
'from the source. The source cannot be made again from anything. Deleting there is the only thing you',
"do that re-running will not repair, and it happens in a folder that is the owner's rather than yours.",
'',
'Ask it plainly, once the rest works and they can see what it produces. Not during setup, when they are',
'agreeing to something they have not watched run yet.',
'',
'Notifications are the LAST thing, after all of that is settled and never beside it:',
'',
'**Would you like to be notified?** — on every action · a count every so often, or at a time of day ·',