From b5115e45afb1ca9d75cae9ccbb6ab002540a7a4a Mon Sep 17 00:00:00 2001 From: Agentic Cycle Five Date: Fri, 20 Nov 2026 06:56:22 -0500 Subject: [PATCH 01/11] chore(templates): add milestone-groom issue form --- .github/ISSUE_TEMPLATE/milestone-groom.yml | 52 ++++++++++++++++++++++ 1 file changed, 52 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/milestone-groom.yml diff --git a/.github/ISSUE_TEMPLATE/milestone-groom.yml b/.github/ISSUE_TEMPLATE/milestone-groom.yml new file mode 100644 index 0000000..8abc086 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/milestone-groom.yml @@ -0,0 +1,52 @@ +name: Milestone Groom +description: Start-of-milestone chore — write, size, label, and order work; set scope and exit criteria. +title: "[groom] : Groom" +labels: [] +body: + - type: markdown + attributes: + value: | + Start-of-milestone chore. After opening, apply one assignment label: `assigned:nyx`, `assigned:muse`, or `assigned:duet`. + Labels are trusted only when applied by a collaborator with triage or higher. + - type: input + id: milestone + attributes: + label: Milestone + description: Milestone title or number this chore belongs to. + placeholder: v1.2 + validations: + required: true + - type: dropdown + id: agent + attributes: + label: Assigned agent + description: Must match the `assigned:` label you apply after opening. + options: + - nyx + - muse + - duet + validations: + required: true + - type: checkboxes + id: checklist + attributes: + label: Checklist + options: + - label: Write issues that cover the intended milestone scope (and only that scope). + - label: Size each issue. + - label: Apply type/priority labels and put issues in delivery order. + - label: Set the milestone description with scope and exit criteria. + - label: Move or close leftovers from the prior milestone so they are in or out on purpose. + - label: Apply `assigned:` for this chore (triage+ only). Do not use the label as a substitute for GitHub assignees. + - type: textarea + id: scope + attributes: + label: Scope and exit criteria + description: Paste or write the milestone scope and the conditions under which it is done. + validations: + required: true + - type: textarea + id: notes + attributes: + label: Notes + description: Sizing questions, deferred items, links to the board or project. From 25da32977f13254f9ee17cbf0de112ebf5091294 Mon Sep 17 00:00:00 2001 From: Agentic Cycle Five Date: Fri, 20 Nov 2026 06:56:24 -0500 Subject: [PATCH 02/11] chore(templates): add milestone-scope-check issue form --- .../ISSUE_TEMPLATE/milestone-scope-check.yml | 52 +++++++++++++++++++ 1 file changed, 52 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/milestone-scope-check.yml diff --git a/.github/ISSUE_TEMPLATE/milestone-scope-check.yml b/.github/ISSUE_TEMPLATE/milestone-scope-check.yml new file mode 100644 index 0000000..bba8854 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/milestone-scope-check.yml @@ -0,0 +1,52 @@ +name: Milestone Scope Check +description: Midpoint chore — compare open work to exit criteria; cut or defer drift. +title: "[scope] : Scope check" +labels: [] +body: + - type: markdown + attributes: + value: | + Midpoint chore. After opening, apply one assignment label: `assigned:nyx`, `assigned:muse`, or `assigned:duet`. + Labels are trusted only when applied by a collaborator with triage or higher. + Ping Lothrop only when a decision is required (scope change, slip, or something the chore cannot cut or defer alone). + - type: input + id: milestone + attributes: + label: Milestone + description: Milestone title or number this chore belongs to. + placeholder: v1.2 + validations: + required: true + - type: dropdown + id: agent + attributes: + label: Assigned agent + description: Must match the `assigned:` label you apply after opening. + options: + - nyx + - muse + - duet + validations: + required: true + - type: checkboxes + id: checklist + attributes: + label: Checklist + options: + - label: List open milestone issues against the recorded exit criteria. + - label: Identify drift (out of scope, unneeded, or unbounded). + - label: Cut or defer drift (drop from the milestone, close, or move to a later milestone). + - label: Flag Lothrop only if a decision is needed; otherwise finish the chore without a ping. + - label: Record midpoint status (on track / at risk / slipping) and what changed. + - type: textarea + id: status + attributes: + label: Midpoint status + description: "On track / at risk / slipping. What still maps to exit criteria, what was cut or deferred, and any decision needed." + validations: + required: true + - type: textarea + id: notes + attributes: + label: Notes + description: Links to issues moved or closed, and any decision request for Lothrop. From a61dcd3fad0bfcacadfd83be5d40dff6e6036d01 Mon Sep 17 00:00:00 2001 From: Agentic Cycle Five Date: Fri, 20 Nov 2026 06:56:25 -0500 Subject: [PATCH 03/11] chore(templates): add milestone-close-out issue form --- .../ISSUE_TEMPLATE/milestone-close-out.yml | 59 +++++++++++++++++++ 1 file changed, 59 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/milestone-close-out.yml diff --git a/.github/ISSUE_TEMPLATE/milestone-close-out.yml b/.github/ISSUE_TEMPLATE/milestone-close-out.yml new file mode 100644 index 0000000..942381c --- /dev/null +++ b/.github/ISSUE_TEMPLATE/milestone-close-out.yml @@ -0,0 +1,59 @@ +name: Milestone Close-out +description: End-of-milestone chore — verify exit criteria, cut the release, retro, open the next milestone and its chores. +title: "[close-out] : Close-out" +labels: [] +body: + - type: markdown + attributes: + value: | + End-of-milestone chore. After opening, apply one assignment label: `assigned:nyx`, `assigned:muse`, or `assigned:duet`. + Labels are trusted only when applied by a collaborator with triage or higher. + Releases are cut as `cycle-five` per the release trains. Never force-push. + - type: input + id: milestone + attributes: + label: Milestone + description: Milestone title or number being closed. + placeholder: v1.2 + validations: + required: true + - type: dropdown + id: agent + attributes: + label: Assigned agent + description: Must match the `assigned:` label you apply after opening. + options: + - nyx + - muse + - duet + validations: + required: true + - type: checkboxes + id: checklist + attributes: + label: Checklist + options: + - label: Verify every exit criterion is met, or record an explicit waiver. + - label: Cut the release as `cycle-five` per the release trains (no force-push). + - label: Write a short retro (keep / drop / change for the next milestone). + - label: Create the next milestone (scope placeholder is fine). + - label: Open the next milestone's three chore issues (Groom, Scope check, Close-out) from the issue forms. + - label: Assign those chores by `assigned:` using the rotation (nyx → muse → duet → nyx); assign three different agents, and do not repeat the same agent on the same chore type as this milestone. + - label: Close this milestone. + - type: input + id: release + attributes: + label: Release + description: Tag, PR, or release URL cut as cycle-five. Leave blank if this milestone had no release. + - type: textarea + id: retro + attributes: + label: Retro + description: Short keep / drop / change. Note the agents chosen for the next milestone's three chores. + validations: + required: true + - type: textarea + id: notes + attributes: + label: Notes + description: Waivers, leftover issues, links to the next milestone and its chore issues. From 7c3967dc51540c7fab7d13faac1b0206986d4787 Mon Sep 17 00:00:00 2001 From: Agentic Cycle Five Date: Fri, 20 Nov 2026 06:56:26 -0500 Subject: [PATCH 04/11] docs: milestone chores process (groom, scope check, close-out) --- docs/milestone-chores.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 docs/milestone-chores.md diff --git a/docs/milestone-chores.md b/docs/milestone-chores.md new file mode 100644 index 0000000..e43d7bf --- /dev/null +++ b/docs/milestone-chores.md @@ -0,0 +1,13 @@ +# Milestone chores + +Lead duties (create issues, groom the backlog, check scope creep) are per-milestone tasks, not a standing role. Every milestone opens three chore issues and routes each with an `assigned:` label. The chores rotate across Nyx, Muse, and Claude Duet. + +1. **Groom** (start) — write, size, label, and order issues; set milestone scope and exit criteria. +2. **Scope check** (midpoint) — compare open work to the exit criteria; cut or defer drift. Ping Lothrop only when a decision is needed. +3. **Close-out** (end) — verify exit criteria; cut the release as `cycle-five` per the release trains; short retro; open the next milestone and its three chores. + +Use the issue forms in `.github/ISSUE_TEMPLATE/`. After opening, apply exactly one of `assigned:nyx`, `assigned:muse`, or `assigned:duet`. + +**Rotation.** Ring order: `nyx` → `muse` → `duet` → `nyx`. Assign one distinct agent to each of the three chores in a milestone, and advance each chore type one step in the ring from the prior milestone so no agent does the same chore twice in a row. Record the agent on the issue (dropdown + label) so the next close-out can pick the successor. + +**Trust.** Assignment labels are honored only when applied by a collaborator with triage, write, maintain, or admin on that repo. Anyone can open an issue on a public repo, but they cannot add labels. The mailbox still checks the labeler: a trusted `assigned:` routes (tag `routed:assigned`); an untrusted or unknown labeler is recorded with `untrusted-label` and does not wake the agent. From fa54fb0a3c014a6bac83e2c87555acfbdfebc0fd Mon Sep 17 00:00:00 2001 From: Agentic Cycle Five Date: Fri, 20 Nov 2026 09:41:53 -0500 Subject: [PATCH 05/11] docs(chores): define chore cycles on the rolling next train (review fixes) - Close-out cuts a version from next, moves shipped issues into a closed version milestone, and leaves next (#12) open. - Define release trains and chore cycles in docs/milestone-chores.md and link milestone #12 from the forms. - Version input with v0.7.0 placeholder; groom confirms the label matches the dropdown; scope check names #needs-lothrop; mailroom lives outside this repo. --- .../ISSUE_TEMPLATE/milestone-close-out.yml | 34 +++++++++---------- .github/ISSUE_TEMPLATE/milestone-groom.yml | 23 +++++++------ .../ISSUE_TEMPLATE/milestone-scope-check.yml | 23 +++++++------ docs/milestone-chores.md | 20 +++++++---- 4 files changed, 55 insertions(+), 45 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/milestone-close-out.yml b/.github/ISSUE_TEMPLATE/milestone-close-out.yml index 942381c..171e376 100644 --- a/.github/ISSUE_TEMPLATE/milestone-close-out.yml +++ b/.github/ISSUE_TEMPLATE/milestone-close-out.yml @@ -1,20 +1,21 @@ name: Milestone Close-out -description: End-of-milestone chore — verify exit criteria, cut the release, retro, open the next milestone and its chores. -title: "[close-out] : Close-out" +description: End-of-cycle chore — verify exit criteria, cut the version from `next`, retro, open the next cycle's chores. +title: "[close-out] : Close-out" labels: [] body: - type: markdown attributes: value: | - End-of-milestone chore. After opening, apply one assignment label: `assigned:nyx`, `assigned:muse`, or `assigned:duet`. + End-of-cycle chore. A chore cycle is one release train: the work in the rolling [`next`](https://github.com/CycleFive/kharon/milestone/12) milestone up to one version cut. See `docs/milestone-chores.md`. + After opening, apply one assignment label: `assigned:nyx`, `assigned:muse`, or `assigned:duet`. Labels are trusted only when applied by a collaborator with triage or higher. - Releases are cut as `cycle-five` per the release trains. Never force-push. + `next` never closes. Never force-push. - type: input id: milestone attributes: - label: Milestone - description: Milestone title or number being closed. - placeholder: v1.2 + label: Version + description: The version this cycle cuts from `next`. + placeholder: v0.7.0 validations: required: true - type: dropdown @@ -33,27 +34,26 @@ body: attributes: label: Checklist options: - - label: Verify every exit criterion is met, or record an explicit waiver. - - label: Cut the release as `cycle-five` per the release trains (no force-push). - - label: Write a short retro (keep / drop / change for the next milestone). - - label: Create the next milestone (scope placeholder is fine). - - label: Open the next milestone's three chore issues (Groom, Scope check, Close-out) from the issue forms. - - label: Assign those chores by `assigned:` using the rotation (nyx → muse → duet → nyx); assign three different agents, and do not repeat the same agent on the same chore type as this milestone. - - label: Close this milestone. + - label: Verify the train's gate - master is green and something user-visible landed - and every exit criterion is met, or record an explicit waiver. + - label: Cut the version from `next` as `cycle-five` (tag and release; no force-push). + - label: Create a milestone named for the version, move the closed issues that shipped in it from `next` into it, and close that version milestone. Leave `next` open. + - label: Write a short retro (keep / drop / change for the next cycle). + - label: Open the next cycle's three chore issues (Groom, Scope check, Close-out) from the issue forms. + - label: Assign those chores by `assigned:` using the rotation (nyx → muse → duet → nyx); assign three different agents, and do not repeat the same agent on the same chore type as this cycle. - type: input id: release attributes: label: Release - description: Tag, PR, or release URL cut as cycle-five. Leave blank if this milestone had no release. + description: Tag, PR, or release URL cut as cycle-five. Leave blank if the gate was not met and nothing was cut. - type: textarea id: retro attributes: label: Retro - description: Short keep / drop / change. Note the agents chosen for the next milestone's three chores. + description: Short keep / drop / change. Note the agents chosen for the next cycle's three chores. validations: required: true - type: textarea id: notes attributes: label: Notes - description: Waivers, leftover issues, links to the next milestone and its chore issues. + description: Waivers, leftover issues still in `next`, links to the version milestone and the next cycle's chore issues. diff --git a/.github/ISSUE_TEMPLATE/milestone-groom.yml b/.github/ISSUE_TEMPLATE/milestone-groom.yml index 8abc086..4f134d5 100644 --- a/.github/ISSUE_TEMPLATE/milestone-groom.yml +++ b/.github/ISSUE_TEMPLATE/milestone-groom.yml @@ -1,19 +1,20 @@ name: Milestone Groom -description: Start-of-milestone chore — write, size, label, and order work; set scope and exit criteria. -title: "[groom] : Groom" +description: Start-of-cycle chore — write, size, label, and order work in `next`; set scope and exit criteria. +title: "[groom] : Groom" labels: [] body: - type: markdown attributes: value: | - Start-of-milestone chore. After opening, apply one assignment label: `assigned:nyx`, `assigned:muse`, or `assigned:duet`. + Start-of-cycle chore. A chore cycle is one release train: the work in the rolling [`next`](https://github.com/CycleFive/kharon/milestone/12) milestone up to one version cut. See `docs/milestone-chores.md`. + After opening, apply one assignment label: `assigned:nyx`, `assigned:muse`, or `assigned:duet`. Labels are trusted only when applied by a collaborator with triage or higher. - type: input id: milestone attributes: - label: Milestone - description: Milestone title or number this chore belongs to. - placeholder: v1.2 + label: Version + description: The version this cycle will cut from `next`. + placeholder: v0.7.0 validations: required: true - type: dropdown @@ -32,17 +33,17 @@ body: attributes: label: Checklist options: - - label: Write issues that cover the intended milestone scope (and only that scope). + - label: Write issues in `next` that cover the intended scope of this cycle (and only that scope). - label: Size each issue. - label: Apply type/priority labels and put issues in delivery order. - - label: Set the milestone description with scope and exit criteria. - - label: Move or close leftovers from the prior milestone so they are in or out on purpose. - - label: Apply `assigned:` for this chore (triage+ only). Do not use the label as a substitute for GitHub assignees. + - label: Record this cycle's scope and exit criteria in the Scope field below. + - label: Triage leftovers in `next` from the prior cycle so they are in or out on purpose. + - label: Confirm the `assigned:` label matches the dropdown. Do not use the label as a substitute for GitHub assignees. - type: textarea id: scope attributes: label: Scope and exit criteria - description: Paste or write the milestone scope and the conditions under which it is done. + description: Paste or write this cycle's scope and the conditions under which the version is ready to cut. validations: required: true - type: textarea diff --git a/.github/ISSUE_TEMPLATE/milestone-scope-check.yml b/.github/ISSUE_TEMPLATE/milestone-scope-check.yml index bba8854..e59d5c1 100644 --- a/.github/ISSUE_TEMPLATE/milestone-scope-check.yml +++ b/.github/ISSUE_TEMPLATE/milestone-scope-check.yml @@ -1,20 +1,21 @@ name: Milestone Scope Check -description: Midpoint chore — compare open work to exit criteria; cut or defer drift. -title: "[scope] : Scope check" +description: Midpoint chore — compare open work in `next` to the cycle's exit criteria; cut or defer drift. +title: "[scope] : Scope check" labels: [] body: - type: markdown attributes: value: | - Midpoint chore. After opening, apply one assignment label: `assigned:nyx`, `assigned:muse`, or `assigned:duet`. + Midpoint chore. A chore cycle is one release train: the work in the rolling [`next`](https://github.com/CycleFive/kharon/milestone/12) milestone up to one version cut. See `docs/milestone-chores.md`. + After opening, apply one assignment label: `assigned:nyx`, `assigned:muse`, or `assigned:duet`. Labels are trusted only when applied by a collaborator with triage or higher. - Ping Lothrop only when a decision is required (scope change, slip, or something the chore cannot cut or defer alone). + Ping Lothrop in #needs-lothrop only when a decision is required (scope change, slip, or something the chore cannot cut or defer alone). - type: input id: milestone attributes: - label: Milestone - description: Milestone title or number this chore belongs to. - placeholder: v1.2 + label: Version + description: The version this cycle will cut from `next`. + placeholder: v0.7.0 validations: required: true - type: dropdown @@ -33,10 +34,10 @@ body: attributes: label: Checklist options: - - label: List open milestone issues against the recorded exit criteria. + - label: List open issues in `next` against the exit criteria recorded in this cycle's Groom issue. - label: Identify drift (out of scope, unneeded, or unbounded). - - label: Cut or defer drift (drop from the milestone, close, or move to a later milestone). - - label: Flag Lothrop only if a decision is needed; otherwise finish the chore without a ping. + - label: Cut or defer drift (close it, or leave it in `next` explicitly marked for a later cycle). + - label: "Flag Lothrop in #needs-lothrop only if a decision is needed; otherwise finish the chore without a ping." - label: Record midpoint status (on track / at risk / slipping) and what changed. - type: textarea id: status @@ -49,4 +50,4 @@ body: id: notes attributes: label: Notes - description: Links to issues moved or closed, and any decision request for Lothrop. + description: Links to issues deferred or closed, and any decision request for Lothrop. diff --git a/docs/milestone-chores.md b/docs/milestone-chores.md index e43d7bf..c14ee84 100644 --- a/docs/milestone-chores.md +++ b/docs/milestone-chores.md @@ -1,13 +1,21 @@ # Milestone chores -Lead duties (create issues, groom the backlog, check scope creep) are per-milestone tasks, not a standing role. Every milestone opens three chore issues and routes each with an `assigned:` label. The chores rotate across Nyx, Muse, and Claude Duet. +Lead duties (create issues, groom the backlog, check scope creep) are per-cycle tasks, not a standing role. Every chore cycle opens three chore issues and routes each with an `assigned:` label. The chores rotate across Nyx, Muse, and Claude Duet. -1. **Groom** (start) — write, size, label, and order issues; set milestone scope and exit criteria. -2. **Scope check** (midpoint) — compare open work to the exit criteria; cut or defer drift. Ping Lothrop only when a decision is needed. -3. **Close-out** (end) — verify exit criteria; cut the release as `cycle-five` per the release trains; short retro; open the next milestone and its three chores. +## Release trains and chore cycles + +kharon ships on a rolling release train. Work is collected in the one open milestone, [`next`](https://github.com/CycleFive/kharon/milestone/12), which never closes. A version (`v0.7.0`, `v0.8.0`, …) is cut from `next` when its gate passes: master is green and something user-visible landed. Platform goals are tracked with `platform:` labels and tracking issues, not milestones. + +A **chore cycle** is one train: the span from one version cut to the next. The chore issues name the version the cycle is expected to cut. At close-out, the shipped issues move from `next` into a closed milestone named for that version, the same as `v0.2.0`–`v0.6.0`. + +## The three chores + +1. **Groom** (start) — write, size, label, and order issues in `next`; record the cycle's scope and exit criteria. +2. **Scope check** (midpoint) — compare open work in `next` to the exit criteria; cut or defer drift. Ping Lothrop in #needs-lothrop only when a decision is needed. +3. **Close-out** (end) — verify the gate and exit criteria; cut the version from `next` as `cycle-five`; move the shipped issues into the version milestone and close it (`next` stays open); short retro; open the next cycle's three chores. Use the issue forms in `.github/ISSUE_TEMPLATE/`. After opening, apply exactly one of `assigned:nyx`, `assigned:muse`, or `assigned:duet`. -**Rotation.** Ring order: `nyx` → `muse` → `duet` → `nyx`. Assign one distinct agent to each of the three chores in a milestone, and advance each chore type one step in the ring from the prior milestone so no agent does the same chore twice in a row. Record the agent on the issue (dropdown + label) so the next close-out can pick the successor. +**Rotation.** Ring order: `nyx` → `muse` → `duet` → `nyx`. Assign one distinct agent to each of the three chores in a cycle, and advance each chore type one step in the ring from the prior cycle so no agent does the same chore twice in a row. Record the agent on the issue (dropdown + label) so the next close-out can pick the successor. -**Trust.** Assignment labels are honored only when applied by a collaborator with triage, write, maintain, or admin on that repo. Anyone can open an issue on a public repo, but they cannot add labels. The mailbox still checks the labeler: a trusted `assigned:` routes (tag `routed:assigned`); an untrusted or unknown labeler is recorded with `untrusted-label` and does not wake the agent. +**Trust.** Assignment labels are honored only when applied by a collaborator with triage, write, maintain, or admin on that repo. Anyone can open an issue on a public repo, but they cannot add labels. Nothing in this repo reads the labels; routing happens in the agents' mailroom, which lives outside kharon and checks who applied the label before acting on it. From 35683dc3a9941b664446ad3008712371054884fc Mon Sep 17 00:00:00 2001 From: Agentic Cycle Five Date: Fri, 20 Nov 2026 09:58:52 -0500 Subject: [PATCH 06/11] chore(templates): milestones are scope units; release trains run independently (milestone-chores.md) --- docs/milestone-chores.md | 24 ++++++++++++++---------- 1 file changed, 14 insertions(+), 10 deletions(-) diff --git a/docs/milestone-chores.md b/docs/milestone-chores.md index c14ee84..708ae10 100644 --- a/docs/milestone-chores.md +++ b/docs/milestone-chores.md @@ -1,21 +1,25 @@ # Milestone chores -Lead duties (create issues, groom the backlog, check scope creep) are per-cycle tasks, not a standing role. Every chore cycle opens three chore issues and routes each with an `assigned:` label. The chores rotate across Nyx, Muse, and Claude Duet. +Lead duties (writing issues, grooming the backlog, checking scope creep) are tasks inside each milestone, not a standing role. Every milestone carries three chore issues, and each one is routed with an `assigned:` label. The chores rotate across Nyx, Muse, and Claude Duet. -## Release trains and chore cycles +## Milestones and release trains -kharon ships on a rolling release train. Work is collected in the one open milestone, [`next`](https://github.com/CycleFive/kharon/milestone/12), which never closes. A version (`v0.7.0`, `v0.8.0`, …) is cut from `next` when its gate passes: master is green and something user-visible landed. Platform goals are tracked with `platform:` labels and tracking issues, not milestones. +These are two separate things, and they run independently. -A **chore cycle** is one train: the span from one version cut to the next. The chore issues name the version the cycle is expected to cut. At close-out, the shipped issues move from `next` into a closed milestone named for that version, the same as `v0.2.0`–`v0.6.0`. +- **A milestone is a unit of scope.** It has a goal, exit criteria in its description, and a due date (for example `M6 — teach mode`). It opens with its Groom chore and closes when its Close-out chore closes. The due date gives the Scope check a real midpoint, and the milestone's progress bar counts the chores along with the work. +- **The release train is the shipping schedule.** A version (`v0.7.0`, `v0.8.0`, …) is cut whenever master is green and something user-visible has landed. That can happen zero, one, or several times during a milestone. Each version is recorded as a tag and a GitHub release whose notes list the issues it shipped. Versions no longer get their own milestones, because GitHub puts an issue in only one milestone and that slot now belongs to scope. The closed milestones `v0.2.0` through `v0.6.0` stay as history. +- **[`next`](https://github.com/CycleFive/kharon/milestone/12) is the unscheduled backlog.** Work that isn't in the current milestone waits there. Groom pulls issues from `next` into the new milestone, and Close-out sends unfinished work back to `next` or forward into the next milestone on purpose. `next` itself has no chores and never closes. + +Platform goals are still tracked with `platform:` labels and tracking issues. ## The three chores -1. **Groom** (start) — write, size, label, and order issues in `next`; record the cycle's scope and exit criteria. -2. **Scope check** (midpoint) — compare open work in `next` to the exit criteria; cut or defer drift. Ping Lothrop in #needs-lothrop only when a decision is needed. -3. **Close-out** (end) — verify the gate and exit criteria; cut the version from `next` as `cycle-five`; move the shipped issues into the version milestone and close it (`next` stays open); short retro; open the next cycle's three chores. +1. **Groom** (start). Create the milestone with its goal, exit criteria, and due date. Then write, size, label, and order its issues, pulling them from `next`. +2. **Scope check** (around the midpoint, using the due date). Compare the open work to the exit criteria, and cut or defer anything that has drifted. Ping Lothrop in #needs-lothrop only when a decision is needed. +3. **Close-out** (end). Verify the exit criteria or record a waiver, and list the versions the train shipped during the milestone. Move unfinished issues on purpose, write a short retro, open the next milestone's three chores, and then close this issue and the milestone. Close-out doesn't cut a release; the train does that whenever its gate passes. -Use the issue forms in `.github/ISSUE_TEMPLATE/`. After opening, apply exactly one of `assigned:nyx`, `assigned:muse`, or `assigned:duet`. +Use the issue forms in `.github/ISSUE_TEMPLATE/`. Open all three chores into the milestone they belong to, then apply exactly one of `assigned:nyx`, `assigned:muse`, or `assigned:duet`. -**Rotation.** Ring order: `nyx` → `muse` → `duet` → `nyx`. Assign one distinct agent to each of the three chores in a cycle, and advance each chore type one step in the ring from the prior cycle so no agent does the same chore twice in a row. Record the agent on the issue (dropdown + label) so the next close-out can pick the successor. +**Rotation.** The ring order is `nyx` → `muse` → `duet` → `nyx`. Each of a milestone's three chores goes to a different agent. Each chore type moves one step around the ring from the prior milestone, so no agent does the same chore twice in a row. Record the agent on the issue (in the dropdown and the label) so the next Close-out can pick the successor. -**Trust.** Assignment labels are honored only when applied by a collaborator with triage, write, maintain, or admin on that repo. Anyone can open an issue on a public repo, but they cannot add labels. Nothing in this repo reads the labels; routing happens in the agents' mailroom, which lives outside kharon and checks who applied the label before acting on it. +**Trust.** Assignment labels count only when a collaborator with triage, write, maintain, or admin access on the repo applied them. Anyone can open an issue on a public repo, but they can't add labels. Nothing in this repo reads the labels. Routing happens in the agents' mailroom, which lives outside kharon and checks who applied a label before acting on it. From 0c5a5cc14d304f8ffed913f2b7bb4fdbec7a3044 Mon Sep 17 00:00:00 2001 From: Agentic Cycle Five Date: Fri, 20 Nov 2026 09:58:54 -0500 Subject: [PATCH 07/11] chore(templates): milestones are scope units; release trains run independently (milestone-groom.yml) --- .github/ISSUE_TEMPLATE/milestone-groom.yml | 35 +++++++++++----------- 1 file changed, 17 insertions(+), 18 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/milestone-groom.yml b/.github/ISSUE_TEMPLATE/milestone-groom.yml index 4f134d5..450f2ab 100644 --- a/.github/ISSUE_TEMPLATE/milestone-groom.yml +++ b/.github/ISSUE_TEMPLATE/milestone-groom.yml @@ -1,27 +1,27 @@ name: Milestone Groom -description: Start-of-cycle chore — write, size, label, and order work in `next`; set scope and exit criteria. -title: "[groom] : Groom" +description: Start-of-milestone chore. Create the milestone, set its goal, exit criteria, and due date, and groom its issues. +title: "[groom] : Groom" labels: [] body: - type: markdown attributes: value: | - Start-of-cycle chore. A chore cycle is one release train: the work in the rolling [`next`](https://github.com/CycleFive/kharon/milestone/12) milestone up to one version cut. See `docs/milestone-chores.md`. - After opening, apply one assignment label: `assigned:nyx`, `assigned:muse`, or `assigned:duet`. - Labels are trusted only when applied by a collaborator with triage or higher. + Start-of-milestone chore. A milestone is a unit of scope with a goal, exit criteria, and a due date. Releases run on their own train. See `docs/milestone-chores.md`. + Put this issue in the milestone it grooms. After opening it, apply one assignment label: `assigned:nyx`, `assigned:muse`, or `assigned:duet`. + A label counts only when a collaborator with triage access or higher applied it. - type: input id: milestone attributes: - label: Version - description: The version this cycle will cut from `next`. - placeholder: v0.7.0 + label: Milestone + description: The title of the milestone this chore belongs to. + placeholder: M6 — teach mode validations: required: true - type: dropdown id: agent attributes: label: Assigned agent - description: Must match the `assigned:` label you apply after opening. + description: This must match the `assigned:` label you apply after opening the issue. options: - nyx - muse @@ -33,21 +33,20 @@ body: attributes: label: Checklist options: - - label: Write issues in `next` that cover the intended scope of this cycle (and only that scope). - - label: Size each issue. - - label: Apply type/priority labels and put issues in delivery order. - - label: Record this cycle's scope and exit criteria in the Scope field below. - - label: Triage leftovers in `next` from the prior cycle so they are in or out on purpose. - - label: Confirm the `assigned:` label matches the dropdown. Do not use the label as a substitute for GitHub assignees. + - label: Create the milestone with its goal and exit criteria in the description and a due date. + - label: Pull issues from `next` (and from the prior milestone's leftovers) into this milestone, or write new ones, covering this scope and only this scope. + - label: Size each issue, apply type and priority labels, and put the issues in delivery order. + - label: Make sure this milestone's Scope check and Close-out issues exist and are in it. + - label: Confirm the `assigned:` label matches the dropdown. Don't use the label as a substitute for GitHub assignees. - type: textarea id: scope attributes: - label: Scope and exit criteria - description: Paste or write this cycle's scope and the conditions under which the version is ready to cut. + label: Goal and exit criteria + description: The milestone's goal and the conditions under which it is done. Copy them into the milestone description. validations: required: true - type: textarea id: notes attributes: label: Notes - description: Sizing questions, deferred items, links to the board or project. + description: Sizing questions, deferred items, and links to the board or project. From afd216d4458e321e91d6d670582641f0f59b0c1b Mon Sep 17 00:00:00 2001 From: Agentic Cycle Five Date: Fri, 20 Nov 2026 09:58:55 -0500 Subject: [PATCH 08/11] chore(templates): milestones are scope units; release trains run independently (milestone-scope-check.yml) --- .../ISSUE_TEMPLATE/milestone-scope-check.yml | 34 +++++++++---------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/milestone-scope-check.yml b/.github/ISSUE_TEMPLATE/milestone-scope-check.yml index e59d5c1..d8da91e 100644 --- a/.github/ISSUE_TEMPLATE/milestone-scope-check.yml +++ b/.github/ISSUE_TEMPLATE/milestone-scope-check.yml @@ -1,28 +1,28 @@ name: Milestone Scope Check -description: Midpoint chore — compare open work in `next` to the cycle's exit criteria; cut or defer drift. -title: "[scope] : Scope check" +description: Midpoint chore. Compare the open work to the exit criteria, and cut or defer anything that has drifted. +title: "[scope] : Scope check" labels: [] body: - type: markdown attributes: value: | - Midpoint chore. A chore cycle is one release train: the work in the rolling [`next`](https://github.com/CycleFive/kharon/milestone/12) milestone up to one version cut. See `docs/milestone-chores.md`. - After opening, apply one assignment label: `assigned:nyx`, `assigned:muse`, or `assigned:duet`. - Labels are trusted only when applied by a collaborator with triage or higher. - Ping Lothrop in #needs-lothrop only when a decision is required (scope change, slip, or something the chore cannot cut or defer alone). + Midpoint chore, done around halfway to the milestone's due date. See `docs/milestone-chores.md`. + Put this issue in the milestone it checks. After opening it, apply one assignment label: `assigned:nyx`, `assigned:muse`, or `assigned:duet`. + A label counts only when a collaborator with triage access or higher applied it. + Ping Lothrop in #needs-lothrop only when a decision is required: a scope change, a slip, or something this chore can't cut or defer on its own. - type: input id: milestone attributes: - label: Version - description: The version this cycle will cut from `next`. - placeholder: v0.7.0 + label: Milestone + description: The title of the milestone this chore belongs to. + placeholder: M6 — teach mode validations: required: true - type: dropdown id: agent attributes: label: Assigned agent - description: Must match the `assigned:` label you apply after opening. + description: This must match the `assigned:` label you apply after opening the issue. options: - nyx - muse @@ -34,20 +34,20 @@ body: attributes: label: Checklist options: - - label: List open issues in `next` against the exit criteria recorded in this cycle's Groom issue. - - label: Identify drift (out of scope, unneeded, or unbounded). - - label: Cut or defer drift (close it, or leave it in `next` explicitly marked for a later cycle). - - label: "Flag Lothrop in #needs-lothrop only if a decision is needed; otherwise finish the chore without a ping." - - label: Record midpoint status (on track / at risk / slipping) and what changed. + - label: Check the milestone's open issues against its exit criteria. + - label: Identify drift, meaning work that's out of scope, unneeded, or unbounded. + - label: Cut or defer the drift by closing it or moving it back to `next`. + - label: "Flag Lothrop in #needs-lothrop only if a decision is needed. Otherwise finish the chore without a ping." + - label: Record the midpoint status (on track, at risk, or slipping) and what changed, and adjust the due date only with a stated reason. - type: textarea id: status attributes: label: Midpoint status - description: "On track / at risk / slipping. What still maps to exit criteria, what was cut or deferred, and any decision needed." + description: "On track, at risk, or slipping. What still maps to the exit criteria, what was cut or deferred, and any decision needed." validations: required: true - type: textarea id: notes attributes: label: Notes - description: Links to issues deferred or closed, and any decision request for Lothrop. + description: Links to issues that were deferred or closed, and any decision request for Lothrop. From 264908688d1b716ab628c34e15578865cc291440 Mon Sep 17 00:00:00 2001 From: Agentic Cycle Five Date: Fri, 20 Nov 2026 09:58:57 -0500 Subject: [PATCH 09/11] chore(templates): milestones are scope units; release trains run independently (milestone-close-out.yml) --- .../ISSUE_TEMPLATE/milestone-close-out.yml | 47 ++++++++++--------- 1 file changed, 25 insertions(+), 22 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/milestone-close-out.yml b/.github/ISSUE_TEMPLATE/milestone-close-out.yml index 171e376..dab83eb 100644 --- a/.github/ISSUE_TEMPLATE/milestone-close-out.yml +++ b/.github/ISSUE_TEMPLATE/milestone-close-out.yml @@ -1,28 +1,28 @@ name: Milestone Close-out -description: End-of-cycle chore — verify exit criteria, cut the version from `next`, retro, open the next cycle's chores. -title: "[close-out] : Close-out" +description: End-of-milestone chore. Verify the exit criteria, record what shipped, write a retro, and open the next milestone's chores. +title: "[close-out] : Close-out" labels: [] body: - type: markdown attributes: value: | - End-of-cycle chore. A chore cycle is one release train: the work in the rolling [`next`](https://github.com/CycleFive/kharon/milestone/12) milestone up to one version cut. See `docs/milestone-chores.md`. - After opening, apply one assignment label: `assigned:nyx`, `assigned:muse`, or `assigned:duet`. - Labels are trusted only when applied by a collaborator with triage or higher. - `next` never closes. Never force-push. + End-of-milestone chore. This is the last open issue in the milestone, and closing it closes the milestone. See `docs/milestone-chores.md`. + Put this issue in the milestone it closes. After opening it, apply one assignment label: `assigned:nyx`, `assigned:muse`, or `assigned:duet`. + A label counts only when a collaborator with triage access or higher applied it. + Releases run on their own train, which cuts a version whenever master is green and something user-visible has landed, so Close-out doesn't cut one. Never force-push. - type: input id: milestone attributes: - label: Version - description: The version this cycle cuts from `next`. - placeholder: v0.7.0 + label: Milestone + description: The title of the milestone being closed. + placeholder: M6 — teach mode validations: required: true - type: dropdown id: agent attributes: label: Assigned agent - description: Must match the `assigned:` label you apply after opening. + description: This must match the `assigned:` label you apply after opening the issue. options: - nyx - muse @@ -34,26 +34,29 @@ body: attributes: label: Checklist options: - - label: Verify the train's gate - master is green and something user-visible landed - and every exit criterion is met, or record an explicit waiver. - - label: Cut the version from `next` as `cycle-five` (tag and release; no force-push). - - label: Create a milestone named for the version, move the closed issues that shipped in it from `next` into it, and close that version milestone. Leave `next` open. - - label: Write a short retro (keep / drop / change for the next cycle). - - label: Open the next cycle's three chore issues (Groom, Scope check, Close-out) from the issue forms. - - label: Assign those chores by `assigned:` using the rotation (nyx → muse → duet → nyx); assign three different agents, and do not repeat the same agent on the same chore type as this cycle. - - type: input - id: release + - label: Verify that every exit criterion is met, or record an explicit waiver. + - label: List the versions the release train shipped during this milestone. If user-visible work landed and no version was cut, raise it and don't cut one here. + - label: Move every unfinished issue on purpose, either into the next milestone or back to `next`. + - label: Write a short retro covering what to keep, drop, or change for the next milestone. + - label: Open the next milestone's three chore issues (Groom, Scope check, and Close-out) from the issue forms, and put them in that milestone. + - label: Assign those chores with `assigned:` labels following the rotation (nyx → muse → duet → nyx). Each chore goes to a different agent, and no chore type repeats this milestone's agent. + - label: Close this issue and then the milestone. + - type: textarea + id: releases attributes: - label: Release - description: Tag, PR, or release URL cut as cycle-five. Leave blank if the gate was not met and nothing was cut. + label: Versions shipped + description: Tags or release URLs the train cut during this milestone. Write "none" if it cut none. + validations: + required: true - type: textarea id: retro attributes: label: Retro - description: Short keep / drop / change. Note the agents chosen for the next cycle's three chores. + description: A short note on what to keep, drop, or change. Name the agents chosen for the next milestone's three chores. validations: required: true - type: textarea id: notes attributes: label: Notes - description: Waivers, leftover issues still in `next`, links to the version milestone and the next cycle's chore issues. + description: Waivers, issues that were moved and where they went, and links to the next milestone and its chore issues. From 8db5156b7313e4b1b0335c7837cf1b4954606045 Mon Sep 17 00:00:00 2001 From: Agentic Cycle Five Date: Fri, 20 Nov 2026 11:41:56 -0500 Subject: [PATCH 10/11] chore(templates): Close-out creates the next milestone, Groom fills it in Resolves Duet's required item on #370: Close-out creates the next milestone (title only) and files its chores into it; Groom sets goal, exit criteria and due date. Also names where to raise a missing release, and adds a bootstrap note. --- .github/ISSUE_TEMPLATE/milestone-close-out.yml | 4 ++-- .github/ISSUE_TEMPLATE/milestone-groom.yml | 4 ++-- docs/milestone-chores.md | 8 +++++--- 3 files changed, 9 insertions(+), 7 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/milestone-close-out.yml b/.github/ISSUE_TEMPLATE/milestone-close-out.yml index dab83eb..c7c44bb 100644 --- a/.github/ISSUE_TEMPLATE/milestone-close-out.yml +++ b/.github/ISSUE_TEMPLATE/milestone-close-out.yml @@ -35,10 +35,10 @@ body: label: Checklist options: - label: Verify that every exit criterion is met, or record an explicit waiver. - - label: List the versions the release train shipped during this milestone. If user-visible work landed and no version was cut, raise it and don't cut one here. + - label: List the versions the release train shipped during this milestone. If user-visible work landed and no version was cut, raise it in #kharon (or in #needs-lothrop if it needs Lothrop's call), and don't cut one here. - label: Move every unfinished issue on purpose, either into the next milestone or back to `next`. - label: Write a short retro covering what to keep, drop, or change for the next milestone. - - label: Open the next milestone's three chore issues (Groom, Scope check, and Close-out) from the issue forms, and put them in that milestone. + - label: Create the next milestone with a title only (its Groom sets the goal, exit criteria, and due date). Then open its three chore issues (Groom, Scope check, and Close-out) from the issue forms and put them in it. - label: Assign those chores with `assigned:` labels following the rotation (nyx → muse → duet → nyx). Each chore goes to a different agent, and no chore type repeats this milestone's agent. - label: Close this issue and then the milestone. - type: textarea diff --git a/.github/ISSUE_TEMPLATE/milestone-groom.yml b/.github/ISSUE_TEMPLATE/milestone-groom.yml index 450f2ab..fcdd858 100644 --- a/.github/ISSUE_TEMPLATE/milestone-groom.yml +++ b/.github/ISSUE_TEMPLATE/milestone-groom.yml @@ -1,5 +1,5 @@ name: Milestone Groom -description: Start-of-milestone chore. Create the milestone, set its goal, exit criteria, and due date, and groom its issues. +description: Start-of-milestone chore. Set the milestone's goal, exit criteria, and due date, and groom its issues. title: "[groom] : Groom" labels: [] body: @@ -33,7 +33,7 @@ body: attributes: label: Checklist options: - - label: Create the milestone with its goal and exit criteria in the description and a due date. + - label: Fill in the milestone (the prior Close-out created it with a title only). Put its goal and exit criteria in the description and set a due date. - label: Pull issues from `next` (and from the prior milestone's leftovers) into this milestone, or write new ones, covering this scope and only this scope. - label: Size each issue, apply type and priority labels, and put the issues in delivery order. - label: Make sure this milestone's Scope check and Close-out issues exist and are in it. diff --git a/docs/milestone-chores.md b/docs/milestone-chores.md index 708ae10..c919427 100644 --- a/docs/milestone-chores.md +++ b/docs/milestone-chores.md @@ -6,7 +6,7 @@ Lead duties (writing issues, grooming the backlog, checking scope creep) are tas These are two separate things, and they run independently. -- **A milestone is a unit of scope.** It has a goal, exit criteria in its description, and a due date (for example `M6 — teach mode`). It opens with its Groom chore and closes when its Close-out chore closes. The due date gives the Scope check a real midpoint, and the milestone's progress bar counts the chores along with the work. +- **A milestone is a unit of scope.** It has a goal, exit criteria in its description, and a due date (for example `M6 — teach mode`). The prior milestone's Close-out creates it with a title only, its Groom chore fills in the goal, exit criteria, and due date, and it closes when its own Close-out chore closes. The due date gives the Scope check a real midpoint, and the milestone's progress bar counts the chores along with the work. - **The release train is the shipping schedule.** A version (`v0.7.0`, `v0.8.0`, …) is cut whenever master is green and something user-visible has landed. That can happen zero, one, or several times during a milestone. Each version is recorded as a tag and a GitHub release whose notes list the issues it shipped. Versions no longer get their own milestones, because GitHub puts an issue in only one milestone and that slot now belongs to scope. The closed milestones `v0.2.0` through `v0.6.0` stay as history. - **[`next`](https://github.com/CycleFive/kharon/milestone/12) is the unscheduled backlog.** Work that isn't in the current milestone waits there. Groom pulls issues from `next` into the new milestone, and Close-out sends unfinished work back to `next` or forward into the next milestone on purpose. `next` itself has no chores and never closes. @@ -14,12 +14,14 @@ Platform goals are still tracked with `platform:` labels and tracking issues. ## The three chores -1. **Groom** (start). Create the milestone with its goal, exit criteria, and due date. Then write, size, label, and order its issues, pulling them from `next`. +1. **Groom** (start). Set the milestone's goal, exit criteria, and due date (the prior Close-out created it with a title only). Then write, size, label, and order its issues, pulling them from `next`. 2. **Scope check** (around the midpoint, using the due date). Compare the open work to the exit criteria, and cut or defer anything that has drifted. Ping Lothrop in #needs-lothrop only when a decision is needed. -3. **Close-out** (end). Verify the exit criteria or record a waiver, and list the versions the train shipped during the milestone. Move unfinished issues on purpose, write a short retro, open the next milestone's three chores, and then close this issue and the milestone. Close-out doesn't cut a release; the train does that whenever its gate passes. +3. **Close-out** (end). Verify the exit criteria or record a waiver, and list the versions the train shipped during the milestone. Move unfinished issues on purpose, write a short retro, create the next milestone (title only) and open its three chores in it, and then close this issue and the milestone. Close-out doesn't cut a release; the train does that whenever its gate passes. Use the issue forms in `.github/ISSUE_TEMPLATE/`. Open all three chores into the milestone they belong to, then apply exactly one of `assigned:nyx`, `assigned:muse`, or `assigned:duet`. **Rotation.** The ring order is `nyx` → `muse` → `duet` → `nyx`. Each of a milestone's three chores goes to a different agent. Each chore type moves one step around the ring from the prior milestone, so no agent does the same chore twice in a row. Record the agent on the issue (in the dropdown and the label) so the next Close-out can pick the successor. +**Bootstrapping.** The first milestone has no prior Close-out. Lothrop, or the agent he names, creates it with a title, opens its three chores in it, and assigns them as he directs. The rotation runs from there. + **Trust.** Assignment labels count only when a collaborator with triage, write, maintain, or admin access on the repo applied them. Anyone can open an issue on a public repo, but they can't add labels. Nothing in this repo reads the labels. Routing happens in the agents' mailroom, which lives outside kharon and checks who applied a label before acting on it. From ddd30eb63709ef2e0bb429bb07e9a3bb6b411ad4 Mon Sep 17 00:00:00 2001 From: Agentic Cycle Five Date: Fri, 20 Nov 2026 11:42:26 -0500 Subject: [PATCH 11/11] chore(templates): quote Close-out label so ' #kharon' isn't read as a YAML comment --- .github/ISSUE_TEMPLATE/milestone-close-out.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/milestone-close-out.yml b/.github/ISSUE_TEMPLATE/milestone-close-out.yml index c7c44bb..0d66b12 100644 --- a/.github/ISSUE_TEMPLATE/milestone-close-out.yml +++ b/.github/ISSUE_TEMPLATE/milestone-close-out.yml @@ -35,7 +35,7 @@ body: label: Checklist options: - label: Verify that every exit criterion is met, or record an explicit waiver. - - label: List the versions the release train shipped during this milestone. If user-visible work landed and no version was cut, raise it in #kharon (or in #needs-lothrop if it needs Lothrop's call), and don't cut one here. + - label: "List the versions the release train shipped during this milestone. If user-visible work landed and no version was cut, raise it in #kharon (or in #needs-lothrop if it needs Lothrop's call), and don't cut one here." - label: Move every unfinished issue on purpose, either into the next milestone or back to `next`. - label: Write a short retro covering what to keep, drop, or change for the next milestone. - label: Create the next milestone with a title only (its Groom sets the goal, exit criteria, and due date). Then open its three chore issues (Groom, Scope check, and Close-out) from the issue forms and put them in it.