AutoCore Data-Store Security
Documents PostgreSQL, Redis, Meilisearch, storage, and network boundaries.
PostgreSQL is authoritative for transactional data. Redis supports queue, cache, and session-related functions. Meilisearch is derived search state and requires a master key; production compose keeps infrastructure ports private.
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 |
|---|---|
| PostgreSQL | Authoritative records, legal revisions, consent receipts, sessions, payment state, and audit records live in the database. |
| Redis | Treat queue and cache contents as operational data with access and expiry controls. |
| Meilisearch | Keep the master key server-side and rebuild derived indexes from authoritative records when required. |
| Storage | Choose local or R2 through the storage abstraction; protect credentials and object paths. |
| Network | Edition-scoped compose names and private service networking reduce accidental cross-installation access. |
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.