Extract normative core docs (TREV-WP-0003 T01-T05)
Stabilizes day-to-day terminology out of the exploratory concept draft: - specs/TargetRevenueFrameworkCore.md — core terms, target formula, five-verb lifecycle, nine rules, invariants. - specs/PhaseManifestSpecification.md — field tiers aligned with schemas/phase_manifest.schema.json. - specs/TargetLedgerSpecification.md — entry types, hash chain, pure Outstanding Target fold, aligned with the WP-0002 library. - specs/MonetizationExtensionSpecification.md — six-field contract, registered/canonical distinction, Stage 0 Q11 catalog. Cross-links PRD/TSD/README/CONTRIBUTING to the new extracts, confirms no placeholder tails remain, and prepares a review checklist for T06 (human promotion gate, left open pending maintainer review). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
parent
9279c7a3bb
commit
7d6b4f4f50
9 changed files with 557 additions and 21 deletions
|
|
@ -17,7 +17,7 @@ This repository defines a **framework concept and specifications**. It does not
|
|||
|
||||
## Terminology
|
||||
|
||||
Use the normative terms from `spec/TargetRevenueLicenseConcept.md` §7. 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 `spec/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).
|
||||
|
||||
Pre-conversion software is **source-available**, not OSI Open Source.
|
||||
|
||||
|
|
@ -34,8 +34,8 @@ A Developer Certificate of Origin (DCO) alone is **not** assumed sufficient for
|
|||
The following must not be marked complete by agents alone without explicit human accept (comment, decision record, or maintainer message):
|
||||
|
||||
- Non-binding TRSL draft skeleton (WP-0001-T06)
|
||||
- Library/stack ADR that locks implementation technology (WP-0002-T01)
|
||||
- Promotion of working defaults into normative core wording
|
||||
- Library/stack ADR that locks implementation technology (WP-0002-T01 — **accepted 2026-07-29**, see ADR-0001)
|
||||
- Promotion of working defaults into normative core wording (WP-0003-T06, open)
|
||||
|
||||
## Workplans
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue