Ordinant makes all of this something your software can work with. It establishes decisions with their basis intact, so people, agents and systems can find them, check whether they apply, see what depends on them and act from them.
Software can recognize the same question.
Ordinant identifies what is being decided and the distinctions that make it the same question or a different one, using your institution’s definitions. That lets software recognize when the same question appears in different work, find earlier decisions about it and apply the requirements that belong to that question. It calls that common reference a Decision Address.
One piece of work can require several decisions, and one decision can be used by several pieces of work.
Ordinant keeps the decisions separate from the work around them and checks whether each use is supported.
Your requirements govern how a decision is formed.
The evidence and judgments needed, who may supply them, any independent checks and how much uncertainty is acceptable belong to the question being decided. Contributions from people, agents and systems are assessed against those requirements for the decision.
We make those requirements explicit from your policies, procedures and the judgment your institution relies on today. Your institution ratifies them before the software uses them to establish decisions.
People, agents, rules and systems contribute evidence and judgment. Ordinant brings those contributions together and establishes the decision only when everything required has been resolved and the supporting contributions meet the declared standard. Until then, it shows what is still needed.
Judgment stays with the contributors. Ordinant checks that the requirements were satisfied; it does not redo the judgment or prove that the answer is right.
The decision keeps what it was based on.
The result includes the question and answer, the requirements that governed it, the evidence and judgments that satisfied them, who or what supplied those contributions, and the uncertainty and conditions accepted in reaching it.
These remain connected. A claim is connected to its source. A judgment is connected to the requirement it satisfied. An earlier decision used as support is connected to the decision that relied on it. The institution can inspect how the answer was established, including which rules applied at the time.
A correction can establish another answer to the same question. The original decision and its basis remain intact, so the institution can distinguish what it decided then from what it can rely on now.
Software can use what the decision establishes.
Because the question, basis and conditions are explicit, another system can check whether a decision applies to its work and whether it establishes enough for that use. Ordinant checks both the supporting basis and the conditions that must still hold. It can distinguish a decision that already settles the question from one that needs more support for this use, or whose conditions no longer hold.
The same decision can be used again.
When another piece of work raises the same question, an existing decision can settle it if its basis meets the requirements for that use and its conditions still hold. Other questions required by that work remain separate.
Actions can proceed from established decisions.
Where action follows, Ordinant uses every decision required for that act to issue an authorization specifying exactly what may be done. This is a Decision Warrant. The executing system checks the warrant and its conditions, alongside its own identity and permission checks, and can carry out the authorized act without reconstructing the judgment. If a required condition cannot be shown to hold, that act cannot proceed under the warrant.
The executing system reports what it did. Ordinant connects that report to the authorization and the decisions supporting it. The institution can inspect what was decided, how it was established, what was authorized and what the executing system reported doing.
Changes can be traced to the work they affect.
When something a decision relied on changes, expires, is withdrawn or proves wrong, Ordinant can find the decisions affected and follow those connections to later work and actions. The institution can then determine what needs attention.
One way to work with decisions across your systems.
Ordinant sits alongside the systems you already run. Your people, agents and applications connect to it to contribute evidence and judgment, find what is still needed, inspect established decisions and carry out the acts those decisions support.
People, agents and machines can all contribute to the work. The decision belongs to the institution.