---
extension_id: trsl:extension:service-with-development-allocation@1.0
title: 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`.