Title: ADR-001 Version: 1.0 Owner: [TENANT_CONFIGURATION_REQUIRED — Architecture] Status: Accepted Last reviewed: 2026-09-07 Next review: [TENANT_CONFIGURATION_REQUIRED] Reviewers: Architecture, Security
The platform must guarantee that workflow status, approval history, offers, Green Form data, and employee records are consistent, auditable, and never lost — including under concurrent access and partial failures. It also uses a vector store for RAG retrieval, which raises the question of which store is authoritative.
A relational database (PostgreSQL or SQL Server — see technology-selection-matrix.md) is the single system of record for all transactional HR data: tenants, users/roles (reference), candidates, TANs, applications, interviews, offers, Green Form submissions, documents metadata, verification/discrepancy records, approvals, workflow state transitions, employee master, and audit logs. All writes to these entities go through ACID transactions. The transactional outbox pattern is used to publish events derived from these writes (see ADR-002 note on agent state, and integration-architecture.md).
Accepted. Superseding this decision (e.g., moving to event sourcing) requires a new ADR and a data-migration plan.
| Version | Date | Author | Change |
|---|---|---|---|
| 1.0 | 2026-09-07 | Documentation package generation | Initial creation |