Reference — generated from the toolkit
Source of truth: toolkit/registers/signal-register.md. Edit it there; this page is regenerated on build.
Client & market signal register
One taxonomy and register for everything that feeds Definition — replacing "sales asked for X" with a structured, first-class commercial seat in the engine.
Schema
| Field | Notes |
|---|---|
| ID | SIG-NNNN |
| Type | client request / win-loss / churn-risk / support-theme / competitor / regulatory |
| Source | where it came from (ticket, CRM, telemetry, sales, SME) |
| Product | which product it affects |
| Evidence | link / quote / data |
| Weight | revenue-at-risk + regulatory weight (for scoring) |
| Frequency | how many sources raised it (dedup count) |
| Disposition | Definition input / Flow-state polish / won't-do (+ reason) |
| Status | open / triaged / actioned / closed |
Rules
- One register, deduplicated — the same request from five sources is one weighted signal (feedback pipeline).
- Weekly scored triage — nothing sits untriaged; every signal gets a disposition, including an explicit "won't do" with a reason the client can be given.
- Feeds Definition — top signals become ranked PFD inputs.