QgenticQgentic
Qgentic / dora / live demo
Live demo · Qgentic DORA

Watch the register assemble itself.

A narrated walkthrough of the Qgentic dashboard running a full DORA cycle, then the engine underneath it: a real, unedited run, offline, with no AI API, on the synthetic contracts bundled with every download. One contract carries a deliberately broken LEI; one hides its subcontractors. Then try the checksum gate yourself: it runs live in your browser, ported line-for-line from the engine.

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: contracts read from your systems, the register assembled and a broken identifier repaired, a named person's approval, the xBRL-CSV filing package generated, every step re-verified. No terminal, no input required. See how Qgentic collects this data from your ERP.

The same run, at the engine level

Behind the scenes Qgentic DORA · 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 run) and take the approval yourself.

Four moments worth pausing on

  1. The checksum gate caught a bad LEIQC-004's contract carried …145, one digit off. The ISO 17442 MOD 97-10 check failed, the engine looked the vendor up in your procurement master data, repaired it to …144, and wrote the correction to the audit chain. Nothing silent, nothing manual.
  2. The run parked instead of blockingQC-003 supports a critical function but doesn't disclose its subcontractors. The engine drafted vendor outreach, parked the task input-required, and resumed the moment the reply landed, merging one disclosed subcontractor into the supply chain.
  3. A named person approved; a grant expiredThe export happened behind a named approval and a scoped, HMAC-signed grant valid for 120 seconds. No standing access exists: the approval, the grant and the export are three separate audit entries.
  4. The proof re-verifiesEvery service appends to a SHA-256 hash chain. The run ends by re-verifying all of them: alter one historical entry and every hash after it breaks. You can re-run this verification on your own machine, any time.

The filing package this run produced

The run above ends with an export, and this is it: the actual files, unedited, for you to open and check. The data is synthetic (the firm and its vendors are fictional), but the identifiers are checksum-valid, so the validation you're looking at is real. Every file's SHA-256 hash is listed in the manifest.

FileWhat it is
B_01.01.csvOne of the eleven templates this run populates, out of the fifteen ITS (EU) 2024/2956 defines; all eleven are in the zip below
manifest.jsonA SHA-256 hash for every file in the package (2.1 KB)
filing-indicators.jsonWhich templates are reported in this filing
validation-report.jsonThe validation verdict: zero errors, zero warnings
pipeline-summary.jsonEverything that happened in the run, including the repaired identifier and the audit-chain verification (3.4 KB)

Verify any hash yourself: Get-FileHash B_01.01.csv -Algorithm SHA256 and compare it with the manifest.

The LEI checksum, live in your browser

This is the engine's ISO 17442 validator (MOD 97-10, the same scheme as IBAN), ported line-for-line to this page. It runs entirely in your browser: nothing you type leaves this tab. Change any single character of a valid LEI and watch the checksum break.

Validate an LEI

20 characters: 18 alphanumerics + 2 check digits.

✓ VALID — MOD 97-10 checksum holds

Why this matters

The EU dry runs saw ~235,000 validation errors, mostly typos.

A register row with a fat-fingered LEI fails at the regulator, weeks after you filed. Qgentic refuses it at assembly time instead: the validator gate is deterministic code, so an invalid identifier cannot reach the export, whatever the AI, the ERP or a tired human supplied. When the checksum fails, the engine repairs from your master data and audits the repair.

try it: flip any character on the left

See the other platforms, or run it for real

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