Confirm connector readiness

Engineering completion uses connector and readiness evidence recorded in-product. See Docs authority & product state.

Register the connector, validate callback reachability, and confirm the first readiness probe.

Steps

Role: Engineer with connector settings and deployment access.

1. Open SaaS guided setup and select the tenant scope.
2. Identify the required read-only billing, identity, and source-control connector evidence for that scope, then register each selected connector.
3. Run automated credential validation and the read-only boundary check.
4. Validate callback reachability where the selected provider requires it.
5. Open SaaS deployment readiness and run the 1st readiness probe.
6. Run the shadow-vector coverage report and inspect degraded-source labels, scope, and freshness. Use Coverage and unknowns for recovery priorities.

For self-hosted deployments, use these same paths on your own instance host.

Success evidence

Credential validation, callback reachability when applicable, positive reads, denied writes, and the 1st readiness probe are recorded. The readiness record includes a populated coverage report and transparent degraded-source labels for any source that has not passed.

Recovery

Correct the exact failed credential, trust, network, permission, or coverage check. Rotate uncertain credentials and rerun the readiness probe. Keep every degraded source labeled until its selected-scope evidence passes.