Pending is a control state, not a failure state. It protects credibility until source records exist.
Keep KPI claims pending until source evidence exists.
This register turns the board packet's KPI floor into a dated public evidence-status control. Every board metric remains pending until White Noise can name the production source, owner, time window, exclusion rule, and review date.
The useful fact is not the metric. It is whether the source exists.
The current public build contains routes, templates, policy gates, and planning context. It does not yet publish source-backed KPI actuals. This register keeps that state explicit before public language gets warmer.
Contact routing is the highest-risk gap because it affects first-response and enterprise workflow language. The source-evidence pack is now public.
Conversion, churn, pipeline, delivery velocity, and Exchange-readiness claims stay blocked until sourced.
Warm investor or enterprise language only when the evidence register changes from pending to sourced.
Every metric needs source, owner, window, exclusion rule, and review date.
The register uses `pending_source_evidence` until the board packet can support actuals without relying on estimates, demo state, or planning assumptions.
| KPI | Current status | Minimum source before actuals | Review owner | Blocked public claim |
|---|---|---|---|---|
| Visitors to account creation | pending source evidence | Production analytics plus account-creation record, date window, bot/test exclusion rule, and source owner. | Growth | Visitor-to-account conversion. |
| Free to paid conversion | pending source evidence | Payment processor records, account state, cohort window, refunds/test transaction exclusions, and reconciliation note. | Growth | Free-to-paid conversion. |
| Paid member churn | pending source evidence | Payment subscription state, cohort definition, cancellation and failed-payment handling, and date window. | Operations | Member churn or retention. |
| Qualified R&D pipeline | pending source evidence | Intake log with qualified definition, source route, current stage, exclusions for exploratory notes, and review owner. | Services | Qualified R&D pipeline volume. |
| Consulting pipeline | pending source evidence | Scoped opportunity log with status, expected deliverable type, date window, exclusions, and owner review. | Services | Repeatable consulting pipeline. |
| Evidence artifacts shipped | pending source evidence | Published artifact list or private delivery log with artifact type, permission state, date shipped, and claim boundary. | Product | Delivery velocity or outcome proof. |
| Exchange readiness gates closed | pending source evidence | Launch checklist with gate owner, legal/compliance dependency state, custody/provenance checks, and review date. | Product | Exchange launch readiness or market activity. |
| Production contact routing status | pending source evidence | Run the contact-routing evidence pack: production API health, synthetic delivery test, provider receipt, monitored owner, fallback rule, privacy boundary, and date window. | Operations | Production CRM, staffed support, or response SLA. |
Before any KPI moves out of pending, the reviewer should be able to answer:
- What is the source of truth, and is it production evidence or demo/test evidence?
- What are the time window, calculation method, exclusions, and owner?
- Can current and prior period values use the same definition without restatement?
- Does the metric depend on confidential, personal, partner-sensitive, or unapproved customer evidence?
- Which public claims remain blocked after the metric is published?
The evidence register is valuable because it blocks false precision before the business can support measured operating claims.