Evidence: case packs, sign-off packs, savings and Consumer Duty
Tag work with a case reference and get a signed case file for any complaint, a signed sign-off pack for a risk committee, a pilot savings report on your own traffic, and Consumer Duty outcomes by product and vulnerability driver.
Evidence
Vorim already signs every decision, approval and audit event. These calls turn that record into the documents people ask for: a complaints team wants one case, a risk committee wants to know an agent is safe to launch, a buyer wants to know what a pilot saved, and a board wants Consumer Duty outcomes. Everything here is also on the dashboard under Evidence.
Tag work with a case reference
Send your own case or customer reference as caseRef on actions and intents, or as metadata.case_ref on audit events. Use an opaque reference (letters, digits and . _ : @ -, up to 128 characters), never a name; a value with spaces is refused.
await vorim.beforeAction({
agentId, actionType: "issue_refund", actionTarget: "/refunds",
payload: { amount: 7250, currency: "GBP" }, // minor units: £72.50
caseRef: "CMP-2026-0142",
});
const pack = await vorim.getCasePack("CMP-2026-0142");
// pack.payload.timeline: every decision, approval, intent, outcome and mandate, in order
// pack.hash + pack.signature: the platform's Ed25519 signature over the whole pack
const check = await vorim.verifyEvidence(pack); // or verify offline with GET /v1/trust/keystypescriptv.before_action(agent_id, "issue_refund", action_target="/refunds",
payload={"amount": 7250, "currency": "GBP"}, case_ref="CMP-2026-0142")
pack = v.get_case_pack("CMP-2026-0142")
assert v.verify_evidence(pack)["ok"]pythonTo prove later what a pack said on a given day, keep it with a timestamp. Vorim sends the pack's SHA-256 to an RFC 3161 Time Stamping Authority (DigiCert's public service, whose tokens chain to a root your systems already trust), checks the token covers that hash, and keeps it with the pack. Anyone can verify it with openssl, without Vorim.
const kept = await vorim.storeCasePack("CMP-2026-0142");
// kept.timestamp: { ok, tsa_url, gen_time, token_b64, verify } (ok: false with the error if the TSA was down)
// openssl pkcs7 -inform DER -in pack.tst -print_certs > tsa-chain.pem
// openssl ts -verify -digest <pack sha256> -token_in -in pack.tst -untrusted tsa-chain.pem -CAfile /etc/ssl/cert.pemtypescriptA case pack holds only what carries the reference. It records what the agents and the people did; it does not judge whether the outcome was fair.
Sign-off packs for a risk committee
Before an agent goes live, run it through things it must refuse and work it must be allowed to do. Each scenario goes through the real decision pipeline in shadow (nothing is written and the agent does not run). The pack also answers the committee's questions from your live settings: what the agent may do, what stops it, who approves, what happens when no one answers, how fast it stops, and whether its records are signed.
const pack = await vorim.runSignoff(agentId, { preset: "fintech", label: "pre-launch v2" });
// preset "fintech": a large payment to a new payee, a refund to another account,
// a change of contact details, a full customer export, a credit limit above policy
pack.verdict; // "pass" | "pass_with_findings" | "fail"
pack.payload.committee; // [{ question, answer, evidence }]
// or bring your own: { scenarios: [{ name, action_type, payload, required_scope, expect: "not_allow" }] }typescriptLibraries for the jobs fintechs ask about first: refunds, collections, credit and aml (alert triage), beside fintech and hazards. Each pack also maps its evidence to the five principles of the PRA's SS1/23 on model risk management, as material for a validator, not as validation.
A pack is a snapshot, so Vorim keeps it current: when your rules change, the agent's latest pack runs again, and a worse result raises the signoff.regressed webhook. getSignoffDiff(id) lists what changed since the pack before: the verdict, each scenario that flipped, settings, answers and permissions.
A pack fails when anything you said must not be allowed gets through. It records what Vorim would decide under the configuration it names; it is not a certificate that the agent is safe.
Pilot savings report
Start a pilot with shadow rules (they record what they would decide without blocking). At the end, the report shows per rule how often it fired or would have, the value of the actions it held back or would have, how many went or would have gone to a person, and what that review costs at your own minutes per review and hourly cost.
const r = await vorim.getSavingsReport({ days: 30, reviewMinutes: 8, hourlyCost: 45, currency: "GBP" });
r.rules; // per rule: fired, would_fire, value_held, value_would_hold, sent_to_person, ...
r.totals; // review_hours, review_cost, would_review_cost, reviewed_sharetypescriptValue held is money a person looked at first, not money saved: some of those actions were fine. Amounts are summed as stored, with no currency conversion.
To prove savings, record what happened afterwards. Send a complaint, chargeback, confirmed fraud, reversed refund or no issue against each decision; the report then shows the actions that went wrong a shadow rule would have caught, the ones no rule touched, and the refusals that drew complaints.
await vorim.recordActionOutcome({ decisionId: "dec_...", kind: "chargeback", amount: 4500 });
const r = await vorim.getSavingsReport({ days: 30 });
r.outcomes; // went_ahead_and_went_wrong, shadow_would_have_caught, no_rule_touched, stopped_but_complained, rules[]typescriptConsumer Duty outcomes
Declare the result an agent expects, tag the intent with a product and, when the customer is vulnerable, the FCA's drivers of vulnerability from FG21/1 (health, life_events, resilience, capability). Record later whether it happened. The report groups outcomes by product and by driver, and flags a gap of 10 points or more against customers not flagged as vulnerable.
const intent = await vorim.declareIntent({
agentId, goal: "Agree an affordable payment plan",
expectedOutcome: "A plan the customer can afford, agreed within 5 working days",
product: "Payment plans", vulnerabilityDrivers: ["life_events"], caseRef: "CUST-88213",
});
// ... later, a person reviews it on the dashboard (or the agent records its own view)
await vorim.setOutcomeDefinition({ product: "Payment plans", good: "Plan agreed in 5 days and still running at 90 days" });
const duty = await vorim.getConsumerDutyReport({ days: 365 }); // groups, by_driver, driver_gaps, definitionstypescript- Shares use outcomes a person reviewed, never the agent's own view, and appear once 5 are reviewed in a group.
- A gap is a signal to look at, not a finding. The report supports a Consumer Duty review; it does not show compliance on its own.
- The dashboard exports it as PDF, Excel, CSV and JSON.
Book a demo for a walkthrough, or contact us for support. For enterprise needs, reach out at sales@vorim.ai.