S2.3.4 — Story roll-up on last-task-resolved #51

Activity

1. dev-pmallapp

   added this to the M2 — Universal lifecycle milestone on Aug 25, 2026
2. dev-pmallapp

   added

   type:taskOne unit of work within a StoryOne unit of work within a Story

   domain:devSoftware development packSoftware development pack

   iaiCreated or managed by iAICreated or managed by iAI

   on Aug 25, 2026
3. dev-pmallapp

   added a parent issue on Aug 25, 2026

   • S2.3 — Execution skills #47
4. dev-pmallapp commented on Sep 7, 2026

   

   dev-pmallapp

   on Sep 7, 2026

   OwnerAuthor

   More actions

   Closed as out of scope for S2.3, by the repository owner's ruling on 2026-09-07. iAI did not author the decision — docs/design/03-workflow.md:271.

   Why

   This is a bootstrapped stub, created from the indicative task row at docs/milestones/M2.md:145 — "Story roll-up on last-task-resolved · Step 8 of the pipeline; derived, not commanded". It was never a considered issue.

   docs/design/stories/47.md places it in Out of Scope, on the ground that references/workflow-states.md:76-79 states plainly that nothing in M1 or M2 implements that automation and that it is performed by hand during the bootstrap window.

   S2.3 ships three Tier-1 verbs — task-create, task-do, task-verify. The roll-up is a derived state transition, not a verb, and building it here would mean this Story shipping a fourth thing that no claim covers: it is anchored to none of CLAIM-47.1–.12.

   Nothing is lost by closing this

   The capability remains recorded in two places that outlive this issue:

   • references/workflow-states.md:76-79 — the contract, which says the automation does not exist and the flip is manual
   • docs/milestones/M2.md:145 — the indicative row

   Named here so the row is not silently dropped a sixth time. The milestone's task table under-counting real work is a confirmed pattern across six Stories; this is the opposite case — a row that names work no Story should do yet, and closing it with a reason is the honest disposition rather than leaving it open to rot.

   Reopening

   Reopen this issue when a Story owns the roll-up. It needs a milestone with the automation in scope and a claim to anchor to. It should not be reopened as an S2.3 task.

   S2.3's task set is now six: #315, #316, #48, #49, #50, #317 — in that dependency order.
5. dev-pmallapp

   closed this as not plannedon Sep 7, 2026