Skip to content

source-control: dossier branches per owning item #7579

Description

@kyle-sexton

Parent

Refs #7555. Source: PLAN Phase 12, topic poteto-review. Thread: Dossier branches.

Depends on

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 context branch per issue ("context" is overloaded, D70); workfiles and
    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:work both name the dossier/ 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

  1. added
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 16, 2026
  2. github-actions commented on Oct 16, 2026

    @github-actions
    Contributor

    Thanks for the report. Automated triage handed this issue to a maintainer.

    Proposed work class: work-class: structural
    Basis: automated intake triage; a maintainer confirms or changes it.

    Automated triage. A maintainer reviews it.

  3. changed the issue type fromtoon Oct 16, 2026
  4. changed the issue type fromtoon Oct 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.needs-specNeeds a Brief or plan before anyone can build it.

    Fields

    Work status

    needs-spec

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions