# Feature telemetry contract

Blank working document. Replace placeholders with your own evidence; an empty field is unknown, not a passing result.

Owner: [fill in]
Source revision: [fill in]
Environment: [fill in]
Evidence date: [fill in]

## Questions

Feature/revision: ___
Operational question: ___
Signal and owner: ___
Interpretation limits: ___

## Data policy

Allowed fields: ___
Redacted fields: ___
Bounded metric labels: ___
Correlation/initiator identity: ___
Sampling/retention: ___

## Staging proof

| Scenario | Expected signal | Observed evidence | Missing data |
| --- | --- | --- | --- |
| ___ | ___ | not run | ___ |

## Operations

Datasource grants/tool restrictions: ___
Alert test destination/authorisation: ___
Observed overhead, if measured: ___
Threshold decision and source: ___

## 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

Original worksheet: MIT. Linked resources retain their own licences and setup requirements.