THE RISK OS PLATFORM
The harness that puts
agents to work in risk.
Connect evidence, agents, tools and reviewers in one governed workflow. Keep your existing systems and decision authority.
WHAT A HARNESS MEANS HERE
Define the work.
Control how it runs.
An agent performs a task. Risk OS coordinates the process around it.
Loan systems · Documents · Risk models · Data sources
State, permissions, waits, escalations and evidence carried through the workflow.
Domain-specific agents and tools work inside the agreed process.
Credit officers, risk teams and operations retain the decisions assigned to them.
Conceptual operating architecture. System connections and permissions are agreed per deployment.
CONTROL WHEN THE PROCESS CHANGES
Work can wait.
The context stays.
Select a condition to see how the harness is intended to handle the next step.
- 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.
THE PLATFORM FOUNDATION
Same controls.
Different risk workflows.
Context
Source-linked evidence and case state.
What is the task based on?Policy
Versioned rules at workflow transitions.
May this step proceed?Execution
Tool calls, dependencies and resumable waits.
What happens next?Human review
Evidence and exceptions routed for judgement.
Who has authority?Record
Events, versions and review decisions retained.
How did we get here?STARTING FOUNDATION
Built in stages.
Validated with you.
Prototype work demonstrates durable state, versioned rules, resumable waits and source-linked credit review. The first application is credit.
See the credit workflowDefine the pilot boundary
- Which workflow and systems are in scope
- Which actions agents may take
- Which exceptions require human review
- Data access, model routing and security requirements
- Acceptance criteria and operating ownership
Current demonstrations include synthetic cases, simulators and recorded responses. Institution-specific integrations and production controls require validation.
START WITH ONE RISK WORKFLOW