WP-0003-T06 review: cross-link polish for full pointer symmetry
Per reviewer request (polish only, item 5): added the same "ultimate source / day-to-day reference" dual-citation to the PRD header's Terminology alignment line, matching README/TSD/CONTRIBUTING. Named all three other normative extracts (PhaseManifestSpecification.md, TargetLedgerSpecification.md, MonetizationExtensionSpecification.md) in CONTRIBUTING.md's Terminology section, which previously named only TargetRevenueFrameworkCore.md - now symmetric with README's full four-document table. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
parent
54bfc726fa
commit
6b34c05e35
3 changed files with 13 additions and 4 deletions
|
|
@ -6,7 +6,7 @@ Owner: target-revenue initiative
|
|||
Primary artifacts: `INTENT.md`, `SCOPE.md`, `specs/TargetRevenueLicenseConcept.md`, `history/260728-InitialExploration.md`
|
||||
Living scope: `SCOPE.md` states Stage 0 in/out boundaries and workplan sequencing (normative extract + schemas/fold before hosted Trust Service).
|
||||
Working defaults: `specs/OpenQuestions-WorkingDefaults.md` holds provisional answers to §14 items for Stage 0 unblocking; promotion into core requires human accept.
|
||||
Terminology alignment: This document does not redefine terms already normatively defined in `specs/TargetRevenueLicenseConcept.md`. Where a definitive formula, rule, or schema already exists there, this PRD references it rather than restating it with variation.
|
||||
Terminology alignment: This document does not redefine terms already normatively defined in `specs/TargetRevenueLicenseConcept.md` (ultimate source; day-to-day reference: `specs/TargetRevenueFrameworkCore.md` §1). Where a definitive formula, rule, or schema already exists there, this PRD references it rather than restating it with variation.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue