Glossary of terms

The words this product uses, in one place. Private to the institution's app.

Approval recorded: A named person signed a gate: who, when, under what conditions, until when. It never means the system may run now.
Run status: Whether a system in use is within its approval, as the records show.
Gates G1 to G5: G1 data and design (the Data lead), G2 validation (the Validator), G3 approval (the CRO), G4 deployment (the CRO), G5 operation and retirement (the Actuary). One named approver per gate.
Approved configuration: The configuration approved at G3 and deployed at G4. When the configuration on live calls no longer matches the one approved at G4, that is a signal.
Tier: The institution's own risk tier, from its tier profile. The records a gate requires follow from the tier. In Nebula Mutual's profile, Tier 1 carries the most obligations: see the tier profile on the Regime profile page.
Boundary modes: Watching only: beside your own gateway, which enforces; the boundary declares every call. Watching and flagging: the boundary declares every call and flags what it sees outside the approval; enforcement off. In the path: the boundary can allow, escalate or block, with enforcement switched on per boundary. Only in the path can it block.
Declaration: One record per call at the boundary, chained to the one before: what was called, and under which policy.
PARA entry: An agent's registry entry under the PARA specification: its faculties (what it can do) and the authority it holds.
PEVG contract: An agent's contract under the PEVG specification, versioned; a new version is a recorded change.
Re-assertion: The owner confirms an entry is still true, and names what that rests on: evidence on the chain, a file, or the owner's word only. Each one is signed and resets the interval the register owner set. An owner who cannot confirm it escalates it to the CRO.
Unexamined set: What a validation did not examine, each item with the reason. The Validator keeps it current; every change is a new version, and earlier versions stay on the record.
Escalation: A signed record that sends a question outside the line that raised it: a re-assertion the owner cannot make goes to the CRO; dissent at G2 goes to Internal audit or the board risk committee chair, never to the approver.
Typed and produced: Typed: entered by a person. Produced: computed by GovernanceOS from other records. Nothing typed is ever shown as produced.
Refusal values: Recorded values such as “none in force”, “not named” or “declined”, each with the date it was checked. The service never fills a value it was not given.
Self-declared: Conformance self-tests run over your own records. The registry is a specification, not a certification scheme.
Examiner key: Read-only, time-boxed access for a supervisor or auditor. Every read is logged.
SACF: For Islamic finance tenants: a second authority, the Sharia board, closes the same records beside the approver.
Intake: A request to use AI, recorded before G1: the request, its owner, purpose, data and its class, the proposed tier and the triage decision. Routing stays in the institution's ticketing.
Vendor class C1 to C3: The AVRF class of a vendor's capability, set by the institution before the questionnaire is issued. C1 carries the most: the capability influences a decision about a person, or handles personal or restricted data. Any doubt means C1.