A partner asks you what a new circular requires. You paste it into an AI tool and get back a clean paragraph: regulators want crypto firms to check whether they need a payment licence, and there is a deadline soon. It reads well. Then the partner asks the only question that matters, which is what exactly do we file, under which instrument, and by when. And the clean paragraph has nothing to give you, because it was a summary of the law rather than the law itself.
That gap is the whole problem.
A practitioner cannot act on an unsourced answer. They cannot file against a gist, advise a client on a paraphrase, or defend a position they cannot trace back to a primary source. The summary feels like progress and delivers none, because the part that got compressed away is the part the work actually depends on.
This is the OmniLaw position, and it is not a slogan. Every answer carries its citation. Primary sources, not summaries.
The failure mode of summary-first AI
Most AI legal research optimises for fluency. It reads the source, extracts the shape of the argument, and hands you prose that sounds like a confident associate.
The problem is what fluency discards. Summarisation is lossy by design, and in law the losses cluster exactly where the risk lives.
→ Instrument numbers vanish into "a payment services directive" → Dates and deadlines blur into "soon" or "this year" → Cross-references between instruments collapse into "related rules" → The precise scope of who is in and who is out gets smoothed into a generality
None of that is laziness. It is what summarisation does. The model is rewarded for a readable answer, and the readable answer is the one that drops the ten-digit instrument number and the calendar date, because those are the least fluent things on the page.
For most writing, that trade is fine. For legal work it inverts the value. The citation was the product, and the summary threw it out.
A worked example: CySEC Circular C756
Take a real document. On 16 February 2026, CySEC issued a circular to crypto-asset service providers about dual licensing under PSD2. CySEC Circular C756 (16 February 2026)
Ask a summary-first tool what it says and you will likely get something like this: following an EBA opinion, Cyprus regulators want crypto firms handling electronic money tokens to assess whether they need a payment licence, and there are some deadlines.
That is not wrong. It is just unusable. Watch what it quietly drops.
The circular concerns the interplay between two named instruments: Directive (EU) 2015/2366, defined in the circular as PSD2, and Regulation (EU) 2023/1114, defined as the MiCA Regulation. CySEC Circular C756 (16 February 2026) Those numbers are not decoration. They are how you find the controlling text, check the recitals, and confirm the firm is reading the right rule.
The trigger is a self-assessment. Under C756, CASPs are requested to assess whether the crypto-asset services they offer qualify as payment services per the No Action letter, and are therefore subject to licensing from the Central Bank of Cyprus unless other arrangements with an eligible PSP are made. CySEC Circular C756 (16 February 2026) "Check whether you need a licence" is the gist. The self-assessment against a specific No Action letter, with a specific fallback, is the instruction.
Then the dates. CASPs already offering the relevant EMT-related services that qualify as payment services must submit an application for authorisation to the CBC by 20 February 2026. The transitional period provided in the No Action Letter ends on 1 March 2026. CySEC Circular C756 (16 February 2026) "Soon" is not a date you can put in a file note. 20 February 2026 is.
And the scope. The circular's footnote defines the CASPs it addresses as CySEC MiCA-regulated entities and crypto entities operating under the national transitional regime until 1 July 2026, under Article 143(3) of the MiCA Regulation. CySEC Circular C756 (16 February 2026) A summary that says "crypto firms" cannot tell you whether your client is inside that defined set. The Article 143(3) reference and the 1 July 2026 date can.
Same document. One version you nod at. The other version you act on.
What citation-grounded actually requires
It is easy to bolt a link onto a summary and call it grounded. Real citation-grounding is stricter, and it changes how the tool has to work.
→ Primary-source linkage. Every claim resolves to the actual instrument or circular, not to a paraphrase of it. If the answer says 20 February 2026, you can click through to the line that says 20 February 2026.
→ Instrument-level granularity. The answer preserves the identifiers a practitioner needs to verify. Directive (EU) 2015/2366 stays Directive (EU) 2015/2366. It does not become "the payments directive".
→ Cross-reference fidelity. When a circular points at MiCA Article 143(3), or at PSD2, the chain survives intact. The references between instruments are often where the actual legal question lives, and a summary is precisely where they get flattened.
→ Faithful scope. The defined class of addressees, the carve-outs, the transitional windows. These are reproduced, not approximated.
This is harder than generating prose, which is the point. Citation-grounded retrieval across EUR-Lex, Cyprus and CySEC, and Austria is built so the answer and its source travel together. Research across the Union, settled in seconds, with the trail still attached.
The practitioner's verification workflow
Grounding matters because of what a careful lawyer does next. No responsible practitioner files on an AI answer they have not checked. The right question is whether the tool makes checking fast or impossible.
With a summary, verification means starting over. You go find the circular yourself, read it, and reconstruct the specifics the tool dropped. The AI saved you nothing on the part that counted.
With citation-grounding, verification is a loop you can close in minutes.
→ Read the answer and the cited source side by side → Confirm each specific against the primary text: the instrument number, the date, the article → Follow the cross-references one level out where the matter demands it → Then advise, or file, on a record you can stand behind
The tool does not replace the lawyer's judgment. It puts the source one click from the claim so that judgment has something to act on.
The OmniLaw position
A legal answer you cannot trace is not a shortcut. It is a deferred cost that comes due at the worst possible moment, usually a deadline like 20 February 2026.
So the citation is not an add-on to the answer. The citation is the product. The summary is the disposable layer on top.
OmniLaw is built that way on purpose. Citation-grounded retrieval across EUR-Lex, Cyprus and CySEC, and Austria. Every answer carries its citation. Primary sources, not summaries.
See it on your own matters at omnilaw.ai.
FAQ
Does a citation-grounded tool mean the AI output is always accurate?
No, and any tool that promises that is overpromising. Grounding does not guarantee correctness. It guarantees traceability, which is what lets a practitioner verify the answer quickly against the primary source and catch an error before it reaches a client or a filing.
Why not just trust a well-written summary for speed?
Because the speed is fake when the deliverable needs specifics. A summary that omits the instrument number, the deadline, and the defined scope forces you to re-derive all of it before you can act. A citation-grounded answer keeps those specifics attached, so the time saved is real rather than borrowed against the verification you still have to do.
What does "instrument-level granularity" mean in practice?
It means the answer preserves the exact identifiers you would cite yourself. For the C756 example that is Directive (EU) 2015/2366 and Regulation (EU) 2023/1114 by number, the 20 February 2026 deadline as a date, and the Article 143(3) MiCA cross-reference intact, rather than a smoothed-over paraphrase of any of them.
Which sources does OmniLaw cover?
EUR-Lex for EU law, Cyprus and CySEC for the Cypriot regime, and Austrian law. The aim is citation-grounded retrieval across those corpora, so an answer and the primary source behind it arrive together.
