The aspect store in PostgreSQL is the only authoritative store. The graph and the search index are projections, rebuilt by replaying the change log.
This is the answer to graph-versus-relational: both, but only one of them is true. A graph database as system of record makes versioning, backup and point-in-time restore far harder than they need to be.
Source systems remain authoritative for their own technical metadata. The platform holds a described copy with provenance, never a fork.
Numbers
RPO 5 minutes and RTO 30 minutes apply to the aspect store alone.
Projection rebuild from the change log completes in under 4 hours at 5 million assets; the payload archive covers replay beyond the 7-day log retention.
Version history is online for 24 months, then compacted to first and current with the audit trail retained for 7 years.
Trade-off accepted
Projections are eventually consistent, typically under 60 seconds behind. Search may briefly miss a rename. The alternative — synchronous dual writes — trades a visible, measurable lag for invisible partial failures.
