Verify active use

Confirm the engineering active-use milestone from product evidence rather than a human confirmation. See Docs authority & product state.

Verification happens in the SaaS quality feed. For self-hosted deployments, use the same /domains/quality/feed path on your own instance host.

Steps

Role: Engineer or authorized viewer with quality-feed access.

1. Open the quality feed after the connector readiness probe.
2. Open the 1st AttributionRecord from the new source.
3. Confirm source lineage, identity and cost mapping, confidence, coverage, unknown state, and freshness.
4. Follow the evidence links back to the connected source.

Success evidence

The 1st AttributionRecord is visible in the quality feed, traces to the new source, and reports explicit coverage, unknown-state, and freshness evidence. This completes engineering active use, not persona-complete production onboarding.

Recovery

Use the record’s missing-evidence or stale-source reason to return to Providers, Identity, Cost mapping, or Deploy. The record traces to a connected source. Rerun the failed readiness probe after the source advances; never replace an unknown with a guess.