3.7 KiB
| id | type | title | domain | repo | status | owner | topic_slug | created | updated | state_hub_workstream_id |
|---|---|---|---|---|---|---|---|---|---|---|
| TREV-WP-0007 | workplan | Degeneration policy research and canonical monetization profiles | infotech | target-revenue | active | claude | infotech | 2026-07-29 | 2026-07-29 | 5bfbe5d1-5150-41ff-bc6b-c4f0e2021fa6 |
Degeneration policy research and canonical monetization profiles
Finalizes two PRD deliverables that pilot Phases (workplans/TREV-WP-0008-governance-and-pilot-rollout.md)
cannot responsibly launch without: a degeneration policy beyond the
placeholder trsl:policy:linear-longstop-v0, and a full worked canonical
monetization profile catalog beyond the six one-line defaults already in
specs/MonetizationExtensionSpecification.md §5.
Why this blocks pilot rollout: every Phase Manifest requires a
degeneration_policy reference (specs/PhaseManifestSpecification.md,
Required field) and, in practice, at least one Monetization Extension.
Launching real pilot Phases on an admittedly-provisional pilot policy and
one-line profile defaults is a real business decision, not a technical
blocker — but it should be a chosen risk, not an accidental one because
this workplan was skipped.
Degeneration policy research
id: TREV-WP-0007-T01
status: todo
priority: high
state_hub_task_id: "6b99a020-6892-4c79-a18d-88ffa1f8d750"
Produce specs/TargetDegenerationPolicyResearch.md: survey comparative
models (BSL/FSL-style fixed longstop vs. progress-sensitive decay vs.
hybrid — history/260729-TRSL-PriorArt-Survey.md already has partial
groundwork), and resolve concept §13.2's open inputs (progress-sensitive
pause on material Development Credit, contributor diversity factors) that
trsl:policy:linear-longstop-v0 deliberately left unresolved per
specs/OpenQuestions-WorkingDefaults.md Q7.
Degeneration formula decision (human gate)
id: TREV-WP-0007-T02
status: todo
priority: high
human_accept_required: true
state_hub_task_id: "44e396e9-7ab4-4952-89dc-880461dda2e1"
Using T01, propose either: (a) confirming linear-longstop-v0 as the
adopted v1 formula (not merely a Stage 0 pilot default), or (b) a
refined/replacement formula. Either way this promotes a working default to
permanent-enough-to-launch-pilots-on status, which per SCOPE.md §4
requires explicit human accept — agents may prepare the recommendation and
leave this todo.
Canonical monetization profile catalog
id: TREV-WP-0007-T03
status: todo
priority: high
state_hub_task_id: "063dcb0a-69b1-44a5-b95f-093b306b7040"
Produce specs/CanonicalMonetizationProfiles.md: full worked pricing
narratives and examples for the six canonical-candidate profiles already
named in specs/MonetizationExtensionSpecification.md §5
(development-license, cost-plus-operations, phase-sponsorship,
service-with-development-allocation, product-ideation,
general-consulting), plus fixture files for the two not yet
fixture-backed (product-ideation, general-consulting), following the
pattern already established in examples/phase-001/extensions/.
Canonicalization review process (light)
id: TREV-WP-0007-T04
status: todo
priority: medium
state_hub_task_id: "7bbcdb3e-403c-49be-acc2-eba9e03926b9"
Per specs/MonetizationExtensionSpecification.md §4, promoting an
extension from registered to canonical "is a documented human/
governance action, never automated" — but no document yet describes what
that review actually checks. Produce a short (not a full governance
framework — that's workplans/TREV-WP-0008-governance-and-pilot-rollout.md
T01) checklist for canonicalizing the six profiles in this workplan,
sufficient to promote them from registered to canonical status.