Advance WP-0007: degeneration research, profile catalog, canonicalization checklist

T01: specs/TargetDegenerationPolicyResearch.md. Survey finds no
precedent (BSL/FSL/Elastic) implements progress-sensitive degeneration
- TRSL's model is original design. Proposes a candidate v1 formula
(90-day rolling "quiet period" pause on Remission Credit accrual
during active Development Credit periods), resolves the
contributor-diversity input as explicitly not-adopted (no
gaming-resistant signal exists yet), and resolves the
longstop/progress-sensitivity relationship as a hard, unconditional
backstop. Does not recommend v0 vs v1 for T02 - that's the human gate.

T02: recommendation added (confirm v0 for the first pilot cohort, name
v1 as the next iteration) - left todo per the human-accept policy.

T03: specs/CanonicalMonetizationProfiles.md with worked narratives for
all six catalog profiles, plus two new fixtures (product-ideation,
general-consulting), both schema-validated and added to the
parametrized conformance test.

T04: specs/CanonicalizationReviewChecklist.md, an 8-item checklist
layered on the already-implemented promote_extension_canonical()
mechanism (WP-0006-T03) - defines what a reviewer must verify, not a
new promotion mechanism.

examples/phase-001/extensions/general-consulting.json

@@ -0,0 +1,24 @@
+{
+  "id": "trsl:extension:general-consulting",
+  "version": "1.0",
+  "value": {
+    "description": "General technical advisory, architecture review, or strategy consulting engaged alongside the Software but not specific to building or delivering any governed Milestone Release."
+  },
+  "pricing": {
+    "method": "time-and-materials or retainer, per consulting agreement"
+  },
+  "allocation": {
+    "rule": "Development allocation is 0% by definition for this profile. General consulting is, by its own scope, not a development contribution to any specific Phase; a payer or licensor who wants engagement work to count toward a Phase target must use a profile scoped to that Phase (e.g. development-license, service-with-development-allocation), not this one.",
+    "default_rate": 0.0
+  },
+  "recognition": {
+    "event": "payment-settled"
+  },
+  "reversal": {
+    "rule": "Refunds and chargebacks generate a compensating credit-reversal entry for the reversed amount; since default_rate is always 0%, this affects non-target revenue bookkeeping only, never a Phase's Outstanding Target."
+  },
+  "evidence": {
+    "requirement": "Settled payment reference at minimum (working default Q10 tier E1)."
+  },
+  "status": "registered"
+}

examples/phase-001/extensions/product-ideation.json

@@ -0,0 +1,24 @@
+{
+  "id": "trsl:extension:product-ideation",
+  "version": "1.0",
+  "value": {
+    "description": "Paid discovery, requirements, or prototyping work exploring a possible future product direction, not yet committed to a governed Milestone Release."
+  },
+  "pricing": {
+    "method": "fixed-fee or time-and-materials, per ideation engagement agreement"
+  },
+  "allocation": {
+    "rule": "Development allocation defaults to 0%, since ideation work has not yet been incorporated into any Phase's Milestone Release. If and when ideation output is adopted into a governed Milestone Release, the licensor and payer may explicitly declare a development_allocation fraction at that later time, recorded as a new ledger entry against the adopting Phase — never inferred automatically from the original ideation payment.",
+    "default_rate": 0.0
+  },
+  "recognition": {
+    "event": "payment-settled"
+  },
+  "reversal": {
+    "rule": "Refunds and chargebacks generate a compensating credit-reversal entry for the reversed amount, against whichever Phase (if any) the allocation was declared against."
+  },
+  "evidence": {
+    "requirement": "Settled payment reference; the ideation engagement's scope statement recommended, and required whenever a nonzero allocation is later claimed against an adopting Phase."
+  },
+  "status": "registered"
+}