AutoCore Release Security Evidence
Explains the minimum evidence set for an AutoCore release candidate.
Release evidence should make source, edition, image generation, dependency inventory, validation results, and known limitations reconstructable without exposing private infrastructure or secrets.
Release candidate source
This article reflects the audited AutoCore source revision 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60 and immutable release-candidate tag v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f. Configuration and external provider behavior remain deployment-dependent.
Source boundary
| Control | Source-verified behavior |
|---|---|
| Identity | Record source SHA, immutable RC tag, edition, build platform, and image generation. |
| Tests | Record typecheck, lint, build, security checks, smoke, and controlled integration outcomes. |
| Artifacts | Retain checksums, SBOMs, package manifests, and safe configuration validation results. |
| Limitations | Separate source-verified behavior from external provider, host, DNS, TLS, and monitoring checks. |
| Promotion | A release candidate is not a production deployment approval. |
High-risk operation
Use explicit authorization, a written reason, a confirmation gate, and post-action verification. Documentation does not grant permission to change a deployment.
Operational controls
Use the smallest verified control for the task. Keep provider, host, legal, and operator responsibilities separate from application behavior. When a control is not implemented or not verified, leave it disabled or mark it as a limitation.
Verification
Verify the route, relevant API or configuration state, negative path, audit/evidence result, and public effect before closing the task. Record unknown or configuration-dependent behavior as a limitation.