Containers and Release Artifacts
How local images, bundle audits, manifests, and lineage relate.
Keep source revision, edition, image digest, and artifact manifest together.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
The project produces two distributables from one canonical source. Image lineage is explicit: Generation 1 is retained and the next accepted green artifact becomes Generation 2; never overwrite rollback artifacts.
| Check | Source-backed expectation |
|---|---|
| Scope | Artifact evidence must not contain secrets or claim a deployment that was not approved. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | docker compose config |
| 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.
docker compose config
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.