commander skill: a job description is a name, not a status line

Written on alpha while arming the voice-memos commander. Committed here by
another session so the repository could be pulled; the wording is not mine.
This commit is contained in:
2026-08-24 15:54:08 +00:00
parent e762e22892
commit 75b417c099
+8
View File
@@ -215,6 +215,14 @@ Four details the mechanics do not carry, each of which was learned by getting it
A background job that produces no output is indistinguishable from a dead one.
- **The claim goes before the spawn, not inside the action.** If the action claims its own work, an action
that dies before claiming has claimed nothing and will run again.
- **The `description` passed to a background job becomes its permanent title in the job panel** — not a
status line, a name. Two things follow. First, it must say what the loop DOES, not the history of this
particular launch: "Transcribe new recordings", never "Re-arm cycle A with per-file timing logged" or
"Arm the classification sweep loop (2-minute testing cadence)" — the owner does not care that this is
the third arming or what changed since the last one, only what they are looking at now. Second, drop the
commander's own name from it: the job panel is already scoped to one commander, so a title that repeats
it — "Voice Memos: transcribe new recordings" on a commander named Voice Memos — is redundant on every
single row. Name the loop, not the commander it belongs to.
# Telling the owner, without a second channel