AutoCore Data and Derived-State Rebuild
Separates authoritative data from rebuildable indexes, variants, and operational caches.
Recovery decisions should begin by classifying the affected state. Rebuild derived state from authoritative records whenever possible; do not restore a stale derivative over a valid source of truth.
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 |
|---|---|
| Authoritative | PostgreSQL records and approved media objects require backup and restore protection. |
| Derived | Meilisearch indexes, generated media variants, and caches may be reconstructed from authoritative state. |
| Queue | Redis-backed work must be classified for retry, deduplication, or manual reconciliation. |
| Integrity | Compare counts, checksums, lifecycle state, and public behavior after a rebuild. |
| Boundary | A successful index rebuild does not prove payment, legal, or consent integrity. |
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.