Design the close process and resolution comments #244

New issue

Closed

opened 2026-08-03 14:43:00 +00:00 by jared · 1 comment

jared commented

2026-08-03 14:43:00 +00:00

Owner

Map: #239

Question

What structure should closing carry? Candidates from #56: a resolution comment recording what was decided/done, evidence links, and explicit out-of-scope; plus how this composes with the existing review-label flow and the never-close rule for recurring issues.

Map: #239 ## Question What structure should closing carry? Candidates from #56: a resolution comment recording what was decided/done, evidence links, and explicit out-of-scope; plus how this composes with the existing review-label flow and the never-close rule for recurring issues.

jared added the

wayfinder:grilling

label

2026-08-03 14:43:06 +00:00

jared referenced this issue

2026-08-03 14:43:45 +00:00

Assemble the os-backlog lifecycle design #247

jared self-assigned this

2026-08-04 10:33:42 +00:00

jared commented

2026-08-04 10:35:02 +00:00

Author

Owner

Resolution

Decided (grilling session 2026-08-04):

Three-part resolution comment, mandatory for agent closes. Every AI-performed close carries ## Resolution with: (a) what was decided/done; (b) evidence links — commits, PR, test output, ADRs, linked never pasted; (c) explicit out-of-scope/follow-ups, each either linked to a captured issue (/os-backlog:capture) or declared dropped. A follow-up mentioned in prose but not captured is a lifecycle leak — (c) is the enforcement point. Human closes: encouraged, not policed.
Merge approval = sign-off. Pipeline-worked tickets (os-sdlc merge gate) close at merge with the resolution comment; the human's merge approval subsumes the review label. review + stays-open is reserved for work with no merge gate (pure decisions, docs, ops changes).
Corollary (recurring issues): occurrence outcomes are recorded with the same three-part comment shape, without closing — the never-closed-by-AI rule stands.

Composes with prior decisions unchanged: sweep-gate closes decision children (#240); refine may close duplicate/done captures with evidence (#242).

## Resolution Decided (grilling session 2026-08-04): 1. **Three-part resolution comment, mandatory for agent closes.** Every AI-performed close carries `## Resolution` with: (a) what was decided/done; (b) evidence links — commits, PR, test output, ADRs, linked never pasted; (c) explicit out-of-scope/follow-ups, each either linked to a captured issue (`/os-backlog:capture`) or declared dropped. A follow-up mentioned in prose but not captured is a lifecycle leak — (c) is the enforcement point. Human closes: encouraged, not policed. 2. **Merge approval = sign-off.** Pipeline-worked tickets (os-sdlc merge gate) close at merge with the resolution comment; the human's merge approval subsumes the `review` label. `review` + stays-open is reserved for work with no merge gate (pure decisions, docs, ops changes). 3. **Corollary (recurring issues):** occurrence outcomes are recorded with the same three-part comment shape, without closing — the never-closed-by-AI rule stands. Composes with prior decisions unchanged: sweep-gate closes decision children (#240); refine may close duplicate/done captures with evidence (#242).

jared closed this issue

2026-08-04 10:35:02 +00:00

jared referenced this issue

2026-08-04 10:35:02 +00:00

Wayfinder map: os-backlog issue lifecycle & templates #239

jared referenced this issue

2026-08-04 10:45:01 +00:00

Define the weighted-decision block format and threshold sweep #248