PostgreSQL will own SupportDesk AI's durable business truth: organizations, users, memberships, tickets, approvals, knowledge metadata, AI runs, and audit history. A relational database provides transactions, constraints, indexes, concurrency control, backup, and recovery. Durability still depends on correct configuration, tested backups, and operational discipline.
If Docker is available, create compose.yaml:
This literal password is acceptable only for an isolated local learning environment. Use injected secrets and managed identity or rotated credentials in real environments.
The rollback count and committed row are observable evidence. Delete the practice table when finished.
Do not store plaintext passwords, API keys, unnecessary raw prompts, unrestricted provider payloads, or customer documents without retention and access policy. Encryption at rest does not solve overcollection or overly broad queries.
AI operations need durable lineage: which approved inputs, prompt/schema versions, retrieval references, model settings, output, safety decision, and human approval produced a business artifact. PostgreSQL can keep that audit graph transactionally connected to the ticket. Redis cannot be its only home.
Create a role matrix for migration, application, read-only analytics, and operations. State which can create tables, read ticket bodies, or manage roles.
Acceptance criteria: the runtime role cannot alter schema or manage users; the restore operator is defined; every privilege has a reason.