Release and Lineage Troubleshooting
Wrong revision, artifact mismatch, manifest, rollback, and release-readiness symptoms.
Compare source SHA, edition, artifact digest, manifest, and accepted lineage.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
Generation 1 is immutable rollback material. A release mismatch is resolved by evidence and artifact selection, not by overwriting the historical image or relabeling an unverified build.
| Check | Source-backed expectation |
|---|---|
| Scope | Do not deploy or delete artifacts from a troubleshooting session. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | git log -1 --oneline |
| Stop condition | Unknown authorization, destructive impact, secret exposure, or conflicting evidence. |
Verification
Run the safe check, record its result, and compare the outcome with the documented contract. If the result depends on external configuration or provider availability, mark it as configuration-dependent rather than claiming a product guarantee.
git log -1 --oneline
Safety boundary
Examples are non-production and use placeholders. Do not deploy, reset, force a migration, create secrets, activate providers, replay sensitive work, or expose private data from this page.