Watch the register
assemble itself.
Below is a real, unedited run of the Qgentic engine — offline, no AI API, on the synthetic contracts bundled with every download. One contract carries a deliberately broken LEI; one hides its subcontractors. See both checks in action. This is the engine underneath — shown for transparency: in the product, people review and approve in the Qgentic console. Then try the checksum gate yourself — it runs live in your browser, ported line-for-line from the engine.
See the console through a full run.
A guided, narrated walkthrough of the real Qgentic console — 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 approves, the eleven-template 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.
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 LEI
QC-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 blocking
QC-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 human approved; a grant expired
The 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-verifies
Every 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.
Download 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.
| File | What it is |
|---|---|
| B_01.01.csv | One of the eleven populated ITS (EU) 2024/2956 register templates — all eleven are in the zip below |
| manifest.json | A SHA-256 hash for every file in the package (2.1 KB) |
| filing-indicators.json | Which templates are reported in this filing |
| validation-report.json | The validation verdict: zero errors, zero warnings |
| pipeline-summary.json | Everything 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.
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 — no matter what the AI, the ERP, or a tired human supplied. When the checksum fails, the engine repairs from your master data and audits the repair.
See the other platforms, or run it for real.
The download runs this exact pipeline on your hardware, fully offline. Sample data included.