Migrating history. Records posted before this feature carry no supersede and no roll-call; nothing is rewritten. #421

New issue

Closed

opened 2026-08-26 16:20:22 +00:00 by jbr870 · 1 comment

jbr870 commented

2026-08-26 16:20:22 +00:00

Owner

Spawned from finding F-PO-45-2-5 (out-of-scope) on issue #45 during decision D-PO-45-2-5.

Original scope note: Flagged as out of scope in the approved PREQ — an old outcome can still be annulled going forward, because a supersede is a new record.

Disposition rationale: Nothing is rewritten: records posted before this feature simply carry no supersede and no roll-call, and both readers tolerate their absence by design (roll_call reads null like suite, and enforcement lives only at the post seam). An old outcome remains correctable going forward, because a supersede is a new record rather than an edit — which is the whole point of the forward-only design. The stub records that no migration is owed, so nobody later writes one. Resolved under the operator's standing instruction of 2026-08-26 ("resolve all decisions as recommended"), which is the authority for taking each producer recommendation as given.

This issue was deferred out of the parent feature's scope; it carries no PREQ yet. Run /dev:requirements --issue={new-number} to flesh it out before planning.

Spawned from finding `F-PO-45-2-5` (out-of-scope) on issue #45 during decision D-PO-45-2-5. **Original scope note:** Flagged as out of scope in the approved PREQ — an old outcome can still be annulled going forward, because a supersede is a new record. **Disposition rationale:** Nothing is rewritten: records posted before this feature simply carry no supersede and no roll-call, and both readers tolerate their absence by design (`roll_call` reads `null` like `suite`, and enforcement lives only at the post seam). An old outcome remains correctable going forward, because a supersede is a new record rather than an edit — which is the whole point of the forward-only design. The stub records that no migration is owed, so nobody later writes one. Resolved under the operator's standing instruction of 2026-08-26 ("resolve all decisions as recommended"), which is the authority for taking each producer recommendation as given. This issue was deferred out of the parent feature's scope; it carries no PREQ yet. Run `/dev:requirements --issue={new-number}` to flesh it out before planning.

jbr870 added the

labels

2026-08-26 16:20:22 +00:00

jbr870 referenced this issue

2026-08-26 16:20:22 +00:00

Phase Outcomes: no supersede path when a posted outcome's premise turns out false #45

jbr870 commented

2026-08-26 17:56:01 +00:00

Author

Owner

Closing as not actionable by construction.

This stub was spawned from finding F-PO-45-2-5 on #45 because /dev:technical-plan recommends defer-to-issue for every PREQ out-of-scope item. On the merits there is nothing to do: records posted before the supersede feature simply carry no supersede and no roll-call, and both readers tolerate that by design (roll_call reads null like suite; enforcement lives only at the post seam). An old outcome stays correctable going forward, because a supersede is a new record rather than an edit.

"No migration is owed" is recorded in #45's SREQ (Constraints & Non-Goals) and in the resolution of D-PO-45-2-5. Operator decision, 2026-08-26.

Closing as **not actionable by construction**. This stub was spawned from finding `F-PO-45-2-5` on #45 because `/dev:technical-plan` recommends `defer-to-issue` for every PREQ out-of-scope item. On the merits there is nothing to do: records posted before the supersede feature simply carry no supersede and no roll-call, and both readers tolerate that by design (`roll_call` reads `null` like `suite`; enforcement lives only at the post seam). An old outcome stays correctable going forward, because a supersede is a new record rather than an edit. "No migration is owed" is recorded in #45's SREQ (Constraints & Non-Goals) and in the resolution of `D-PO-45-2-5`. Operator decision, 2026-08-26.

jbr870 closed this issue

2026-08-26 17:56:01 +00:00

jbr870 referenced this issue

2026-08-27 07:32:44 +00:00

/dev:technical-plan 2.4b hardcodes proposed_action: defer-to-issue for PREQ out-of-scope findings, contradicting its own rule four paragraphs below #452

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

jbr870/devwork-skills#421

No description provided.

Rows
Columns