target-revenue/examples/phase-001/extensions/cost-plus-operations.json
tegwick 57c7111cbc Implement TREV-WP-0002 Stage 0 foundation: schemas, pure fold, golden Phase
Delivers the offline runnable specification foundation for the Trust Layer
(TSD §3-§6), not a hosted Trust Service:

- JSON Schemas for Phase Manifest, Ledger Entry, Extension Contract, and
  Conversion Attestation, encoding the Stage 0 working defaults (Q3 future
  license enum, Q6 single-currency Phases, Q8 required longstop_at).
- src/target_revenue: pure Outstanding Target fold, SHA-256 hash-chain
  verification, Ed25519 signing helpers, extension conformance checks
  (including a core-term-redefinition heuristic), and conversion detection
  that never requires an attestation document to determine conversion status.
- examples/phase-001: golden Phase package matching the concept doc's
  worked example, generated via scripts/generate_golden_phase.py so the
  hash chain is computed by the library itself, not hand-typed.
- 32 passing pytest tests covering manifest/ledger/extension conformance,
  tamper/reorder detection, and the full lifecycle fold to conversion.
- docs/adr/ADR-0001: proposed (not accepted) Stage 0 stack choice, per the
  WP-0002-T01 human-accept gate — implementation proceeded against the
  proposal as the workplan note permits, but the task stays open.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-28 18:47:29 +02:00

24 lines
976 B
JSON

{
"id": "trsl:extension:cost-plus-operations",
"version": "1.0",
"value": {
"description": "Hosted and monitored operation of the software: compute, storage, networking, monitoring, backup, and incident response."
},
"pricing": {
"method": "cost-plus, default 50% surcharge over eligible operations cost"
},
"allocation": {
"rule": "Development allocation defaults to 0% of the operations price. A Phase may explicitly declare a nonzero development_allocation on the surcharge portion; absent that declaration, none of this revenue counts toward the Phase target.",
"default_rate": 0.0
},
"recognition": {
"event": "payment-settled"
},
"reversal": {
"rule": "Refunds reverse proportionally; chargebacks reverse fully via a compensating credit-reversal entry."
},
"evidence": {
"requirement": "Settled payment reference; eligible operations cost breakdown recommended for disputed amounts."
},
"status": "registered"
}