The Decision Fabric
Governance fails at the moment of decision. Someone has to say yes or no, usually under commercial pressure, usually before the evidence has been assembled. The Decision Fabric takes a proposed action, applies its specialised action-check path within AssureCore using facts already held in TrustGraph, and returns a disposition with its reasons attached.
The action checks are Intent, Data, Model, Decision, Action, Audit and Kill. The action checks run inside AssureCore's Authorisation and Policy Trust Gates. Where an agent runs under an out-of-band hardware supervisor, the Kill check can request network or runtime isolation through that supervisor; a named human still owns the decision to resume.
It does not act on the institution's behalf. It makes the consequence of acting legible before anyone commits.
Dispositions shown here are computed against the demonstration institution. Client evaluations run against that organisation's own graph inside the engagement environment.
Why it is built this way
A disposition, not an opinion
Proceed, proceed with conditions, hold, or refuse. Each one is stated with the gate that produced it and the object whose recorded status decided it. There is no advisory hedge in the middle.
Re-derivable months later
Because every reading resolves to a graph object rather than a judgement in the moment, the same action re-evaluated in a supervisory review returns the same answer, with the same reasons.
Hold is a defensible answer
Where a gate cannot be resolved from evidence, the fabric holds. Institutions do not get into difficulty by pausing; they get into difficulty by proceeding on evidence they could not later produce.