30 lines
1.3 KiB
Markdown
30 lines
1.3 KiB
Markdown
|
---
|
||
|
|
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).
|