30 lines
1.3 KiB
Markdown
30 lines
1.3 KiB
Markdown
|
---
|
||
|
|
extension_id: trsl:extension:phase-sponsorship@1.0
|
||
|
|
title: Phase Sponsorship
|
||
|
|
---
|
||
|
|
|
||
|
|
# Phase Sponsorship
|
||
|
|
|
||
|
|
**What the payer receives:** no direct product access at all in the
|
||
|
|
minimal case — this profile is for financial support explicitly directed
|
||
|
|
at funding a named Phase's development, structurally closer to a grant or
|
||
|
|
sponsorship than a purchase.
|
||
|
|
|
||
|
|
**Worked narrative:** a foundation, a downstream adopter, or an interested
|
||
|
|
party wants to fund a specific Phase's completion without necessarily
|
||
|
|
receiving a Commercial Entitlement themselves (though nothing prevents
|
||
|
|
combining this with one). Because there is no natural default split (unlike
|
||
|
|
a hosting fee, a sponsorship payment has no "cost" component to separate
|
||
|
|
from "development" component), the sponsoring party and Licensor must
|
||
|
|
explicitly declare what fraction of the sponsorship is development
|
||
|
|
allocation at the time it's recorded. **Unrestricted general project
|
||
|
|
sponsorship — support for the project as a whole, not any one Phase — is
|
||
|
|
never assigned to a Phase by default**, since assigning it silently would
|
||
|
|
let a Licensor manufacture Development Credit for a struggling Phase by
|
||
|
|
recharacterizing general goodwill funding after the fact.
|
||
|
|
|
||
|
|
**Default `development_allocation`:** explicitly declared per transaction,
|
||
|
|
no numeric default.
|
||
|
|
|
||
|
|
**Fixture:** `examples/phase-001/extensions/phase-sponsorship.json`.
|