From e516cd9c5cf71910a6d7d46eb06d1b66bf49068c Mon Sep 17 00:00:00 2001 From: "Jamey M. Yates" Date: Wed, 30 Sep 2026 23:19:25 -0500 Subject: [PATCH] fix: require durable ownership of material consequences --- handoffs/return-of-control.md | 6 ++++++ roles/planning.md | 15 +++++++++++++++ workflows/reviewed-change.md | 3 +++ 3 files changed, 24 insertions(+) diff --git a/handoffs/return-of-control.md b/handoffs/return-of-control.md index 14f492e..b8327e2 100644 --- a/handoffs/return-of-control.md +++ b/handoffs/return-of-control.md @@ -52,6 +52,12 @@ instantiated handoff under the actual authority. | Follow-up | `` | | Return destination and requested decision | `` | +For a completion return, use **Follow-up** to preserve the disposition of material +consequences outside the completed scope: the responsible owner and durable +work-record identity when deferred, or supporting rationale when inapplicable. +Apply [Planning's consequence guidance](../roles/planning.md#workflow-local-operational-guidance) +proportionately; vague future intent does not establish ownership. + Report only the state evidence supports. Distinguish completed authorized work from unresolved architectural or operational completion. Preserve useful partial work safely; do not use a stop report as permission to erase it, change scope, or diff --git a/roles/planning.md b/roles/planning.md index 98aad2b..4c2d545 100644 --- a/roles/planning.md +++ b/roles/planning.md @@ -50,6 +50,21 @@ authority, protected effects, and justified constraints from forecast files or techniques. Mark deliberate exact-change restrictions and the consequence they protect. Implementation owns ordinary mechanics inside those boundaries. +Before claiming governed work complete, Planning asks: what material consequences +did this decision or change actually create, and where is each one owned? +Disposition each as handled in the current work, explicitly inapplicable with +supporting evidence or rationale, or durably owned elsewhere. Keep this check +proportionate: speculative, unsupported, or immaterial possibilities require +neither disposition records nor follow-up work. + +Bounded scope separation is valid when ownership is retained. For a deferred +material consequence, preserve the actual responsible owner and durable work-record +identity. An existing issue, project record, roadmap item, or instantiated handoff +can suffice; no new issue or GitHub use is required. Labels such as `later`, +`separate work`, or `out of scope` alone do not establish ownership. A deferred +material consequence without a durable owner means completion is premature; +the current work need not absorb it. + When issue completion is part of the project contract, Planning/project authority establishes the substantive completion boundary and whether merge is intended to satisfy it. Distinguish material completion conditions from routine housekeeping. diff --git a/workflows/reviewed-change.md b/workflows/reviewed-change.md index 286b090..1ee092c 100644 --- a/workflows/reviewed-change.md +++ b/workflows/reviewed-change.md @@ -118,6 +118,9 @@ role. Preparing that handoff does not itself authorize the sender to execute it. [return of control](../handoffs/return-of-control.md) on completion, interruption, missing authority, or a new material decision. Publication can be absent; all roles still return useful state, evidence, unresolved conditions, and follow-up. + Governed completion requires material consequences actually created by the work + to be handled, explicitly inapplicable, or durably owned, under + [Planning's consequence guidance](../roles/planning.md#workflow-local-operational-guidance). Instantiated contracts, candidates, findings, and execution records remain with the consuming project. This file supplies a reusable composition, not task state,