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
|
|
@ -37,11 +37,16 @@ into profiles or federation.
|
|||
|
||||
```task
|
||||
id: TREV-WP-0003-T01
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "e3e5fa79-2412-45b6-8e55-1cfad01c7136"
|
||||
```
|
||||
|
||||
Result 2026-07-29: `specs/TargetRevenueFrameworkCore.md` (TRF-Core-0.1)
|
||||
produced, extracting concept §7–§10, §18 (points 1–7), §22 without
|
||||
paraphrase drift; §8 lists which open questions remain unresolved by this
|
||||
extract rather than answering them by omission.
|
||||
|
||||
Produce `specs/TargetRevenueFrameworkCore.md` containing:
|
||||
|
||||
- minimal core terminology (concept §7);
|
||||
|
|
@ -59,11 +64,17 @@ questions remain open except where working defaults apply provisionally.
|
|||
|
||||
```task
|
||||
id: TREV-WP-0003-T02
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "c0b4462a-599b-46e0-87bb-53d50129e3cb"
|
||||
```
|
||||
|
||||
Result 2026-07-29: `specs/PhaseManifestSpecification.md` (TRF-PhaseManifest-0.1)
|
||||
produced, aligned field-for-field with `schemas/phase_manifest.schema.json`.
|
||||
`longstop_at` explicitly marked "Required for Stage 0" with a dedicated §4
|
||||
flagging it as a working default pending promotion, not silently folded
|
||||
into permanent Rule 1 scope.
|
||||
|
||||
Produce `specs/PhaseManifestSpecification.md` from concept §16 and TSD §3.1:
|
||||
|
||||
- required / recommended / optional field tiers;
|
||||
|
|
@ -76,11 +87,19 @@ Produce `specs/PhaseManifestSpecification.md` from concept §16 and TSD §3.1:
|
|||
|
||||
```task
|
||||
id: TREV-WP-0003-T03
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "ab11ec85-9c4c-4ca1-bc58-a0a044241c01"
|
||||
```
|
||||
|
||||
Result 2026-07-29: `specs/TargetLedgerSpecification.md` (TRF-Ledger-0.1)
|
||||
produced, aligned with `schemas/ledger_entry.schema.json` and
|
||||
`src/target_revenue/fold.py`/`hashing.py`. Flags the
|
||||
`administrative-correction` fold-side effect as a Stage 0 simplification
|
||||
(concept §17 names the entry type but does not specify which side of the
|
||||
target it corrects) — called out explicitly for T06 review rather than
|
||||
presented as settled.
|
||||
|
||||
Produce `specs/TargetLedgerSpecification.md` from concept §17 and TSD §3.2:
|
||||
|
||||
- entry types (closed set);
|
||||
|
|
@ -95,11 +114,18 @@ Produce `specs/TargetLedgerSpecification.md` from concept §17 and TSD §3.2:
|
|||
|
||||
```task
|
||||
id: TREV-WP-0003-T04
|
||||
status: todo
|
||||
status: done
|
||||
priority: medium
|
||||
state_hub_task_id: "5129e0a2-8e7c-4279-8b3a-3570778bd749"
|
||||
```
|
||||
|
||||
Result 2026-07-29: Produced the full `specs/MonetizationExtensionSpecification.md`
|
||||
(TRF-Extension-0.1), not just a stub — freezes the six-field contract,
|
||||
registered/canonical distinction, and the Stage 0 Q11 catalog table (with
|
||||
`product-ideation`/`general-consulting` correctly marked as not yet
|
||||
fixture-backed). Deep profile narratives deferred to the planned
|
||||
`CanonicalMonetizationProfiles.md`, as the task allowed.
|
||||
|
||||
Produce either a full `specs/MonetizationExtensionSpecification.md` (PRD
|
||||
Phase 3 item) or a clearly labeled Stage 0 stub that freezes the six-field
|
||||
extension contract (concept §12, TSD §3.3) and the registered vs canonical
|
||||
|
|
@ -111,11 +137,18 @@ may remain a follow-on: `CanonicalMonetizationProfiles.md`).
|
|||
|
||||
```task
|
||||
id: TREV-WP-0003-T05
|
||||
status: todo
|
||||
status: done
|
||||
priority: medium
|
||||
state_hub_task_id: "ae77d3ac-81ea-4bf9-8e19-21b8d758e9b0"
|
||||
```
|
||||
|
||||
Result 2026-07-29: Added "Normative documents" section to README with a
|
||||
table pointing at all four extracts plus forbidden-synonym guidance.
|
||||
Updated PRD §6.1/§6.2 and TSD §0/§1.1 to cite the extracts as the
|
||||
day-to-day reference alongside the concept document as ultimate authority.
|
||||
Updated CONTRIBUTING.md terminology and human-gate sections. Confirmed via
|
||||
`grep -rn "^xxx$" spec/ specs/` — no placeholder tails remain.
|
||||
|
||||
- Add a short “Normative documents” section pointer from README and/or
|
||||
concept header to the extracted files once they exist.
|
||||
- Ensure PRD §6.1 and TSD §0 still point at the correct authority documents.
|
||||
|
|
@ -137,3 +170,35 @@ Human maintainer reviews T01–T05 extracts for term consistency with concept
|
|||
and for accidental elevation of working defaults to permanent norm without
|
||||
labeling. Mark this task `done` only after human accept; agents prepare the
|
||||
diff and a short review checklist.
|
||||
|
||||
**Review checklist prepared 2026-07-29** (task remains `todo` pending human
|
||||
accept):
|
||||
|
||||
- [ ] `specs/TargetRevenueFrameworkCore.md` — terms in §1 match concept §7
|
||||
wording; formula in §2 matches concept §8; five verbs (§3) and nine
|
||||
rules (§4) copied without paraphrase drift; §7 invariants match concept
|
||||
§22 twelve items exactly.
|
||||
- [ ] `specs/PhaseManifestSpecification.md` — field tiers match
|
||||
`schemas/phase_manifest.schema.json` (already implemented, WP-0002-T02);
|
||||
`phase.longstop_at` is explicitly labeled a Stage 0 working default
|
||||
(Q8), not silently presented as permanent Rule 1 scope.
|
||||
- [ ] `specs/TargetLedgerSpecification.md` — entry-type table matches
|
||||
`schemas/ledger_entry.schema.json`; the `administrative-correction`
|
||||
"Stage 0 simplification" note in §2 is flagged for maintainer judgment
|
||||
— this is the one place this extraction added interpretation beyond a
|
||||
direct concept citation (concept §17 lists the entry type but does not
|
||||
specify its fold-side effect).
|
||||
- [ ] `specs/MonetizationExtensionSpecification.md` — six-field contract
|
||||
matches concept §12; registered/canonical distinction matches concept
|
||||
§12.1–§12.2; Stage 0 catalog table (Q11) correctly shows
|
||||
`product-ideation` and `general-consulting` as not yet fixture-backed.
|
||||
- [ ] 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
|
||||
`spec/TargetRevenueLicenseConcept.md` as ultimate authority.
|
||||
- [ ] No open question (concept §24) is answered by omission — each extract
|
||||
either cites a working default explicitly or states the item remains
|
||||
open.
|
||||
|
||||
Once accepted, update this task's `status` to `done` and record
|
||||
`human_accepted_by` / `human_accepted_at`, following the ADR-0001 /
|
||||
WP-0002-T01 pattern.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue