AutoCore Media Storage Security and Recovery
Defines media authorization, file validation, deletion, and recovery evidence.
Media controls protect both the object path and the listing relationship. A successful upload is not complete until the processed record, visibility, checksum, and public rendering are verified.
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 |
|---|---|
| Authorization | Owners and permitted moderators may list or mutate media according to the service policy. |
| Content | JPEG, PNG, and WebP checks, magic-byte validation, size limits, and image processing reduce file risk. |
| Deletion | Cover ordering, deletion, and orphan cleanup must preserve listing invariants and audit context. |
| Recovery | Restore or reprocess from the authoritative store; rebuild derived variants when evidence permits. |
| Unverified | The source does not establish immutable object lock or a universal malware scanner; do not claim either. |
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.