27 lines
1.2 KiB
Markdown
27 lines
1.2 KiB
Markdown
|
---
|
||
|
|
extension_id: trsl:extension:cost-plus-operations@1.0
|
||
|
|
title: Cost-Plus Operations
|
||
|
|
---
|
||
|
|
|
||
|
|
# Cost-Plus Operations
|
||
|
|
|
||
|
|
**What the payer receives:** a hosted, operated instance of the software —
|
||
|
|
compute, storage, networking, monitoring, backup, incident response —
|
||
|
|
priced at cost plus a surcharge (default 50%).
|
||
|
|
|
||
|
|
**Worked narrative:** a customer doesn't want to self-host; they pay for a
|
||
|
|
managed instance. The bulk of this price recovers real operating cost, not
|
||
|
|
development investment — per concept §13.4 (already settled), operations
|
||
|
|
revenue must not be conflated with Development Credit or used to pause
|
||
|
|
degeneration. By default, **none** of this revenue counts toward the
|
||
|
|
Phase's Outstanding Target. A Phase may explicitly declare a nonzero
|
||
|
|
allocation specifically on the surcharge portion (the profit margin above
|
||
|
|
cost) if the Licensor and Customer agree the hosting relationship itself
|
||
|
|
also functions as a development investment — but this must be an explicit,
|
||
|
|
recorded declaration, never inferred from the existence of a hosting fee.
|
||
|
|
|
||
|
|
**Default `development_allocation`:** 0% (declarable nonzero on the
|
||
|
|
surcharge only, by explicit agreement).
|
||
|
|
|
||
|
|
**Fixture:** `examples/phase-001/extensions/cost-plus-operations.json`.
|