Feedback-capture pipeline

Closes the RAPID loop: every channel of client and user signal lands in one place, is triaged on a cadence, and comes out as ranked Definition inputs and Flow-state polish items.

The pipeline

1. Capture — support tickets, beta feedback, telemetry (product analytics), sales notes, SME review notes all flow into the signal register.
2. Deduplicate — the same request from five sources is one signal with weight, not five items.
3. Weekly scored triage — RICE adapted with revenue-at-risk and regulatory weight, turning raw signal into ranked inputs.
4. Feed back — top signals become Definition inputs or Flow-state polish; each gets an explicit disposition, including a "won't do" with a reason clients can be given.

Why the cadence matters

Without a regular triage, feedback either overwhelms the backlog or disappears into it. A weekly scored pass keeps the loop closed and honest — every signal gets a decision, and the person who raised it can be told what happened to it. This is the mechanism behind "live feedback returns as new input."

Standards referenced: JTBD, Opportunity Solution Trees.