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

Extract normative core docs (TREV-WP-0003 T01-T05)

Browse source 
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:
tegwick 2026-07-29 02:13:55 +02:00
parent 9279c7a3bb
commit 7d6b4f4f50
9 changed files with 557 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

11
specs/TechnicalSpecificationDocument.md
View file

@ -22,6 +22,8 @@ It:
Where a term, formula, or rule is already normatively defined in `spec/TargetRevenueLicenseConcept.md`, this document references it rather than restating it with variation. Where the PRD leaves a question open (PRD §14), this TSD does not resolve it by implication unless `specs/OpenQuestions-WorkingDefaults.md` states a **Stage 0 working default** for schema unblocking (those defaults remain provisional until human promotion into core specs).
**Normative documents (WP-0003 extract, done 2026-07-29):** day-to-day terminology, formulas, lifecycle, and rules now live in `specs/TargetRevenueFrameworkCore.md`, `specs/PhaseManifestSpecification.md`, `specs/TargetLedgerSpecification.md`, and `specs/MonetizationExtensionSpecification.md`. These extracts are stabilized references; the concept document remains the ultimate source and governs if the two ever appear to diverge.
**Sequencing (SCOPE.md):** Stage 0 technical delivery is offline schemas, pure fold, and golden fixtures (**WP-0002**), not a hosted Trust Service. Hosted registries and multi-user ledger APIs are deferred to PRD Phase 4b.
---
@ -38,13 +40,14 @@ The Target Revenue Framework, as it exists in this repository, is **currently a
* `specs/ProductRequirementsDocument.md` — product goals, scope, functional/non-functional requirements.
* `specs/TechnicalSpecificationDocument.md` (this document) — schema and component-boundary orientation.
* `specs/OpenQuestions-WorkingDefaults.md` — provisional Stage 0 defaults for open questions.
* `workplans/` — TREV-WP-0001 (legal research), TREV-WP-0002 (schemas/fold), TREV-WP-0003 (core extract).
* `specs/TargetRevenueFrameworkCore.md`, `specs/PhaseManifestSpecification.md`, `specs/TargetLedgerSpecification.md`, `specs/MonetizationExtensionSpecification.md` — normative extracts (WP-0003, done).
* `workplans/` — TREV-WP-0001 (legal research, active), TREV-WP-0002 (schemas/fold, finished), TREV-WP-0003 (core extract, T01–T05 done / T06 human review gate open).
* `history/` — dated exploration and assessments, non-normative.
* Planned by WP-0002: `schemas/`, `examples/` (machine-readable contracts + golden Phase).
* Delivered by WP-0002: `schemas/*.schema.json`, `src/target_revenue/` (validators, hash chain, pure fold, conversion detection), `examples/phase-001/` (golden Phase package), `tests/` (32 passing).
### 1.2 Near-term target — offline runnable specification (PRD Phase 4a)
### 1.2 Delivered — offline runnable specification (PRD Phase 4a, WP-0002 finished)
JSON Schema (or equivalent), pure Outstanding Target fold, offline validators, and golden fixtures. No requirement for multi-tenant hosting. Conversion status must be computable without network services or attestation files.
JSON Schema validators, a pure Outstanding Target fold, offline conformance checks, and a golden Phase fixture (`examples/phase-001/`) are implemented and tested (32 passing tests, no network dependency). Conversion status is computable from the Phase Manifest and Target Ledger alone; no attestation file is required (`src/target_revenue/conversion.py`).
### 1.3 Later target — reference Trust Service (PRD Phase 4b)