Skip to main content

Regulatory brain integrity

Every figure Oblifee produces traces back to a rule in its regulatory brain - the cited dataset of fees, thresholds, obligations and labelling requirements. For that traceability to mean anything, the brain has to be trustworthy and it has to be separate. This page explains how its integrity is protected and why the application cannot change it.

A separate dataset the app can only read​

The brain is not part of your workspace and not part of the application's own tables. It is its own dataset, reached over a private connection, and the identity Oblifee uses to read it is granted read-only access. The application can query rates, obligations, citations and confidence statuses - it cannot insert, update or delete a single fact.

This separation is deliberate and load-bearing:

  • The app cannot corrupt the rules. No customer action, and no application code path, can write to the brain. A bug in the product cannot alter regulatory truth.
  • Rules are never copied into your data. Oblifee reads rates live and computes against them; it does not stash a private, drifting copy of the fee schedule in your workspace.
  • What changes the brain is a controlled process, entirely outside the product surface - reviewed, versioned and sourced - not something reachable from the app.

Citations and honesty travel with every fact​

The brain does not just hold numbers; it holds the source behind each one and an honest confidence status. When Oblifee shows you a figure, it carries that citation and that status through to you unchanged. If the brain marks a rate as an estimate, every customer surface that uses it says so too - the product cannot quietly present an estimate as if it were confirmed.

See Confidence labels and Confidence & citations for what the labels mean and how to read them.

Versioned and traceable​

The brain is loaded as a whole, tracked build, so at any moment there is a known version of the rules in force. Features that need to detect change - for example, telling you that the labelling rules behind a saved report have since moved - compare against that recorded version rather than guessing. A saved result therefore records the exact state of the rules it was computed against.

Why this matters​

  • Defensibility. A number you can trace to a cited, versioned source is a number you can stand behind with a regulator or an auditor.
  • No silent drift. Because rules are read live and never mutated by the app, you are not relying on a stale local copy.
  • Clear separation of duties. The product answers questions; a separate, governed process maintains the truth it answers from.

Where to go next​