Four ways generic assistants fail on regulatory text
No signup, no gate. Each failure below is demonstrated with a real transcript against the EU funds perimeter, then shown again with a Citenda pack in place.
1 — The stale version
Asked about a provision that was amended, a generic assistant confidently cites the repealed wording as current law.
With a pack: Packs carry the consolidated in-force text with explicit supersession chains — the superseded version is present, but marked as such.
2 — The citation that doesn't resolve
Generated citations look plausible — article numbers, paragraph letters — but a spot-check finds articles that don't exist or say something else.
With a pack: Every unit in a pack has a stable citation key. An answer grounded in the pack cites keys you can resolve to the exact passage, offline.
3 — The missing consolidation
Web sources return the original act; the amending acts are separate documents. The assistant reads one and misses the others.
With a pack: Packs ship the consolidation as the primary text — reading it is reading the in-force rule.
4 — The egress
Every question your team asks a cloud assistant about a live compliance matter is a disclosure to a third party.
With a pack: The zero-runtime path reads pack files directly from disk. Questions, answers and documents stay inside your perimeter. (When you choose the Cowork convenience path instead, data does go to Anthropic's cloud — we say so plainly.)
See it on your own questions
The free preview is a real cluster from the EU Funds pack — try these failure modes yourself.