Why: PostgreSQL sequence IDs can become visible out of order and undermine fixed audit pagination. Evidence: Isolated PostgreSQL late-commit reproduction and sequence cache behavior were checked against official documentation. Impact: Adds a reviewable proposal with lock, sequence, migration, rollback, and throughput boundaries; no runtime code changes. Refs: feature/rdm-two-trees-latest-templates W9