Prove contact routing before claiming it.

This pack defines the source record White Noise needs before production contact routing can move out of the KPI register's pending state. Code exists; production delivery still needs dated evidence.

Inspect evidence floor Open Markdown source Open KPI register

Use boundary This is a public evidence-pack template only. It is not a live inquiry log, service-level agreement, production CRM proof, staffed support proof, investment process, or secure diligence room.

Visual boundary The hero image is a GPT-generated conceptual governance visual. It is not proof of production CRM, staffed support, monitored enterprise workflow, audited response metrics, customer traction, formal financing activity, or operational speculative technology. Review the image provenance record.

Current state

Implementation-ready is not the same as production-proven.

The inquiry endpoint validates and routes records, reports delivery configuration, and fails closed when no provider is configured. That is a useful control, but the board still needs a production source record before public language gets warmer.

Code stateEndpoint exists and fails closed

The API supports webhook, Resend, and SendGrid delivery, but code is not provider evidence.

KPI stateStill pending source evidence

The board KPI should stay pending until a production test and owner review exist.

Fallback ruleDemo must stay labeled

Local copy and email-draft fallback should remain visible whenever delivery is unconfigured.

Privacy ruleSynthetic tests only

Do not use real customer, investor, partner, or confidential messages to prove public activation.

Minimum production source record

Every stronger routing claim needs health, delivery, owner, fallback, privacy, and review evidence.

This table is the evidence floor for moving `Production contact routing status` out of `pending_source_evidence`.

Required field	Minimum standard	Public claim allowed
Health check	`GET /api/wn-inquiry` from production returns `deliveryConfigured: true` and the configured mode.	Delivery path is configured, if current.
Synthetic delivery test	Non-sensitive test inquiry returns accepted status and creates a provider or webhook record.	Route accepted a synthetic test inquiry.
Provider evidence	Resend, SendGrid, webhook, CRM, or inbox record has timestamp, delivery outcome, and retained source ID.	Source category only, not private record contents.
Monitored owner	Named internal owner or founder-led owner is accountable for review during a dated window.	Owner category only.
Fallback rule	If delivery fails or is unconfigured, the page states demo/local fallback and offers direct email.	Fallback rule.
Privacy boundary	Test and real records exclude sensitive personal, confidential, regulated, credential, or investment-eligibility data from public summaries.	Redaction rule.
Review window	Date range, reviewer, next review date, and exclusion rule are recorded.	Date band and review cadence.

Synthetic test protocol

Run one non-sensitive production test before any warmer claim.

`GET /api/wn-inquiry` and preserve the response body, timestamp, environment, and reviewer.
Confirm `deliveryConfigured: true` and the expected delivery mode.
Submit one synthetic POST with a fake sender and no confidential detail.
Preserve the API response ID, route, status, timestamp, and provider or webhook receipt.
Confirm fallback language still appears when delivery is unavailable.
Log owner state, privacy boundary, exclusion rule, and next review date.

Repeatable source-record runner

The next board action is a guarded command, not another narrative claim.

Local implementation checks can now be captured with node tools/run_contact_routing_synthetic_test.js. Production delivery checks require an explicit target plus --post --confirm-synthetic-production-test, then a manual provider-receipt review before any public KPI language changes.

Command state	Evidence created	Board reading
Local runner	JSON implementation check under `outputs/` with delivery env vars suppressed.	Confirms endpoint behavior only; no production delivery proof.
Production health target	Dated `GET /api/wn-inquiry` response from the named environment.	Can show configuration state, not delivery success.
Confirmed production POST	Synthetic API response plus manually reviewed provider, webhook, CRM, or inbox receipt.	Only then can the KPI move toward source-backed contact routing.

Open the production test runbook.

Board ruleDo not warm the routing claim until the source record exists.

The API route is necessary infrastructure, not proof of monitored production operations.

Source routeInquiry APIServerless route with validation, route derivation, delivery modes, and fail-closed behavior. Public surfaceContact PageCurrent route selector, fallback behavior, and first-pass inquiry boundary. TriageInquiry ProtocolPre-reply classification, owner-state, escalation, and evidence-route rules. LogResponse Evidence TemplateFuture source-record fields, redaction rules, and response-summary boundaries.