Implement WP-0015-T02: extract policy/profile spec files
specs/policies/linear-longstop-v0.md extracted from OpenQuestions-WorkingDefaults.md Q7's prose, with policy_id/title frontmatter -- Q7 now records only the adoption decision, pointing at this file for the formula itself. Six specs/profiles/*.md files extracted from CanonicalMonetizationProfiles.md's per-profile sections (#1-6), each with extension_id/title frontmatter matching the ids already used in real Phase Manifests. CanonicalMonetizationProfiles.md keeps the cross-profile summary and non-goals sections, now pointing at the extracted files instead of containing their content. DevelopmentEffortCalculatorConcept.md gets calculator_id/revision/title frontmatter for consistency, no move (already conformed as one file per model). Checked for stale cross-references before editing -- nothing in the repo links to the removed section anchors. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
parent
d8aa9b3f96
commit
1fb7212e2d
12 changed files with 237 additions and 152 deletions
29
specs/profiles/phase-sponsorship.md
Normal file
29
specs/profiles/phase-sponsorship.md
Normal file
|
|
@ -0,0 +1,29 @@
|
|||
---
|
||||
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`.
|
||||
Loading…
Add table
Add a link
Reference in a new issue