Immutable versioning end to end
Policies, pools and prices are versioned and never edited. Editing a version in place would retroactively rewrite what past executions are recorded as having been permitted.
Obligations around risk management, record-keeping and transparency all assume you can say what happened, when, and under which rules. That is a data-model question before it is a legal one.
Reconstructing which model handled a request, under which policy, at what cost, months later, is impossible if the policy was edited in place and the routing decision was never recorded.
Policies, pools and prices are versioned and never edited. Editing a version in place would retroactively rewrite what past executions are recorded as having been permitted.
The manifest records which candidates were refused and the specific constraint each failed. Demonstrating that a control operated requires evidence of it refusing something.
Settled usage cannot be updated or deleted — a database trigger enforces it. Corrections are adjustment rows, so the original figure remains visible.
Planverity produces the technical records that make compliance arguable. Whether your use is high-risk, and what that obliges you to do, is a question for your counsel. We make no certification claim.