Give risk workflows an operating layer.
Coordinate agent tasks around the evidence, policy and approval authority for each case. Track what can proceed, what is waiting and who needs to act.
From institutional policy to the next action.
The harness is the part of Risk OS that coordinates tasks, checks permissions and preserves the case record.
Operational systems · Documents · Risk models · Data sources
Responsibilities shared across tasks and transitions.
Agents and tools carry out the tasks defined for the workflow.
Risk teams, operations and reviewers exercise the authority assigned by the institution.
Operating architecture. System connections and permissions are scoped for each pilot.
A missing document and a policy exception need different next steps.
Credit illustrates the mechanism here. Compare a complete file, a request for evidence and a coverage exception. See what holds the case and what allows it to proceed.
Credit review scenarios
- 01Coverage recomputed: 1.24×
- 02Minimum required: 1.25×
- 03Exception sent for review
Human review required
The calculation stays attached to the finding. A person reviews the exception before the next authorised step.
Five responsibilities across every workflow.
Context
Source-linked evidence and current case state.
What is the analysis based on?Policy
Versioned rules checked before the next step.
Does the case meet the requirement?Execution
Tasks, dependencies and waits that can resume.
What needs to happen next?Human review
Findings and evidence routed to the authorised reviewer.
Who can resolve the exception?Record
Evidence versions, events and decisions retained.
How was the conclusion reached?What you can evaluate today.
The operating layer retains workflow state, applies versioned rules and resumes work after a wait. The credit application adds memo review and monitoring.
A pilot connects these components to the institution’s workflow and systems.
Review the credit demonstrationSet the operating scope
- The risk workflow, required evidence and systems
- Actions agents may take and checks they must pass
- Exceptions and approval limits for each reviewer
- Data access, model routing and security requirements
- Acceptance criteria and operating ownership