npm - create-agdf - Versions diffs - 0.6.9 → 0.7.1 - Mend

create-agdf 0.6.9 → 0.7.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (24) hide show

package/generated/.agdf/control/templates/AGDF_RUN.md CHANGED Viewed

@@ -4,8 +4,8 @@
 - run_id:
 - started_at:
-- mode: `quick_task | structured_delivery`
-- current_gate: `none | UR | Brownfield Review | Mode/Slice Decision | PRD | SD | TP | Quick Task Execution | Brownfield Analysis | CD+Tests | CR | QA | UAT | OR`
+- mode: `quick_task | verified_change | structured_delivery`
+- current_gate: `none | UR | Brownfield Review | Mode/Slice Decision | PRD | SD | TP | Quick Task Execution | Verified Change Execution | Brownfield Analysis | CD+Tests | CR | QA | UAT | OR`
 - decision: `pass | revise | block | in_progress`
 - owner:
@@ -68,6 +68,7 @@ Valid approval format for new runs: `Approval: <GateName>`.
 | SD |  | `draft | approved | superseded | not_applicable` |  |
 | TP |  | `draft | approved | superseded | not_applicable` |  |
 | Brownfield Review |  | `missing | draft | done | not_applicable | superseded` |  |
+| Verified Change |  | `missing | draft | eligible | executed | escalated` |  |
 | Review |  | `missing | done | not_applicable` |  |
 | QA |  | `missing | pass | revise | block | not_applicable` |  |
 | OR |  | `missing | done | not_applicable` |  |
@@ -77,7 +78,7 @@ Valid approval format for new runs: `Approval: <GateName>`.
 Set this after Brownfield Review. Do not assume the full gate chain before the existing-system impact is understood.
 Quick Task execution or implementation is not allowed until this decision is visible with scope reason and evidence.
-- decision: `undecided | quick_task | structured_slice | structured_delivery | block`
+- decision: `undecided | quick_task | verified_change | structured_slice | structured_delivery | block`
 - required_next_gate: `none | PRD | SD | TP | Brownfield Analysis`
 - scope_reason:
 - evidence:

package/generated/.agdf/control/templates/RUN_STATE.md CHANGED Viewed

@@ -37,6 +37,28 @@ Describe the trustworthy outcome.
 | QA | missing |  |
 | UAT | missing |  |
+## Artefacts
+| Type | Path | Status | Notes |
+|---|---|---|---|
+| UR |  | draft |  |
+| Brownfield Review |  | missing |  |
+| Verified Change |  | missing |  |
+| PRD |  | missing |  |
+| SD |  | missing |  |
+| TP |  | missing |  |
+| Brownfield Analysis |  | missing |  |
+| CD+Tests |  | missing |  |
+| CR |  | missing |  |
+| QA |  | missing |  |
+## Mode/Slice Decision
+- decision: `quick_task | verified_change | structured_slice | structured_delivery | block`
+- required_next_gate:
+- scope_reason:
+- evidence:
 ## Evidence
 | Evidence | Source | Covers | Strength |

package/generated/.agdf/control/templates/artefacts/BROWNFIELD_REVIEW.md CHANGED Viewed

@@ -37,7 +37,7 @@ What approved UR scope is being sized and routed?
 ## Mode / Slice Decision
-- decision: `quick_task | structured_slice | structured_delivery | block`
+- decision: `quick_task | verified_change | structured_slice | structured_delivery | block`
 - required_next_gate: `none | PRD | SD | TP | Brownfield Analysis`
 - scope_reason:
 - evidence:

package/generated/.agdf/control/templates/artefacts/VERIFIED_CHANGE.md ADDED Viewed

@@ -0,0 +1,48 @@
+# Verified Change: <Title>
+Status: `draft | eligible | executed | escalated`
+## Record
+- status: draft
+- related_ur:
+- escalation_target: `structured_slice | structured_delivery`
+- canonical_owner:
+- allowed_source_paths:
+- allowed_derived_paths: none
+- prohibited_impacts: none
+- propagation_command: none
+- validation_commands:
+- baseline_tracked_paths: none
+- baseline_untracked_paths: none
+- validation_status: pending
+- propagation_status: not_applicable
+## Eligibility Assertions
+| Condition | Evidence | Status |
+|---|---|---|
+| Exactly one canonical owner |  | `pass | fail` |
+| Source and derived paths are bounded |  | `pass | fail` |
+| No gate, permission, security, persistence, architecture, external API, CLI or release impact |  | `pass | fail` |
+| Deterministic propagation is defined when derived paths exist |  | `pass | fail | not_applicable` |
+| Deterministic validation is defined |  | `pass | fail` |
+| Candidate paths are clean at baseline |  | `pass | fail` |
+## Execution Evidence
+| Evidence | Source | Result |
+|---|---|---|
+| Changed paths since baseline |  | `pass | fail` |
+| Propagation command |  | `pass | fail | not_applicable` |
+| Validation commands |  | `pass | fail` |
+## Mini-Closeout
+- delivered:
+- intentionally_not_delivered:
+- escalation_result: none
+- residual_risk: none
+- next_step:
+This compact record is valid only for a Brownfield-selected `verified_change`. Any missing, failed or ambiguous condition must set `status: escalated` and continue at `escalation_target`.

package/generated/.github/skills/agdf-runtime-contract.md CHANGED Viewed

@@ -27,6 +27,20 @@ Use this compact output shape when no formal gate artefact is required:
 Do not add a separate `Quality outlook` line for pure Quick Tasks unless the task became a relevant run.
+### Verified Change
+`verified_change` is a compact, fail-closed path for a bounded user-visible change with one canonical owner and deterministic proof. It is neither a prose exception nor a new user approval gate.
+After `Approval: UR`, Brownfield Review may select `verified_change` only when a durable `VERIFIED_CHANGE.md` record can prove all of the following before implementation:
+1. exactly one repository-relative canonical owner and bounded source/derived paths;
+2. no gate, permission, security, persistence, architecture, external API, CLI or release behavior impact;
+3. deterministic propagation when derived paths exist, plus at least one deterministic validation command;
+4. tracked and untracked worktree baseline paths captured before eligibility, with no candidate path already dirty; and
+5. an explicit `structured_slice` or `structured_delivery` escalation target.
+The record is the compact eligibility, execution and mini-closeout artefact. A missing, failed, unknown or ambiguous field/check must fail closed: mark the record `escalated` and continue at its declared structured target. Unrelated paths already dirty at baseline remain isolated; newly introduced unlisted paths invalidate the compact path. An executed record requires passing validation evidence and, where applicable, passing propagation evidence.
 ### Non-Normative Trivial Change Boundary
 A `quick_task` whose entire diff stays fully outside all of the following paths may close using only
@@ -68,10 +82,10 @@ the full existing ceremony unchanged:
 When a run needs an operational status view, use the Run Status Card as a compact projection of existing control state.
 It must not introduce a second gate model or override `agdf-gate-check`, `delivery-map`, QA, OR, or user approvals.
-- `mode`: `quick_task | structured_delivery | unknown`
+- `mode`: `quick_task | verified_change | structured_delivery | unknown`
 - `status`: `open | blocked | pass | warn | revise | block | in_progress`
 - `current_gate`: current user gate or internal step
-- `mode_slice_decision`: `undecided | quick_task | structured_slice | structured_delivery | block`
+- `mode_slice_decision`: `undecided | quick_task | verified_change | structured_slice | structured_delivery | block`
 - `allowed_now`: outputs or actions currently permitted
 - `forbidden_now`: outputs or actions currently forbidden
 - `blocking_condition`: current blocker or `none`
@@ -232,7 +246,8 @@ section or any other existing line.
 ## Gate Rules
 - User gates: `UR -> PRD -> SD -> TP -> QA -> UAT`
-- Internal mandatory steps: `Brownfield Review -> Mode/Slice Decision -> Brownfield Analysis -> CD+Tests -> CR -> OR`
+- Internal mandatory steps: `Brownfield Review -> Mode/Slice Decision -> Verified Change Execution | Brownfield Analysis -> CD+Tests -> CR -> OR`
+- On the approved-TP path, `CD+Tests` and `CR` are satisfied only by `done`; `not_applicable` may satisfy Brownfield Review or Brownfield Analysis, but it must not bypass implementation/test evidence or mandatory Code Review.
 - Exact approval formula: `Approval: <GateName>`
 - Legacy alias: `Freigabe: <GateName>` may be accepted when reviewing older German runs, but all new outputs must use `Approval: <GateName>`.
 - Implicit consent is not approval. Phrases such as "ok", "go ahead", "do it", "approved", "continue", "leg los" or "looks good" are work intent, not gate approval.
@@ -263,7 +278,7 @@ It is the sizing and routing step that decides how much later gate discipline is
 Its output is limited to:
 - workstream or follow-up-slice classification
-- `Mode/Slice Decision`: `quick_task | structured_slice | structured_delivery | block`
+- `Mode/Slice Decision`: `quick_task | verified_change | structured_slice | structured_delivery | block`
 - affected existing owners, source-of-truth artefacts, contracts, policies, runtime paths or tests
 - reuse-before-create risks and parallel-structure risks
 - open questions that PRD or SD must resolve
@@ -272,6 +287,7 @@ Its output is limited to:
 Mode/Slice Decision rules:
 - `quick_task`: use only when Brownfield Review shows a narrow local change, no new product semantics beyond the approved UR, no architecture/policy/persistence/contract expansion, and evidence is sufficient to proceed with a small implementation plus relevant checks.
+- `verified_change`: use only when the compact record can prove one canonical owner, bounded clean-at-baseline paths, no prohibited impact, deterministic propagation/validation and a structured escalation target. It skips later approvals only after every condition is evidenced and machine-validated.
 - `structured_slice`: use when some formal artefacts are needed, but they can stay intentionally small and scoped to the approved slice.
 - `structured_delivery`: use when the change has broad product, architecture, runtime, policy, persistence, release or cross-owner impact.
 - `block`: use when ownership, SoT, impact, evidence or product direction is not clear enough to choose a safe path.
@@ -286,14 +302,22 @@ This table is the canonical transition model. Skills may reference it, but must
 |---|---|---|---|---|
 | No approved UR | `UR` | clarify user need, formulate and persist UR, request `Approval: UR` | PRD, SD, TP, Brownfield Analysis, implementation, QA, release | `Approval: UR` |
 | `UR` approved and UR artefact persisted or linked, Brownfield Review missing | `Brownfield Review` | classify workstream, existing owners, SoT, reuse risks, change size and PRD/SD open questions; mark review done or not_applicable | PRD, SD, TP, implementation, QA, release | none |
-| Brownfield Review done or not_applicable, Mode/Slice Decision missing or incomplete | `Mode/Slice Decision` | decide `quick_task`, `structured_slice`, `structured_delivery` or `block`; record scope reason, evidence and required next gate depth | PRD, SD, TP, implementation, QA, release | none |
+| Brownfield Review done or not_applicable, Mode/Slice Decision missing or incomplete | `Mode/Slice Decision` | decide `quick_task`, `verified_change`, `structured_slice`, `structured_delivery` or `block`; record scope reason, evidence and required next gate depth | PRD, SD, TP, implementation, QA, release | none |
 | Mode/Slice Decision is `quick_task` | `Quick Task Execution` | implement only the narrow approved UR scope, run relevant checks, record evidence and OR-lite when the run is relevant | broad PRD/SD/TP by ritual, scope expansion, QA or release claims without evidence | none |
+| Mode/Slice Decision is `verified_change`, record missing/draft/invalid | `Verified Change Execution` | create or repair compact record, capture baseline and prove eligibility with doctor/agdf-gate-check | implementation, QA, UAT, release | none |
+| Verified Change record is `eligible` | `Verified Change Execution` | implement only declared paths, run declared propagation/validation, record mini-closeout | unlisted paths, prohibited impacts, QA/UAT/release claims | none |
+| Verified Change record is `executed` | `OR` | use mini-closeout and offer delivery closeout when requested | PRD/SD/TP/QA/UAT by ritual; automatic VCS actions | none |
+| Verified Change record is `escalated` | `PRD` | draft the PRD for declared `structured_slice` or `structured_delivery` escalation target | implementation through Verified Change | `Approval: PRD` |
 | Mode/Slice Decision is `structured_slice` or `structured_delivery`, PRD missing or draft | `PRD` | draft/refine PRD at the smallest justified depth, define scope, acceptance criteria and non-goals, persist/link PRD, request `Approval: PRD` | SD, TP, implementation-preparation Brownfield Analysis, implementation, QA, release | `Approval: PRD` |
 | `PRD` approved and PRD artefact persisted or linked, SD missing or draft | `SD` | draft/refine Solution Design, ownership and architecture, persist/link SD, request `Approval: SD` | TP, implementation, QA, release | `Approval: SD` |
 | `SD` approved and SD artefact persisted or linked, TP missing or draft | `TP` | draft/refine Task/Test Plan, task IDs, evidence plan, persist/link TP, request `Approval: TP` | implementation, QA, release | `Approval: TP` |
 | `TP` approved and TP artefact persisted or linked, Brownfield Analysis missing | `Brownfield Analysis` | run Brownfield Analysis for approved TP scope | implementation, QA, release | none |
 | Brownfield Analysis passed for approved TP | `CD+Tests` | implement approved TP tasks and run tests | QA pass, UAT, release | none |
+| `CD+Tests` done for approved TP, CR missing | `CR` | run mandatory Code Review and resolve blocking findings | QA pass, UAT, release | none |
+| `CR` done, QA not approved | `QA` | run QA gate, persist/refine QA report, request `Approval: QA` | UAT, release | `Approval: QA` |
 | `QA` approved but QA report missing or not pass | `QA` | persist/link QA report with `pass` decision or revise/block evidence | UAT, release | none |
+| QA approved and QA report is `pass` or `passed`, UAT not approved | `UAT` | request `Approval: UAT`, prepare non-operative delivery summary | release and automatic VCS actions | `Approval: UAT` |
+| UAT approved | `OR` | produce OR or delivery closeout; prepare VCS handoff only when requested | automatic commit, push, PR or release | none |
 ## Brownfield Modes

package/generated/.opencode/AGDF.md CHANGED Viewed

@@ -26,7 +26,7 @@ Codex and Claude Code plugin surfaces use unprefixed skill names because their p
 ## Mode Selection
 Default entry rule: a new user intent to build, add, change, extend, refactor or otherwise deliver something starts with `agdf-gate-check` unless it is clearly only a question, explanation, local inspection, or explicitly scoped review.
-Use Quick Task Mode for questions, small reviews, local debugging and narrow fixes without new product semantics.
+Use Quick Task Mode for questions, small reviews, local debugging and narrow fixes without new product semantics. Use Verified Change only after approved UR and Brownfield Review when the Runtime Contract's compact record can prove bounded ownership, clean-at-baseline paths, prohibited-impact absence and deterministic validation.
 Use Structured Delivery Mode for new capabilities, architecture, policy, persistence, release-critical work, formal artefacts or explicit approvals.
@@ -38,9 +38,9 @@ Those phrases may express intent to proceed, but they do not unlock a gate unles
 Do not infer active scope from branch names, uncommitted workspace deltas, chat history or generated summaries when durable artefacts point elsewhere.
 If multiple active scopes are plausible, list the evidenced lines and route to `agdf-gate-check` or workstate clarification instead of choosing silently.
 After `Approval: UR`, run lightweight Brownfield Review before PRD when Brownfield, ownership, runtime, policy, persistence, architecture, UI or UX impact is possible.
-Brownfield Review must produce a Mode/Slice Decision: `quick_task`, `structured_slice`, `structured_delivery` or `block`.
+Brownfield Review must produce a Mode/Slice Decision: `quick_task`, `verified_change`, `structured_slice`, `structured_delivery` or `block`.
 Make that decision visible before coding or drafting later artefacts: state the selected path, scope reason, evidence and next required gate in the live control state or linked artefact.
-Do not assume the full PRD/SD/TP chain before that decision; use only as much gate depth as the reviewed change size justifies.
+Do not assume the full PRD/SD/TP chain before that decision; use only as much gate depth as the reviewed change size justifies. A user-visible change is not automatically Verified Change eligible; any missing or ambiguous record condition escalates to the declared structured target before implementation.
 Quick Task Mode must still use the Runtime Contract mini-output: `result`, `evidence`, `risk`, `next_step`.
 Narrow defect work may use the Runtime Contract's Bug Lightweight Track only when a durable bug artefact or linked authoritative issue carries reproduction, actual behavior, expected behavior, fix boundary and evidence plan.

package/generated/.opencode/agdf-runtime-contract.md CHANGED Viewed

@@ -27,6 +27,20 @@ Use this compact output shape when no formal gate artefact is required:
 Do not add a separate `Quality outlook` line for pure Quick Tasks unless the task became a relevant run.
+### Verified Change
+`verified_change` is a compact, fail-closed path for a bounded user-visible change with one canonical owner and deterministic proof. It is neither a prose exception nor a new user approval gate.
+After `Approval: UR`, Brownfield Review may select `verified_change` only when a durable `VERIFIED_CHANGE.md` record can prove all of the following before implementation:
+1. exactly one repository-relative canonical owner and bounded source/derived paths;
+2. no gate, permission, security, persistence, architecture, external API, CLI or release behavior impact;
+3. deterministic propagation when derived paths exist, plus at least one deterministic validation command;
+4. tracked and untracked worktree baseline paths captured before eligibility, with no candidate path already dirty; and
+5. an explicit `structured_slice` or `structured_delivery` escalation target.
+The record is the compact eligibility, execution and mini-closeout artefact. A missing, failed, unknown or ambiguous field/check must fail closed: mark the record `escalated` and continue at its declared structured target. Unrelated paths already dirty at baseline remain isolated; newly introduced unlisted paths invalidate the compact path. An executed record requires passing validation evidence and, where applicable, passing propagation evidence.
 ### Non-Normative Trivial Change Boundary
 A `quick_task` whose entire diff stays fully outside all of the following paths may close using only
@@ -68,10 +82,10 @@ the full existing ceremony unchanged:
 When a run needs an operational status view, use the Run Status Card as a compact projection of existing control state.
 It must not introduce a second gate model or override `agdf-gate-check`, `delivery-map`, QA, OR, or user approvals.
-- `mode`: `quick_task | structured_delivery | unknown`
+- `mode`: `quick_task | verified_change | structured_delivery | unknown`
 - `status`: `open | blocked | pass | warn | revise | block | in_progress`
 - `current_gate`: current user gate or internal step
-- `mode_slice_decision`: `undecided | quick_task | structured_slice | structured_delivery | block`
+- `mode_slice_decision`: `undecided | quick_task | verified_change | structured_slice | structured_delivery | block`
 - `allowed_now`: outputs or actions currently permitted
 - `forbidden_now`: outputs or actions currently forbidden
 - `blocking_condition`: current blocker or `none`
@@ -232,7 +246,8 @@ section or any other existing line.
 ## Gate Rules
 - User gates: `UR -> PRD -> SD -> TP -> QA -> UAT`
-- Internal mandatory steps: `Brownfield Review -> Mode/Slice Decision -> Brownfield Analysis -> CD+Tests -> CR -> OR`
+- Internal mandatory steps: `Brownfield Review -> Mode/Slice Decision -> Verified Change Execution | Brownfield Analysis -> CD+Tests -> CR -> OR`
+- On the approved-TP path, `CD+Tests` and `CR` are satisfied only by `done`; `not_applicable` may satisfy Brownfield Review or Brownfield Analysis, but it must not bypass implementation/test evidence or mandatory Code Review.
 - Exact approval formula: `Approval: <GateName>`
 - Legacy alias: `Freigabe: <GateName>` may be accepted when reviewing older German runs, but all new outputs must use `Approval: <GateName>`.
 - Implicit consent is not approval. Phrases such as "ok", "go ahead", "do it", "approved", "continue", "leg los" or "looks good" are work intent, not gate approval.
@@ -263,7 +278,7 @@ It is the sizing and routing step that decides how much later gate discipline is
 Its output is limited to:
 - workstream or follow-up-slice classification
-- `Mode/Slice Decision`: `quick_task | structured_slice | structured_delivery | block`
+- `Mode/Slice Decision`: `quick_task | verified_change | structured_slice | structured_delivery | block`
 - affected existing owners, source-of-truth artefacts, contracts, policies, runtime paths or tests
 - reuse-before-create risks and parallel-structure risks
 - open questions that PRD or SD must resolve
@@ -272,6 +287,7 @@ Its output is limited to:
 Mode/Slice Decision rules:
 - `quick_task`: use only when Brownfield Review shows a narrow local change, no new product semantics beyond the approved UR, no architecture/policy/persistence/contract expansion, and evidence is sufficient to proceed with a small implementation plus relevant checks.
+- `verified_change`: use only when the compact record can prove one canonical owner, bounded clean-at-baseline paths, no prohibited impact, deterministic propagation/validation and a structured escalation target. It skips later approvals only after every condition is evidenced and machine-validated.
 - `structured_slice`: use when some formal artefacts are needed, but they can stay intentionally small and scoped to the approved slice.
 - `structured_delivery`: use when the change has broad product, architecture, runtime, policy, persistence, release or cross-owner impact.
 - `block`: use when ownership, SoT, impact, evidence or product direction is not clear enough to choose a safe path.
@@ -286,14 +302,22 @@ This table is the canonical transition model. Skills may reference it, but must
 |---|---|---|---|---|
 | No approved UR | `UR` | clarify user need, formulate and persist UR, request `Approval: UR` | PRD, SD, TP, Brownfield Analysis, implementation, QA, release | `Approval: UR` |
 | `UR` approved and UR artefact persisted or linked, Brownfield Review missing | `Brownfield Review` | classify workstream, existing owners, SoT, reuse risks, change size and PRD/SD open questions; mark review done or not_applicable | PRD, SD, TP, implementation, QA, release | none |
-| Brownfield Review done or not_applicable, Mode/Slice Decision missing or incomplete | `Mode/Slice Decision` | decide `quick_task`, `structured_slice`, `structured_delivery` or `block`; record scope reason, evidence and required next gate depth | PRD, SD, TP, implementation, QA, release | none |
+| Brownfield Review done or not_applicable, Mode/Slice Decision missing or incomplete | `Mode/Slice Decision` | decide `quick_task`, `verified_change`, `structured_slice`, `structured_delivery` or `block`; record scope reason, evidence and required next gate depth | PRD, SD, TP, implementation, QA, release | none |
 | Mode/Slice Decision is `quick_task` | `Quick Task Execution` | implement only the narrow approved UR scope, run relevant checks, record evidence and OR-lite when the run is relevant | broad PRD/SD/TP by ritual, scope expansion, QA or release claims without evidence | none |
+| Mode/Slice Decision is `verified_change`, record missing/draft/invalid | `Verified Change Execution` | create or repair compact record, capture baseline and prove eligibility with doctor/agdf-gate-check | implementation, QA, UAT, release | none |
+| Verified Change record is `eligible` | `Verified Change Execution` | implement only declared paths, run declared propagation/validation, record mini-closeout | unlisted paths, prohibited impacts, QA/UAT/release claims | none |
+| Verified Change record is `executed` | `OR` | use mini-closeout and offer delivery closeout when requested | PRD/SD/TP/QA/UAT by ritual; automatic VCS actions | none |
+| Verified Change record is `escalated` | `PRD` | draft the PRD for declared `structured_slice` or `structured_delivery` escalation target | implementation through Verified Change | `Approval: PRD` |
 | Mode/Slice Decision is `structured_slice` or `structured_delivery`, PRD missing or draft | `PRD` | draft/refine PRD at the smallest justified depth, define scope, acceptance criteria and non-goals, persist/link PRD, request `Approval: PRD` | SD, TP, implementation-preparation Brownfield Analysis, implementation, QA, release | `Approval: PRD` |
 | `PRD` approved and PRD artefact persisted or linked, SD missing or draft | `SD` | draft/refine Solution Design, ownership and architecture, persist/link SD, request `Approval: SD` | TP, implementation, QA, release | `Approval: SD` |
 | `SD` approved and SD artefact persisted or linked, TP missing or draft | `TP` | draft/refine Task/Test Plan, task IDs, evidence plan, persist/link TP, request `Approval: TP` | implementation, QA, release | `Approval: TP` |
 | `TP` approved and TP artefact persisted or linked, Brownfield Analysis missing | `Brownfield Analysis` | run Brownfield Analysis for approved TP scope | implementation, QA, release | none |
 | Brownfield Analysis passed for approved TP | `CD+Tests` | implement approved TP tasks and run tests | QA pass, UAT, release | none |
+| `CD+Tests` done for approved TP, CR missing | `CR` | run mandatory Code Review and resolve blocking findings | QA pass, UAT, release | none |
+| `CR` done, QA not approved | `QA` | run QA gate, persist/refine QA report, request `Approval: QA` | UAT, release | `Approval: QA` |
 | `QA` approved but QA report missing or not pass | `QA` | persist/link QA report with `pass` decision or revise/block evidence | UAT, release | none |
+| QA approved and QA report is `pass` or `passed`, UAT not approved | `UAT` | request `Approval: UAT`, prepare non-operative delivery summary | release and automatic VCS actions | `Approval: UAT` |
+| UAT approved | `OR` | produce OR or delivery closeout; prepare VCS handoff only when requested | automatic commit, push, PR or release | none |
 ## Brownfield Modes

package/generated/AGENTS.md CHANGED Viewed

@@ -26,7 +26,7 @@ Codex and Claude Code plugin surfaces use the same canonical router with unprefi
 ## Mode Selection
 Default entry rule: a new user intent to build, add, change, extend, refactor or otherwise deliver something starts with `agdf-gate-check` unless it is clearly only a question, explanation, local inspection, or explicitly scoped review.
-Use Quick Task Mode for questions, small reviews, local debugging and narrow fixes without new product semantics.
+Use Quick Task Mode for questions, small reviews, local debugging and narrow fixes without new product semantics. Use Verified Change only after approved UR and Brownfield Review when the Runtime Contract's compact record can prove bounded ownership, clean-at-baseline paths, prohibited-impact absence and deterministic validation.
 Use Structured Delivery Mode for new capabilities, architecture, policy, persistence, release-critical work, formal artefacts or explicit approvals.
@@ -38,9 +38,9 @@ Those phrases may express intent to proceed, but they do not unlock a gate unles
 Do not infer active scope from branch names, uncommitted workspace deltas, chat history or generated summaries when durable artefacts point elsewhere.
 If multiple active scopes are plausible, list the evidenced lines and route to `agdf-gate-check` or workstate clarification instead of choosing silently.
 After `Approval: UR`, run lightweight Brownfield Review before PRD when Brownfield, ownership, runtime, policy, persistence, architecture, UI or UX impact is possible.
-Brownfield Review must produce a Mode/Slice Decision: `quick_task`, `structured_slice`, `structured_delivery` or `block`.
+Brownfield Review must produce a Mode/Slice Decision: `quick_task`, `verified_change`, `structured_slice`, `structured_delivery` or `block`.
 Make that decision visible before coding or drafting later artefacts: state the selected path, scope reason, evidence and next required gate in the live control state or linked artefact.
-Do not assume the full PRD/SD/TP chain before that decision; use only as much gate depth as the reviewed change size justifies.
+Do not assume the full PRD/SD/TP chain before that decision; use only as much gate depth as the reviewed change size justifies. A user-visible change is not automatically Verified Change eligible; any missing or ambiguous record condition escalates to the declared structured target before implementation.
 Quick Task Mode must still use the Runtime Contract mini-output: `result`, `evidence`, `risk`, `next_step`.
 Narrow defect work may use the Runtime Contract's Bug Lightweight Track only when a durable bug artefact or linked authoritative issue carries reproduction, actual behavior, expected behavior, fix boundary and evidence plan.

package/generated/plugins/agdf/.codex-plugin/plugin.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "agdf",
-  "version": "0.6.9",
+  "version": "0.7.1",
   "description": "Codex-first operating system for governed AI-assisted delivery.",
   "author": {
     "name": "Arndt Gold",
@@ -32,7 +32,7 @@
     "composerIcon": "./assets/agdf-icon.svg",
     "logo": "./assets/agdf-logo.svg",
     "defaultPrompt": [
-      "Evaluate whether AGDF is appropriate for this repository and request. Explain its purpose, practical value, governance overhead, and fit for the project's risk level. Recommend the smallest suitable AGDF path before proposing implementation.",
+      "Assess whether AGDF is proportionate for this repository and request before proposing any implementation. Explain AGDF's purpose and practical benefits, weigh governance overhead against the project's delivery risk, and recommend the lightest suitable path — or explicitly advise against AGDF where it would add more process than value.",
       "Start this request under AGDF governance.",
       "Create durable AGDF control state for this repository.",
       "Close this delivery run with an auditable AGDF report."

package/generated/plugins/agdf/control/README.md CHANGED Viewed

@@ -14,6 +14,7 @@ Use this scaffold when a target repository should keep AGDF state outside chat h
 | `templates/MASTER_BACKLOG.md` | Template for the living backlog pointer: active initiatives and current UR/Brownfield/PRD/SD/TP/QA/OR artefacts |
 | `templates/artefacts/UR.md` | Template for the durable user requirement artefact of a work item |
 | `templates/artefacts/BROWNFIELD_REVIEW.md` | Template for the durable Brownfield Review and Mode/Slice Decision |
+| `templates/artefacts/VERIFIED_CHANGE.md` | Compact fail-closed record for an eligible Verified Change |
 | `templates/artefacts/PRD.md` | Template for the durable product requirements artefact |
 | `templates/artefacts/SD.md` | Template for the durable solution design artefact |
 | `templates/artefacts/TP.md` | Template for the durable task and test plan artefact |
@@ -84,7 +85,7 @@ npx --yes @agdf/cli@latest gate-check --json
 - The selected `runs/<run_id>/RUN_STATE.md` is the current run dashboard.
 - `config.json` stores the project preference for artefact and chat language; runtime rules stay English.
 - `MASTER_BACKLOG.md` points to active delivery work; detailed artefacts live beside the work item.
-- Brownfield Review records the post-UR Mode/Slice Decision before PRD depth or Quick Task execution is chosen.
+- Brownfield Review records the post-UR Mode/Slice Decision before PRD depth, Verified Change execution or Quick Task execution is chosen.
 - UR, PRD, SD, TP and QA decisions require durable artefacts or links to the authoritative repository source of truth before the next gate can open.
 - OR records the run closeout and next permissible step; it does not approve later gates.
 - `SOT_REGISTRY.md` decides which document owns which domain.

package/generated/plugins/agdf/control/templates/AGDF_RUN.md CHANGED Viewed

@@ -4,8 +4,8 @@
 - run_id:
 - started_at:
-- mode: `quick_task | structured_delivery`
-- current_gate: `none | UR | Brownfield Review | Mode/Slice Decision | PRD | SD | TP | Quick Task Execution | Brownfield Analysis | CD+Tests | CR | QA | UAT | OR`
+- mode: `quick_task | verified_change | structured_delivery`
+- current_gate: `none | UR | Brownfield Review | Mode/Slice Decision | PRD | SD | TP | Quick Task Execution | Verified Change Execution | Brownfield Analysis | CD+Tests | CR | QA | UAT | OR`
 - decision: `pass | revise | block | in_progress`
 - owner:
@@ -68,6 +68,7 @@ Valid approval format for new runs: `Approval: <GateName>`.
 | SD |  | `draft | approved | superseded | not_applicable` |  |
 | TP |  | `draft | approved | superseded | not_applicable` |  |
 | Brownfield Review |  | `missing | draft | done | not_applicable | superseded` |  |
+| Verified Change |  | `missing | draft | eligible | executed | escalated` |  |
 | Review |  | `missing | done | not_applicable` |  |
 | QA |  | `missing | pass | revise | block | not_applicable` |  |
 | OR |  | `missing | done | not_applicable` |  |
@@ -77,7 +78,7 @@ Valid approval format for new runs: `Approval: <GateName>`.
 Set this after Brownfield Review. Do not assume the full gate chain before the existing-system impact is understood.
 Quick Task execution or implementation is not allowed until this decision is visible with scope reason and evidence.
-- decision: `undecided | quick_task | structured_slice | structured_delivery | block`
+- decision: `undecided | quick_task | verified_change | structured_slice | structured_delivery | block`
 - required_next_gate: `none | PRD | SD | TP | Brownfield Analysis`
 - scope_reason:
 - evidence:

package/generated/plugins/agdf/control/templates/RUN_STATE.md CHANGED Viewed

@@ -37,6 +37,28 @@ Describe the trustworthy outcome.
 | QA | missing |  |
 | UAT | missing |  |
+## Artefacts
+| Type | Path | Status | Notes |
+|---|---|---|---|
+| UR |  | draft |  |
+| Brownfield Review |  | missing |  |
+| Verified Change |  | missing |  |
+| PRD |  | missing |  |
+| SD |  | missing |  |
+| TP |  | missing |  |
+| Brownfield Analysis |  | missing |  |
+| CD+Tests |  | missing |  |
+| CR |  | missing |  |
+| QA |  | missing |  |
+## Mode/Slice Decision
+- decision: `quick_task | verified_change | structured_slice | structured_delivery | block`
+- required_next_gate:
+- scope_reason:
+- evidence:
 ## Evidence
 | Evidence | Source | Covers | Strength |

package/generated/plugins/agdf/control/templates/artefacts/BROWNFIELD_REVIEW.md CHANGED Viewed

@@ -37,7 +37,7 @@ What approved UR scope is being sized and routed?
 ## Mode / Slice Decision
-- decision: `quick_task | structured_slice | structured_delivery | block`
+- decision: `quick_task | verified_change | structured_slice | structured_delivery | block`
 - required_next_gate: `none | PRD | SD | TP | Brownfield Analysis`
 - scope_reason:
 - evidence:

package/generated/plugins/agdf/control/templates/artefacts/VERIFIED_CHANGE.md ADDED Viewed

@@ -0,0 +1,48 @@
+# Verified Change: <Title>
+Status: `draft | eligible | executed | escalated`
+## Record
+- status: draft
+- related_ur:
+- escalation_target: `structured_slice | structured_delivery`
+- canonical_owner:
+- allowed_source_paths:
+- allowed_derived_paths: none
+- prohibited_impacts: none
+- propagation_command: none
+- validation_commands:
+- baseline_tracked_paths: none
+- baseline_untracked_paths: none
+- validation_status: pending
+- propagation_status: not_applicable
+## Eligibility Assertions
+| Condition | Evidence | Status |
+|---|---|---|
+| Exactly one canonical owner |  | `pass | fail` |
+| Source and derived paths are bounded |  | `pass | fail` |
+| No gate, permission, security, persistence, architecture, external API, CLI or release impact |  | `pass | fail` |
+| Deterministic propagation is defined when derived paths exist |  | `pass | fail | not_applicable` |
+| Deterministic validation is defined |  | `pass | fail` |
+| Candidate paths are clean at baseline |  | `pass | fail` |
+## Execution Evidence
+| Evidence | Source | Result |
+|---|---|---|
+| Changed paths since baseline |  | `pass | fail` |
+| Propagation command |  | `pass | fail | not_applicable` |
+| Validation commands |  | `pass | fail` |
+## Mini-Closeout
+- delivered:
+- intentionally_not_delivered:
+- escalation_result: none
+- residual_risk: none
+- next_step:
+This compact record is valid only for a Brownfield-selected `verified_change`. Any missing, failed or ambiguous condition must set `status: escalated` and continue at `escalation_target`.

package/generated/plugins/agdf/meta/agdf-agent-router.md CHANGED Viewed

@@ -27,7 +27,7 @@ That `agdf-` prefix is reserved for GitHub Copilot repository skills, where no p
 ## Mode Selection
 Default entry rule: a new user intent to build, add, change, extend, refactor or otherwise deliver something starts with `gate-check` unless it is clearly only a question, explanation, local inspection, or explicitly scoped review.
-Use Quick Task Mode for questions, small reviews, local debugging and narrow fixes without new product semantics.
+Use Quick Task Mode for questions, small reviews, local debugging and narrow fixes without new product semantics. Use Verified Change only after approved UR and Brownfield Review when the Runtime Contract's compact record can prove bounded ownership, clean-at-baseline paths, prohibited-impact absence and deterministic validation.
 Use Structured Delivery Mode for new capabilities, architecture, policy, persistence, release-critical work, formal artefacts or explicit approvals.
@@ -39,9 +39,9 @@ Those phrases may express intent to proceed, but they do not unlock a gate unles
 Do not infer active scope from branch names, uncommitted workspace deltas, chat history or generated summaries when durable artefacts point elsewhere.
 If multiple active scopes are plausible, list the evidenced lines and route to `gate-check` or workstate clarification instead of choosing silently.
 After `Approval: UR`, run lightweight Brownfield Review before PRD when Brownfield, ownership, runtime, policy, persistence, architecture, UI or UX impact is possible.
-Brownfield Review must produce a Mode/Slice Decision: `quick_task`, `structured_slice`, `structured_delivery` or `block`.
+Brownfield Review must produce a Mode/Slice Decision: `quick_task`, `verified_change`, `structured_slice`, `structured_delivery` or `block`.
 Make that decision visible before coding or drafting later artefacts: state the selected path, scope reason, evidence and next required gate in the live control state or linked artefact.
-Do not assume the full PRD/SD/TP chain before that decision; use only as much gate depth as the reviewed change size justifies.
+Do not assume the full PRD/SD/TP chain before that decision; use only as much gate depth as the reviewed change size justifies. A user-visible change is not automatically Verified Change eligible; any missing or ambiguous record condition escalates to the declared structured target before implementation.
 Quick Task Mode must still use the Runtime Contract mini-output: `result`, `evidence`, `risk`, `next_step`.
 Narrow defect work may use the Runtime Contract's Bug Lightweight Track only when a durable bug artefact or linked authoritative issue carries reproduction, actual behavior, expected behavior, fix boundary and evidence plan.

package/generated/plugins/agdf/meta/agdf-constitution.md CHANGED Viewed

@@ -184,11 +184,11 @@ Gate Discipline
 AGDF work follows a gate-driven flow:
-    UR → Brownfield Review → Mode/Slice Decision → PRD/SD/TP as needed → QA → UAT
+    UR → Brownfield Review → Mode/Slice Decision → Verified Change or PRD/SD/TP as needed → QA → UAT
 with internal process steps:
-    Brownfield Review → Mode/Slice Decision → Brownfield Analysis → CD+Tests → CR → OR
+    Brownfield Review → Mode/Slice Decision → Verified Change Execution or Brownfield Analysis → CD+Tests → CR → OR
 Rules:
@@ -208,7 +208,7 @@ Rules:
   internal mandatory step.
 * **Size before ceremony**: After an approved durable UR, Brownfield Review
   determines change size and routing before PRD depth is chosen. The Mode/Slice
-  Decision is one of `quick_task`, `structured_slice`, `structured_delivery` or
+  Decision is one of `quick_task`, `verified_change`, `structured_slice`, `structured_delivery` or
   `block`.
 * **No gate leaks**: Later gate artefacts must not be produced when an
   earlier gate is still blocking.

package/generated/plugins/agdf/meta/agdf-plugin.definition.json CHANGED Viewed

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
   "id": "agdf",
-  "version": "0.6.9",
+  "version": "0.7.1",
   "displayName": "AI Governance & Delivery Framework",
   "developerName": "Arndt Gold",
   "description": "Codex-first operating system for governed AI-assisted delivery.",
@@ -35,7 +35,7 @@
       "Write"
     ],
     "defaultPrompt": [
-      "Evaluate whether AGDF is appropriate for this repository and request. Explain its purpose, practical value, governance overhead, and fit for the project's risk level. Recommend the smallest suitable AGDF path before proposing implementation.",
+      "Assess whether AGDF is proportionate for this repository and request before proposing any implementation. Explain AGDF's purpose and practical benefits, weigh governance overhead against the project's delivery risk, and recommend the lightest suitable path — or explicitly advise against AGDF where it would add more process than value.",
       "Start this request under AGDF governance.",
       "Create durable AGDF control state for this repository.",
       "Close this delivery run with an auditable AGDF report."