Dedicated logging, audit, and evidence plane
Separation
Heavy compliance/history writes and long-horizon analysis are kept separate from the live transactional database.
Evidence types
The logging plane can include record changes, AI query/retrieval evidence, authorization context, sensitive disclosure, custom-service/appliance events, and tamper-evident chain data.
Design properties
- Append-oriented rather than ordinary mutable application state.
- Integrity can be protected with hash chaining/tamper detection.
- Read/reveal/export/AI decisions can be logged in addition to writes.
- History remains associated with the tenant/application and can participate in customer-owned export/analytics workflows.
Support value
Correlation IDs and structured metadata let support connect user-visible failures with backend/provisioning/audit evidence without exposing secrets to the browser.