Editing or deleting a posted Phase Outcome — remains a contract violation (§8); this feature adds a forward correction path and never a mutation. #419

New issue

Closed

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

jbr870 commented

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

Owner

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

Original scope note: Flagged as out of scope in the approved PREQ.

Disposition rationale: Editing or deleting a posted Phase Outcome stays a contract violation (§8): this feature adds a forward correction path and never a mutation, which is exactly what lets the annulled record survive as history. The stub records that boundary so the immutability invariant is not later relaxed on the argument that "we now have a correction mechanism anyway" — the opposite is true, the mechanism exists so §8 need not bend. 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-3` (out-of-scope) on issue #45 during decision D-PO-45-2-3. **Original scope note:** Flagged as out of scope in the approved PREQ. **Disposition rationale:** Editing or deleting a posted Phase Outcome stays a contract violation (§8): this feature adds a forward correction path and never a mutation, which is exactly what lets the annulled record survive as history. The stub records that boundary so the immutability invariant is not later relaxed on the argument that "we now have a correction mechanism anyway" — the opposite is true, the mechanism exists so §8 need not bend. 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:18 +00:00

jbr870 referenced this issue

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

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

jbr870 commented

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

Author

Owner

Closing as not actionable by construction.

This stub was spawned from finding F-PO-45-2-3 on #45 because /dev:technical-plan recommends defer-to-issue for every PREQ out-of-scope item. On the merits there is no work here: "editing or deleting a posted Phase Outcome remains a contract violation (forge-contract §8)" is a standing prohibition, not a task — and the supersede feature (#45) exists precisely so §8 never has to bend.

The boundary itself is not lost: it is recorded in #45's SREQ (Constraints & Non-Goals) and in the resolution of D-PO-45-2-3, which is where a future reader will actually encounter it. Operator decision, 2026-08-26.

Closing as **not actionable by construction**. This stub was spawned from finding `F-PO-45-2-3` on #45 because `/dev:technical-plan` recommends `defer-to-issue` for every PREQ out-of-scope item. On the merits there is no work here: "editing or deleting a posted Phase Outcome remains a contract violation (forge-contract §8)" is a **standing prohibition**, not a task — and the supersede feature (#45) exists precisely so §8 never has to bend. The boundary itself is not lost: it is recorded in #45's SREQ (Constraints & Non-Goals) and in the resolution of `D-PO-45-2-3`, which is where a future reader will actually encounter it. Operator decision, 2026-08-26.

jbr870 closed this issue

2026-08-26 17:56:00 +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#419

No description provided.

Rows
Columns