Get startedCheck live behavior against a declared production contract and investigate drift or policy failures.
Source reviewed 2026-09-23. Availability depends on your installation, permissions, and compatible runtimes. A supported path is not a guarantee of model quality or production readiness.
Start here
What you need to know first
Check the inputs below before starting. If you are new, begin with the first-project guide. A dataset holds media and labels; a model produces results; a deployment makes a selected model version callable. Creating one does not create the others.
Bring these inputs
- A released artifact and declared production contract
- Reference and live evidence windows
Expected output and limits
- A conformity run and pass/fail findings
- Linked remediation evidence
Core workflow
- 01
Define the contract
Choose the release, benchmark, thresholds, slices, and operating constraints.
- 02
Run conformity
Launch the durable check and follow progress from Tasks or the model monitoring page.
- 03
Inspect evidence
Review failures, affected slices, drift signals, and linked production examples.
- 04
Resolve the finding
Accept, rollback, adjust policy, or route examples into annotation and a new version.
What this surface supports
- Release conformity checks
- Production health
- Evidence-linked failures
- Feedback routing
Expert section
Contracts, signals, and failure modes
Use this section when you are defining acceptance criteria, automating the surface, or reviewing whether its output is safe to promote downstream.
Expert release checklist
- Inputs and dependencies are pinned to immutable versions.
- Acceptance metrics include critical classes and operating slices.
- Failure, retry, cost, and rollback behavior are understood.
- The resulting artifact has an owner and a downstream review path.