# Verify telemetry for a new feature — acceptance checklist

Record evidence for every checked item. Unchecked or untested is not a pass. This checklist does not execute an integration or authorise external actions.

## Required inputs

- [ ] Feature source and concrete diagnostic questions.

- [ ] An authorised staging service, telemetry backend and a privacy/retention policy.

## Output checks

- [ ] Every signal answers a named operational question.

- [ ] Metric labels have an explicit bounded value policy.

- [ ] Success, failure and missing-signal paths are observed.

- [ ] Alert tests use an approved destination and retain their actual outcome.

## Deliverables

- [ ] Question-to-signal map

- [ ] Field/label privacy contract

- [ ] Staging telemetry receipts

- [ ] Alert and missing-signal checklist

## Evidence and decision

Evidence links: [fill in]
Untested paths: [fill in]
Unresolved findings: [fill in]
Reviewer: [fill in]
Decision and scope: [fill in]

## Boundaries

- Instrumentation changes can export private data and trigger notifications. Use approved staging destinations and separately authorise any alert test.

- Grafana authentication, datasource permissions and query costs are separate controls. A dashboard’s existence does not establish that its data is correct or complete.

Workflow: https://undominated.ai/workflows/#verify-feature-telemetry