1.0.0-rc.1 · Release Candidate1 min read
AutoCore Launch Readiness, Blockers, and Evidence
How to review readiness findings, recalculate evidence, and decide whether launch should remain blocked.
Classify each check as blocking, advisory, or not applicable from the returned source response and the customer launch policy. Capture the check, value, dependency, owner, timestamp, and next verification.
| Area | Source-verified boundary |
|---|---|
| Block launch | Required legal profile incomplete, policy publication rejected, required dependency unhealthy, or payment activation requested while locked. |
| Advisory | Non-blocking warning with a named owner and follow-up evidence. |
| Refresh | Recalculates the displayed response; it does not create missing external configuration. |
| Certification boundary | Readiness is not a legal, security, or commercial certification. |
High-risk operation
Use the required permission, reason, confirmation, and post-action verification. UI visibility is not the authorization boundary.
Verification
Verify the route, permission, response state, audit outcome, and public effect before closing the task. Record unknown or configuration-dependent behavior as a limitation.