Write down the open-decisions file's fixed shape and its permanent-number rule #35
Loading…
Reference in a new issue
No description provided.
Delete branch "fm/fm-ship-open-decisions-template"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
The captain set two rules on 2026-09-11. The open-decisions file keeps its current structure exactly. A decision number is never reused, renumbered or deleted: an answered decision keeps a one-line row in an answered table at the foot of the file, in numeric order, linking to its own answer document.
This change records those rules as a template beside the decision-hold-lifecycle skill, which is already loaded whenever an answer is recorded or routed, so a future session preserves the shape instead of redesigning it.
Why it is a PR now
This commit (
60c7cb2) sat on this machine's local main, never pushed. On the night of 09/23 it bundled itself into three other workers' branches, and each had to be rebased around it. Shipping it on its own ends that. It is a clean cherry-pick onto current main with content identical to the original, and the no-mistakes pipeline passed at6d694ce.Original commit message
The captain set two rules on 2026-09-11: the open-decisions file keeps its
current structure exactly, and a decision number is never reused,
renumbered or deleted - an answered decision keeps a one-line row in an
answered table at the foot of the file, in numeric order, linking to its
own answer document.
Record that as a template beside decision-hold-lifecycle, which is
already loaded when an answer is recorded or routed, so a future session
preserves the shape instead of redesigning it. Classify the new file for
the documentation audience check.
Open
Nothing. This is the firstmate repo, so there is no Plane story. After merge, this machine's local main fast-forwards through the normal fleet-sync path.