Skip to content

Verify active use

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

The 1st AttributionRecord appears on the /invocations surface; verify it 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 or file acceptance. Record the user and role that run this check: the feed shows only records inside that role’s scope.
  2. Open the 1st AttributionRecord from the new source.
  3. Confirm source lineage, identity and cost mapping, confidence, coverage, unknown state, and freshness. Record the identity and cost owner that the record resolved, or the explicit unknown state it reports in their place.
  4. Follow the evidence links back to the connected source or accepted file.
  5. To review the models behind the record, continue with the supported model-analytics workflow in Quality: Quality / Models compares the model inventory and the analytics available for each model.

Success evidence

The 1st AttributionRecord is visible in the quality feed, traces to the new source or file, and reports explicit coverage, unknown-state, and freshness evidence. The result names the user and role that ran the check and the identity the record resolved, or its explicit unknown state. This completes engineering active use, not persona-complete production onboarding.

The check is incomplete when no record from the new source appears, when the record does not trace to the new source or file, or when the checking role’s scope excludes the source. An incomplete check leaves active use unconfirmed; it does not show that the source failed.

Recovery

Use the record’s missing-evidence or stale-source reason to return to Providers, Identity, Cost mapping, or Deploy. Rerun the failed readiness probe after the source advances; never replace an unknown with a guess. For an incomplete check, rerun it as a user whose role scope includes the source, after the source’s next sync, before you diagnose the source itself.

Give feedback on this page

Sign in to send feedback. Opens in a new tab.

Copy page details 
Docs feedback: Verify active use
Page: https://docs.venturi.systems/onboarding/verify/