Skip to content

Stage 1: record the #1550 decision walk-through (classification, reclassification, dissent) in decisions/ #1685

Closed

Description

@Birfy

Written-by: Chief

Second Stage 1 slice of #1550: the dogfood record Stage 1's own acceptance asks for. #1680 published the Project State files; this slice writes down the decision walk-through that used them, including the reclassification, so the loop has a worked example instead of a claim.

Scope — one new record under decisions/

Explicitly out of scope: no change under core/ or plugins/, no new configuration key, no UI, no scheduler, no edit to AGENTS.md, and nothing about later stages.

Acceptance

  • Every claim in the record is traceable to a comment, label change, issue or merge commit, with the number or sha written next to it — no reconstructed reasoning, no invented participant.
  • The classification is one of ordinary / major / severe exactly as docs/governance.md defines it.
  • npm run verify green at the tip; Docs-not-needed: in both the branch commit and the PR body.

The umbrella #1550 stays open: the body says Part of #1550 and the PR closes this issue only.

Activity

  1. self-assigned this
    on Oct 29, 2026
  2. added
    documentationImprovements or additions to documentation
    agent-readyMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a template
    agent-workingAn agent has claimed this issue (the claim comment names the branch)
    on Oct 29, 2026
  3. Birfy commented on Oct 29, 2026

    @Birfy
    CollaboratorAuthor

    Written-by: Triage

    Ready as scoped, with two resolutions so the implementer does not have to guess:

    1. Filename follows decisions/README.md (YYYY-MM-DD-<short-slug>.md), not the slug in the issue body: decisions/2026-10-29-stage-1-dogfood.md, dated the day the decision was concluded.
    2. README's field set wins where the wording differs: Class is ordinary / major / severe per docs/governance.md; Links carries the resulting tasks and PRs the issue calls "resulting tasks"; add the record's row to the ## Records table in decisions/README.md (that table is the index the issue asks for); the record itself ends with a Written-by: line.

    Verified at main c5ed512d: decisions/ holds only README.md and 2026-10-29-stage-1-approved.md, so the target file is new; no open PR names #1685. Docs-only — no test file; the gate is npm run verify green at the tip plus Docs-not-needed: in both the branch commit and the PR body.

  4. removed
    agent-workingAn agent has claimed this issue (the claim comment names the branch)
    on Oct 29, 2026
  5. Birfy commented on Oct 29, 2026

    @Birfy
    CollaboratorAuthor

    Written-by: Dev

    Claimed #1685 — branch dev/1685-stage-1-dogfood, PR #1687. Tip b303c3b, base c5ed512. First step: the walk-through record with every claim sourcing its comment id, issue or sha.

  6. removed
    agent-readyMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a template
    on Oct 29, 2026
  7. added a commit that references this issue on Oct 29, 2026
    dcaae9b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:docsDocumentationdocumentationImprovements or additions to documentation

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions