Methodology & integrity
How Cybiq stays honest
Reviewed August 2026 against Regulation (EU) 2024/2847, OJ L, 12.12.2024.
Most compliance tools wrap a chatbot in a disclaimer. Cybiq is built the other way around: a deterministic engine whose every output is anchored word-for-word to the Official Journal, verified on a schedule, and sealed so you can prove what you relied on. This page explains each layer, because the method is the product.
The engine, not a chatbot
Your answers go through one pure function. The same inputs always produce the same verdict, the same obligations, and the same dates. No language model sits between you and the law, so the legal text cannot be paraphrased, guessed, or hallucinated. All user-facing strings live in one catalogue (questions.ts); all legal weight lives in one corpus of verbatim quotes (corpus.ts). The two never blur.
As a concrete anchor, here is the application clause the engine reads to place every deadline:
“This Regulation shall apply from 11 December 2027. However, Article 14 shall apply from 11 September 2026 and Chapter IV (Articles 35 to 51) shall apply from 11 June 2026.”
Every quote is verified weekly
The corpus is not a snapshot we forgot about. A scheduled check fetches the live Official Journal text from the Publications Office CELLAR endpoint and confirms every stored quote still appears verbatim. If a quote drifts, the check fails before any release ships. A blocked fetch (the EUR-Lex web firewall answers automation with an empty body) is reported as a tooling failure, never as legislation drift, so a network hiccup cannot fake a clean result.
No orphan quotes
The audit works in both directions. Every verbatim quote in the corpus must be cited by the engine or by a public page, or the build fails on an "orphan" quote. And every engine claim must itself cite at least one corpus entry. The result: every legal claim about the Regulation is anchored to a verbatim Official Journal quote, and nothing we store is unused. The corpus covers the CRA text itself, not national implementing measures: claims about national implementation, such as a Member State's designated authorities, are attributed to the named authority's own pages instead. You can read the source behind any line we print.
Documents you can prove
When you buy a pack or download a determination memo, the document is sealed with a SHA-256 hash. The hash travels with the file, so months later you can prove the exact wording you relied on at the time. That is what turns a generated PDF into evidence.
The law still has teeth
Honesty about method does not soften the obligations. Non-compliance carries real exposure:
“administrative fines of up to EUR 15 000 000 or, if the offender is an undertaking, up to 2,5 % of the its total worldwide annual turnover”
“administrative fines of up to EUR 10 000 000 or, if the offender is an undertaking, up to 2 % of its total worldwide annual turnover”
Why this is hard to copy
A competitor can add a disclaimer in an afternoon. Rebuilding a deterministic engine, a verbatim corpus, a weekly verification pipeline, an orphan-quote audit, and a hashing scheme is months of disciplined work with no shortcuts. That distance is the moat, and it is the reason we can show our workings instead of hiding behind them.
Orientation, not legal advice. This page describes how Cybiq is built; it does not assess whether the CRA applies to your product. Verify any figure against the current Official Journal text before relying on it.