From 36033a5e22c06005b40400304863c13b429a8ba8 Mon Sep 17 00:00:00 2001 From: tegwick Date: Wed, 29 Jul 2026 20:02:48 +0200 Subject: [PATCH] =?UTF-8?q?Fix=20TargetRevenueFrameworkCore=20=C2=A71.11?= =?UTF-8?q?=20extension-redefinition=20scope=20drift?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit WP-0003-T06 review finding: §1.11 paraphrased concept §7.11's closed extension-redefinition list (Phase, Initial Target, Development Credit, Remission Credit, Outstanding Target, Conversion Event, Future License) as "any term in this section" - silently broadening the constitutional boundary to also cover Milestone Release, Target Multiple, Trust Service, and Monetization Profile/Extension itself. This created an inconsistency with MonetizationExtensionSpecification.md §3, which already carried the concept's narrower list correctly, and would have left the extract and its sibling document silently disagreeing on what an extension may not touch. Corrected §1.11 to quote the closed list verbatim, matching the concept, MonetizationExtensionSpecification.md, TSD §5, and PRD FR-4 (all four of which already had it right). Whether the broader rule might be desirable is a separate design question from this faithfulness fix, and is not addressed here. Co-Authored-By: Claude Sonnet 5 --- specs/TargetRevenueFrameworkCore.md | 2 +- .../TREV-WP-0003-normative-core-extraction.md | 14 ++++++++++++-- 2 files changed, 13 insertions(+), 3 deletions(-) diff --git a/specs/TargetRevenueFrameworkCore.md b/specs/TargetRevenueFrameworkCore.md index e20afce..5ce529d 100644 --- a/specs/TargetRevenueFrameworkCore.md +++ b/specs/TargetRevenueFrameworkCore.md @@ -72,7 +72,7 @@ The publication, accounting, metrics, evidence, and attestation infrastructure f ### 1.11 Monetization Profile or Extension -A standardized or project-specific declaration describing what value is supplied, how it is priced, how payments are allocated, when allocations are recognized, how reversals are handled, and what evidence is required. May not redefine the core meaning of any term in this section. +A standardized or project-specific declaration describing what value is supplied, how it is priced, how payments are allocated, when allocations are recognized, how reversals are handled, and what evidence is required. May not redefine the core meaning of Phase, Initial Target, Development Credit, Remission Credit, Outstanding Target, Conversion Event, or Future License — this closed list, not "any term in this section," is the constitutional boundary (concept §7.11 verbatim; Milestone Release, Target Multiple, Trust Service, and this term itself are deliberately not on it). --- diff --git a/workplans/TREV-WP-0003-normative-core-extraction.md b/workplans/TREV-WP-0003-normative-core-extraction.md index c40a0ff..317e40b 100644 --- a/workplans/TREV-WP-0003-normative-core-extraction.md +++ b/workplans/TREV-WP-0003-normative-core-extraction.md @@ -184,10 +184,20 @@ diff and a short review checklist. **Review checklist prepared 2026-07-29** (task remains `todo` pending human accept): -- [ ] `specs/TargetRevenueFrameworkCore.md` — terms in §1 match concept §7 +- [x] `specs/TargetRevenueFrameworkCore.md` — terms in §1 match concept §7 wording; formula in §2 matches concept §8; five verbs (§3) and nine rules (§4) copied without paraphrase drift; §7 invariants match concept - §22 twelve items exactly. + §22 twelve items exactly. **Reviewed and accepted 2026-07-29, one fix + applied:** §1.11 had paraphrased concept §7.11's closed extension- + redefinition list ("Phase, Initial Target, Development Credit, + Remission Credit, Outstanding Target, Conversion Event, or Future + License") as "any term in this section" — silently broadening the + constitutional boundary to also cover Milestone Release, Target + Multiple, Trust Service, and Monetization Profile/Extension itself, + and creating an inconsistency with `MonetizationExtensionSpecification.md` + §3, which already carried the concept's narrower list correctly. + Corrected §1.11 to quote the closed list verbatim; confirmed no other + document (TSD §5, PRD FR-4) carries the broadened version. - [ ] `specs/PhaseManifestSpecification.md` — field tiers match `schemas/phase_manifest.schema.json` (already implemented, WP-0002-T02); `phase.longstop_at` is explicitly labeled a Stage 0 working default