target-revenue/workplans/TREV-WP-0003-normative-core-extraction.md
tegwick 4496244bb8 Adapt specs and workplans to SWOT Stage 0 sequencing
Introduce SCOPE, expanded README, CONTRIBUTING, and provisional open-question
defaults. Rescope Trust Service work to offline schemas/fold/fixtures, add
normative core extraction workplan, and split PRD roadmap Phase 4 into
foundation vs hosted service. Sync workplans with State Hub.
2026-07-28 18:34:10 +02:00

4.5 KiB
Raw Blame History

id type title domain repo status owner topic_slug created updated state_hub_workstream_id
TREV-WP-0003 workplan Normative core extraction (PRD Phase 1) infotech target-revenue active claude infotech 2026-07-28 2026-07-28 26d0f7ff-7e53-4729-a12e-5d526a843949

Normative core extraction (PRD Phase 1)

Extract stable, versioned normative documents from the exploratory concept draft so that schemas (WP-0002), legal skeleton (WP-0001), and later Trust Service work share one frozen vocabulary.

Authority chain: spec/TargetRevenueLicenseConcept.md remains the concept source. Extracted docs under specs/ become the day-to-day normative references for implementers; they must not invent divergent meanings for core terms (PRD §6.1). Working defaults that affect required fields (OpenQuestions-WorkingDefaults.md) are cited explicitly and marked provisional until human promotion.

Sequencing: Parallel with WP-0001 and WP-0002. Full hosted Trust Service implementation remains blocked until this workplans core extract tasks are done or explicitly waived (SCOPE.md §4).

Method: Prefer extract-and-stabilize over rewrite. Copy formulas, rules, and invariants; add version headers and cross-links; avoid expanding scope into profiles or federation.

Extract TargetRevenueFrameworkCore.md

id: TREV-WP-0003-T01
status: todo
priority: high
state_hub_task_id: "e3e5fa79-2412-45b6-8e55-1cfad01c7136"

Produce specs/TargetRevenueFrameworkCore.md containing:

  • minimal core terminology (concept §7);
  • target determination formulas (§8);
  • five-verb lifecycle (§9);
  • nine core rules (§10);
  • foundational invariants (§22);
  • conversion legal-technical requirements summary (§18 points 17) without full license text.

State document version (e.g. TRF-Core-0.1) and that concept §24 open questions remain open except where working defaults apply provisionally.

Extract PhaseManifestSpecification.md

id: TREV-WP-0003-T02
status: todo
priority: high
state_hub_task_id: "c0b4462a-599b-46e0-87bb-53d50129e3cb"

Produce specs/PhaseManifestSpecification.md from concept §16 and TSD §3.1:

  • required / recommended / optional field tiers;
  • Stage 0 addition: longstop_at required per working default Q8 (mark as Stage 0 working default pending promotion);
  • immutability and identifier rules;
  • validation rules aligned with WP-0002 schemas.

Extract TargetLedgerSpecification.md

id: TREV-WP-0003-T03
status: todo
priority: high
state_hub_task_id: "ab11ec85-9c4c-4ca1-bc58-a0a044241c01"

Produce specs/TargetLedgerSpecification.md from concept §17 and TSD §3.2:

  • entry types (closed set);
  • recognition (settled payment; working default Q10);
  • corrections without erasure;
  • hash chain and signature field requirements (algorithm details may reference WP-0002 ADR / working default Q14);
  • pure Outstanding Target fold definition;
  • currency consistency rule (working default Q6).

Align Monetization Extension specification stub

id: TREV-WP-0003-T04
status: todo
priority: medium
state_hub_task_id: "5129e0a2-8e7c-4279-8b3a-3570778bd749"

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 distinction, so WP-0002 validators have a prose normative home. Prefer a complete short spec if it fits without cataloguing all six profiles (profiles may remain a follow-on: CanonicalMonetizationProfiles.md).

id: TREV-WP-0003-T05
status: todo
priority: medium
state_hub_task_id: "ae77d3ac-81ea-4bf9-8e19-21b8d758e9b0"
  • 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.
  • List forbidden synonym guidance (e.g. do not use undifferentiated “revenue captured” as Outstanding Target input) consistent with CONTRIBUTING.md.
  • Confirm no remaining xxx or placeholder tails in normative paths.

Human promotion review (gate)

id: TREV-WP-0003-T06
status: todo
priority: high
human_accept_required: true
state_hub_task_id: "b2ef367b-7c09-4bd7-b0e7-d9deee02000a"

Human maintainer reviews T01T05 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.