Versions VS Approvals

The author encountered a bug where both versioned and non-versioned records could be marked as 'actual', revealing a fundamental design distinction. Working with versioned data requires clarifying whether drafts are persisted, which data takes priority, and what triggers new versions. This leads to two distinct patterns: a versioning system where regular data is current and historical versions need special access, versus an approval system where unversioned data is less important until approved.