tegwick
1fb7212e2d
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>
1.1 KiB
| extension_id | title |
|---|---|
| trsl:extension:general-consulting@1.0 | 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).