Worked Examples
These worked examples show how ARAF outputs can be used in pilot governance decisions.
Example 1: Customer Service Escalation Agent
Section titled “Example 1: Customer Service Escalation Agent”Pilot context
Section titled “Pilot context”An organisation deploys an autonomous customer service agent that can approve low-value credits and initiate service actions without human approval.
Governance signal
Section titled “Governance signal”- D1 (Autonomy Gradient) is elevated because the system can commit value and trigger operational changes.
- D4 (Liability Architecture) is moderate where customer remediation pathways are defined but not fully tested.
- D6 (Adaptive Stability) is elevated because weekly model updates are not yet coupled to formal governance change approval.
Pilot action
Section titled “Pilot action”- Set a hard commitment cap for autonomous credits.
- Add a mandatory escalation rule for edge-case categories.
- Require change-control approval before model updates go live.
Evidence expected
Section titled “Evidence expected”- Deployment approval record with scope boundary and cap settings.
- Escalation logs showing when human intervention occurred.
- Change approval records linked to each model release.
Example 2: Procurement Triage Assistant
Section titled “Example 2: Procurement Triage Assistant”Pilot context
Section titled “Pilot context”A procurement team uses an autonomous triage assistant to classify inbound requests, recommend suppliers, and draft purchase pathways.
Governance signal
Section titled “Governance signal”- D2 (Data Sensitivity Exposure) rises where commercial terms and potentially sensitive pricing data are processed.
- D3 (Contract Infrastructure) rises where supplier platform terms do not clearly allocate governance obligations.
- D5 (Commercial Leverage) rises if the team cannot enforce remediation commitments on the supplier.
Pilot action
Section titled “Pilot action”- Restrict ingestion to approved data classes.
- Add contractual language covering decision traceability and audit access.
- Define supplier remediation timeframes and escalation consequences.
Evidence expected
Section titled “Evidence expected”- Data classification controls and access policy evidence.
- Executed contract clauses allocating accountability for autonomous decision support.
- Supplier governance notices, remediation requests, and response records.
Example 3: Claims Routing and Prioritisation
Section titled “Example 3: Claims Routing and Prioritisation”Pilot context
Section titled “Pilot context”An insurer deploys a claims routing system that prioritises claims for handling urgency and allocates review pathways.
Governance signal
Section titled “Governance signal”- D4 (Liability Architecture) becomes central because routing decisions affect customer outcomes and claim handling timelines.
- D6 (Adaptive Stability) is elevated where the model behaviour changes with new data and feedback loops.
- GBI interpretation depends on whether governance controls remain effective through updates.
Pilot action
Section titled “Pilot action”- Define protected categories requiring human review before final routing.
- Record rationale traces for priority assignments.
- Introduce monthly governance review checkpoints tied to incident and complaint data.
Evidence expected
Section titled “Evidence expected”- Routing policy with documented override rules.
- Decision trace records for sampled claims.
- Governance review minutes and approved remediation actions.
How to Use These Examples
Section titled “How to Use These Examples”Use each example as a template:
- Define the pilot boundary and autonomous commitments.
- Map likely dimensional pressure points before deployment.
- Agree controls, ownership, and escalation triggers.
- Build contemporaneous evidence capture into operations.
- Review whether evidence quality supports institutional reliance.
For implementation detail, use the Evidence Checklist.