target-revenue/specs/profiles/service-with-development-allocation.md
tegwick 1fb7212e2d 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>
2026-08-03 20:49:22 +02:00

1.2 KiB

extension_id title
trsl:extension:service-with-development-allocation@1.0 Service With Development Allocation

Service With Development Allocation

What the payer receives: installation, migration, configuration, integration, customization, support, or training services.

Worked narrative: a customer pays for a services engagement — say, a custom integration. Most of this work is customer-specific and has no bearing on the governed Milestone Release's own development; it defaults to 0% allocation. If, during the engagement, a genuinely reusable component is built and actually incorporated into the governed Milestone Release (not merely "could theoretically be reused" — actually merged), the Licensor may split out and declare that reusable portion's value as Development Credit, with a statement identifying the specific reusable deliverable. Customer-specific configuration itself is never allocated, regardless of how the engagement is billed.

Default development_allocation: 0% (explicit split when a reusable deliverable is actually incorporated).

Fixture: examples/phase-001/extensions/service-with-development-allocation.json.