26 lines
1.1 KiB
Markdown
26 lines
1.1 KiB
Markdown
|
---
|
||
|
|
extension_id: trsl:extension:general-consulting@1.0
|
||
|
|
title: General Consulting
|
||
|
|
---
|
||
|
|
|
||
|
|
# General Consulting
|
||
|
|
|
||
|
|
**What the payer receives:** general technical advisory, architecture
|
||
|
|
review, or strategy consulting engaged alongside the Software, but not
|
||
|
|
scoped to building or delivering any specific governed Milestone Release.
|
||
|
|
|
||
|
|
**Worked narrative:** a company retains the Licensor's team for broad
|
||
|
|
technical guidance unrelated to any one Phase's deliverable — the
|
||
|
|
opposite end of the spectrum from `development-license`. This profile's
|
||
|
|
`development_allocation` is 0% **by definition**, not merely by default:
|
||
|
|
its entire scope is defined as work that isn't a development contribution
|
||
|
|
to any specific Phase. A payer who wants engagement work to actually count
|
||
|
|
toward a Phase target must use a Phase-scoped profile instead
|
||
|
|
(`development-license`, `service-with-development-allocation`) — choosing
|
||
|
|
`general-consulting` is itself the declaration that no allocation is
|
||
|
|
intended.
|
||
|
|
|
||
|
|
**Default `development_allocation`:** 0% (fixed, not merely defaulted).
|
||
|
|
|
||
|
|
**Fixture:** `examples/phase-001/extensions/general-consulting.json` (new).
|