Product governance
The number never travels without its confession.
Data, configuration and access change over time. OrdinateDB keeps those changes queryable so an answer can include what produced it, what it meant and who was allowed to see it.
Versioned configuration
SPEC 01 §6 · SPEC 11 §4Compare what changed, then restore by making another change.
Asset models, templates, stream bindings, limits, permissions and calculation rules retain versions. Administrators can compare two moments, attribute each change and apply a previewed restoration without rewriting the original history.
Lineage and quality history
SPEC 02 §9 · SPEC 04 §5Keep the evidence attached to the value.
Query results can carry source, quality composition, visible lossy ranges, provisional state and manual origin. A chart cannot quietly promote an uncertain or reconstructed value to the rank of a measurement.
Identity and permissions
SPEC 10 §2–5Explain who can do what, where, and why.
OIDC groups map to roles; roles grant capabilities over asset and folder scopes. Grants inherit down a visible hierarchy, and their versions answer historical questions such as who could read or change an asset at a particular time.
Calculation history
SPEC 05 §4 · §7Derived values retain the rule that made them.
Each output identifies its declared inputs and rule version. A rule change creates a visible boundary; previewed backfill can recompute a chosen range while retaining which version produced each result.
Tamper-resistant audit
SPEC 10 §8Changes append; the record does not quietly disappear.
Configuration, permission, approval and authentication events are attributed and retained through the same versioned model. Restore, redaction and correction create new auditable events instead of erasing the previous state.