coulomb/target-revenue
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

WP-0003-T06 review: cross-link polish for full pointer symmetry

Browse source 
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:
tegwick 2026-07-29 20:12:58 +02:00
parent 54bfc726fa
commit 6b34c05e35
3 changed files with 13 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

2
CONTRIBUTING.md
View file

@ -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.

2
specs/ProductRequirementsDocument.md
View file

@ -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.
---

13
workplans/TREV-WP-0003-normative-core-extraction.md
View file

@ -231,9 +231,18 @@ accept):
the six canonical candidates match concept §12.2's list in the same
order, with the two unfixtured profiles honestly labeled rather than
implied complete.
- [ ] Cross-links (T05) — confirm PRD §6.1/§6.2, TSD §0/§1.1, README, and
- [x] Cross-links (T05) — confirm PRD §6.1/§6.2, TSD §0/§1.1, README, and
CONTRIBUTING.md all point at the new extracts without contradicting
`specs/TargetRevenueLicenseConcept.md` as ultimate authority.
`specs/TargetRevenueLicenseConcept.md` as ultimate authority. **Reviewed
and accepted 2026-07-29 as polish-only, two fixes applied:** added the
same "ultimate source / day-to-day reference" dual-citation to the
PRD header's Terminology alignment line (previously only in
README/TSD/CONTRIBUTING); named all three other 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.
- [ ] No open question (concept §24) is answered by omission — each extract
either cites a working default explicitly or states the item remains
open.