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
|
|
@ -17,7 +17,7 @@ This repository defines a **framework concept and specifications**. It does not
|
|||
|
||||
## Terminology
|
||||
|
||||
Use the normative terms from `specs/TargetRevenueLicenseConcept.md` §7 (day-to-day reference: `specs/TargetRevenueFrameworkCore.md` §1). Do **not** reintroduce ambiguous synonyms for conversion metrics (e.g. treating total project “revenue captured” as equivalent to Development Credit).
|
||||
Use the normative terms from `specs/TargetRevenueLicenseConcept.md` (ultimate source). Day-to-day reference — extracted and stabilized, not a source of variant meaning — is: `specs/TargetRevenueFrameworkCore.md` §1 (core terms), `specs/PhaseManifestSpecification.md` (Phase Manifest fields), `specs/TargetLedgerSpecification.md` (ledger entries, fold), and `specs/MonetizationExtensionSpecification.md` (extension contract). Do **not** reintroduce ambiguous synonyms for conversion metrics (e.g. treating total project “revenue captured” as equivalent to Development Credit).
|
||||
|
||||
Pre-conversion software is **source-available**, not OSI Open Source.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue