QgenticQgentic
Qgentic / opres / live demo
Live demo · Qgentic OpRes

Watch a breach get computed.

A narrated walkthrough of the Qgentic dashboard running a resilience cycle, then the engine underneath it: a real, unedited run, offline, on the synthetic GRC export bundled with every download. Pennine Rose Building Society (a fictional UK-only firm, exactly who DORA doesn't reach) had two incidents this period. One resolved inside its tolerance. One ran 14.5 hours against a 12-hour tolerance, and the engine computed the breach from timestamps. Then try the determination yourself.

The dashboard, through a full run

A guided, narrated walkthrough of the real Qgentic dashboard, the screen your team works in. It runs the whole cycle itself: services and incidents read from your GRC export, a tolerance breach computed from timestamps, a named person's approval, the regulator package prepared and hashed. No terminal, no input required. See how Qgentic collects this data from your systems.

The same run, at the engine level

Behind the scenes Qgentic OpRes · qgentic run

The engine underneath. Your team approves in the Qgentic dashboard.

Transcript of an offline run on the bundled sample data (service start-up lines condensed). Reproduce it with the evaluation binary (QGENTIC_PACK=opres qgentic run) and take the approval yourself.

Four moments worth pausing on

  1. The breach was computed from timestampsINC-2026-052 was detected at 21:30 and resolved at 12:00 next day: 14.5 hours, calculated from timestamps. Online banking's board-approved tolerance is 12 hours. Breach: true, by arithmetic. A hand-set flag that disagrees is refused as validation error OPRES-TOL-008.
  2. Supervisory findings surfaced earlyAlbion Cloud is material with no documented exit plan (OPRES-EXIT-011). Crown Core Banking is material, difficult to substitute, and sub-outsourced, which raises a concentration-risk flag (OPRES-SUB-012). Better your dashboard raises these than your supervisor.
  3. A named approval gated the packageThe submission summary put the tolerance breach in front of the approver. A scoped, HMAC-signed grant valid for 120 seconds then authorised exactly one preparation: register CSV, services CSV, incident report, hashed manifest.
  4. The evidence re-verifiesEvery step landed in a SHA-256 hash chain, re-verified at the end of the run. The prepared package goes to your existing FCA RegData/Connect or PRA channel, with proof of how every number was derived.

The submission package this run produced

The run above ends by preparing a package for your regulator channel, and this is it: the actual files, unedited. The data is synthetic (Pennine Rose Building Society is fictional), but the identifiers are checksum-valid and the 14.5-hour tolerance breach you watched being computed is in the incident report.

FileWhat it is
third-party-register.csvThe register of third-party arrangements, mapped to the services they support
important-business-services.csvThe firm's important business services and their impact tolerances
incident-report.jsonThe operational incidents, with computed durations and the breach determination
manifest.jsonA SHA-256 hash for every file in the package
pipeline-summary.jsonEverything that happened in the run, including the audit-chain verification

Open incident-report.json and find INC-2026-052: the breach flag was calculated from its timestamps.

Tolerance breach, live in your browser

The same computation the engine runs (duration against the affected service's impact tolerance), ported to this page. Nothing you enter leaves this tab.

Assess an incident

Services and tolerances from the bundled sample firm.

Now try to overrule it

Source systems sometimes "remember" incidents kindly.

    See the other platforms, or run it for real

    The download runs this exact pipeline on your hardware, fully offline. Sample data included.