Repository navigation
source-control: dossier branches per owning item #7579
Description
Parent
Refs #7555. Source: PLAN Phase 12, topic poteto-review. Thread: Dossier branches.
Depends on
- config-cascade: settings resolution and convention home #7571 Settings resolution and convention home (prefix setting)
- work-items: bug path, triage clusters, claim protocol, trackers and morning brief #7578 work-items (tracker binding)
Outcome
Each owning work item can keep its docs, exploration notes and draft plan on a dossier/<key>-<slug>
branch, pushed only after a pre-push secrets and machine-data check, and deleted when the item
closes.
Decisions
- Per-item
dossier/<key>-<slug>branch with the tracker's own key; prefix a setting, default
dossier/(repo); one dossier per owning item (a parent or spec container gets its own, children
add their own only when needed); holds docs, exploration notes and the draft plan until finalized;
deleted on close; pre-push secrets and machine-data check (Q533, Q573, Q168). Origin: owner's
(the name) and ours. - The pre-push secrets check is this thread's first item: CI runs gitleaks on PRs only, and a dossier
branch is pushed with no PR. - Rejected: one ephemeral
contextbranch per issue ("context" is overloaded, D70);workfilesand
other work-compounds (Q573); findings in the resolution comment instead of a branch (Q533). - No ruleset applies to the prefix today (Q533).
Key interfaces
From the design's contracts, "Settings": "Dossier branch prefix dossier/, repo; branch shape
dossier/<key>-<slug> with the tracker's own key; one per owning item; deleted on close."
Variation verdicts: "Dossier prefix: contain now; setting default dossier/; abstract-now not chosen
(Q573)."
Done when
- The source-control convention and
/work-items:workboth name thedossier/prefix (0
mentions on main), and the branch-name test exits 0. - The pre-push step's test exits non-zero on a planted-token fixture and 0 after its revert, both
runs recorded in the PR. - Every slice sub-issue is closed by a merged PR.
Out of scope
- Prototype evidence branches (Other plugins thread), beyond sharing the secrets check.
Activity
github-actions commentedon Oct 16, 2026
Proposed work class: work-class: structural
Basis: automated intake triage; the lanes App applied this class.
Size: Large
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
Understood: add per-item
dossier/<key>-<slug>branches (prefix is a setting, defaultdossier/) to the source-control convention and/work-items:work. They are pushed only after a pre-push secrets and machine-data check, and deleted when the item closes. The done-when items are checkable, and the decisions in the body leave no open questions. The issue lists #7571 and #7578 as dependencies. Neither appears among the newest open issues I was given, so I couldn't confirm their state and listed no blockers. The work spans the convention, a skill, a branch-name test and a pre-push check, and a final item requires closing all slice sub-issues, so it will need splitting. No likely duplicates found.Automated triage, applied by the lanes App.
kyle-sexton commentedon Oct 24, 2026
Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.
To hold this issue again, add
needs-human(orstatus: needs-decision) and say why in a comment.melodic-automation-lanes commentedon Oct 24, 2026
Not admitted to the issue lane yet: Size large: the split into sub-issues at intake is pending (owner Q93).
melodic-automation-lanes commentedon Oct 24, 2026
The latest triage verdict holds nothing: the issue is at
status: ready.kyle-sexton commentedon Oct 26, 2026
Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.
To hold this issue again, add
needs-human(orstatus: needs-decision) and say why in a comment.melodic-automation-lanes commentedon Oct 26, 2026
Split at intake (owner Q93). This issue is Size Large, so its done-when is split into 2 sub-issues, each holding its task-list lines as written.
Automated split by the lanes App. Admission waits on this issue while a sub-issue is open; work-unblock closes it as completed once every sub-issue is closed by a merge or a listed human.