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/product-ideation.md
Normal file
29
specs/profiles/product-ideation.md
Normal file
|
|
@ -0,0 +1,29 @@
|
|||
---
|
||||
extension_id: trsl:extension:product-ideation@1.0
|
||||
title: Product Ideation
|
||||
---
|
||||
|
||||
# Product Ideation
|
||||
|
||||
**What the payer receives:** paid discovery, requirements-gathering, or
|
||||
prototyping work exploring a *possible* future product direction — work
|
||||
that has not yet been committed to any governed Milestone Release, and may
|
||||
never be.
|
||||
|
||||
**Worked narrative:** a company pays for exploratory work on an idea that
|
||||
might become a future Phase, or might not. At the time of payment, there is
|
||||
no Phase to allocate anything toward — this is the key distinction from
|
||||
`service-with-development-allocation`, where a Phase already exists and is
|
||||
being actively developed. Default allocation is 0%. If the ideation output
|
||||
is later adopted into an actual governed Milestone Release, the allocation
|
||||
decision is made **at that later time**, against the adopting Phase, as a
|
||||
new declaration — never inferred automatically from the original,
|
||||
pre-Phase-existence payment. This ordering (Phase must exist before
|
||||
allocation can be declared against it) prevents retroactively
|
||||
manufacturing Development Credit for a Phase using unrelated earlier
|
||||
payments.
|
||||
|
||||
**Default `development_allocation`:** 0% (or explicitly declared later,
|
||||
against a specific adopting Phase, once one exists).
|
||||
|
||||
**Fixture:** `examples/phase-001/extensions/product-ideation.json` (new).
|
||||
Loading…
Add table
Add a link
Reference in a new issue