NEXUS LEGAL
It searches, cross-references and summarizes a corpus of 150M+ legal documents across 60 jurisdictions — surfacing relevant jurisprudence, legislation and regulatory precedents with verified citations and source URLs. Nexus Legal is a research and reference tool. It does not provide legal advice and does not substitute professional legal counsel.
Memo · termination of a supply contract
The supplier's persistent short deliveries plainly go to the root of the contract — see Marston v Delport Logistics [2026] EWCA Civ 415, on repeated defective instalments under a running supply arrangement. The buyer may therefore terminate under section 31(2) of the Sale of Goods Act 1979, which on the draft confers an automatic right to treat the whole contract as repudiated without notice.
Official source · in force
Sale of Goods Act 1979, s 31(2) — whether a defective instalment repudiates the whole contract is a question in each case, turning on the contract's terms and the circumstances; it is not automatic and the innocent party must elect to terminate.
AI draft
Sale of Goods Act 1979, s 31(2) — grants an automatic right to treat the whole contract as repudiated without notice.
Across 60 jurisdictions. Nexus flags — the lawyer decides.
Request technical demoPositioning
Traditional editorial platforms are excellent knowledge repositories: they give you law and case law. But they do not tell you whether your 300-page contract contains a lethal cross-clause that contradicts that law. Nexus Legal is not a search engine; it is an analytical engine that audits the real transaction document against the legal framework, detecting legal gaps, default risks, and procedural frictions before signature.
The danger of the "Copilot" vs. source-anchored verification: generic AI models are designed to please users (confirmation bias) and tend to hallucinate facts to fill gaps. Our architecture is adversarial. Every legal conclusion is attacked in real time by a second Legal Validator (Node B) applying a "Presumption of Inaccuracy." If the system cannot anchor its conclusion to literal text in your document (Layer A), the transaction is blocked. We move from probability to source-anchored verification (L1–L5 scale).
The four pillars of end-to-end traceability
Every statement, risk or deadline is tied to the exact page, line and clause of the source document. When documentary evidence is missing, the conclusion is blocked — never paraphrased, never inferred. The Isolation Rule prevents the model from filling gaps.
Every conclusion from Analyst Node A is challenged in real time by Validator Node B under the "Presumption of Inaccuracy." Detected discrepancies are logged as findings with severity (H-001, H-002…) and verdict (CONFORMING / NON-CONFORMING → CORRECT AND RESUBMIT), never silently smoothed.
Every session closes with a keyed HMAC-SHA256 integrity seal: any post-issuance change is detectable, and the seal can be re-verified on demand by the issuing system. (On the roadmap: eIDAS qualified timestamps via an accredited QTSP.)
Generic LLMs cite statutes from parametric memory and fabricate references — the Mata v. Avianca pattern. Nexus loads, at request time, a literal block of the statutes in force at the fact date; the model is instructed to cite only from that block. A missing citation is logged as L4-N-NOT-AVAILABLE in the audit-trail, never fabricated.
CITATION VERIFICATION
We verify citations against the real corpus, not by spotting patterns that look fabricated.
Our deterministic verify_cita engine checks every citation against the actual legal corpus — 150M+ rulings and 20M+ statutes. It confirms the cited passage exists and that the legal claim genuinely follows from the source text, applying meaning checks that catch inverted negation, modality, exceptions, quantifiers and numbers. Not pattern-matching, not a guess: a categorical verified, review or not-verified state on every reference, and a publication gate that blocks a dossier with broken citations rather than passing it silently.
Comparative matrix
Four distinct product categories are often marketed under the same label. The table below separates them by scope and by what a risk committee can actually defend.
| Tool | Scope | Forensic defensibility |
|---|---|---|
| Nexus Legal | Deterministic forensic audit | Strict literal anchoring with transactional block when documentary evidence is missing |
| Case-law search engines | Law and case law | Do not audit the real transaction document nor detect lethal cross-clauses before signature |
| Generic Copilot | Pleasing answer | Hallucination and confirmation-bias risk when documentary gaps exist |
| Black-box AI | Opaque summary | No literal traceability or forensic defensibility before committee or court |
SOVEREIGNTY AND TOKENIZATION
The Dissociated-Identity Protocol
Nexus Legal protects professional secrecy and GDPR by a Sensitive-Data Tokenization layer. Before contracts or case files ever reach the analysis engine, the names of counterparties, UBOs and amounts are replaced by unique cryptographic tokens. The AI audits procedural and structural viability blind, enabling privacy-by-design processing without ever knowing the real identity of the subject.
Cryptographic session integrity
Every completed analysis is sealed with a SHA-256 hash of the final output, an ISO 8601 timestamp and an HMAC signature using a per-organization key. The output is stored encrypted at rest with AES-256-GCM under per-organization key isolation. Any post-issuance tampering breaks verification. No external dependencies, no third parties, no public networks — the chain of custody lives entirely inside Nexus's GDPR-compliant infrastructure (Supabase EU + Railway EU).
ZERO RETENTION
No client document is ever persisted on our disks or in our database. Every analysis runs entirely in RAM and is destroyed at session end. We store execution metadata (jobs table) and — only if the user explicitly opts in — the anonymised output. There is no "delete client data" feature because there is no client data to delete. Zero Retention isn't a policy that depends on us; it is an architectural property of the pipeline.
MODEL SOVEREIGNTY · BRING YOUR OWN
Sovereignty here is not a claim about where a server sits — it is about who runs the compute. In bring-your-own mode the firm connects its own AI engine and its own perception models, and the reasoning pipeline runs on them from end to end.
Connect your own inference engine — an OpenAI-compatible endpoint, or Anthropic / Amazon Bedrock — and every generative node (analysis, audit, consultation, opinion, drafting, review) runs on it. Under mandatory-BYO mode the platform never falls back to its own model: with no provider configured it returns an explicit error (HTTP 409), never a silent fallback. This fail-closed behaviour was confirmed in a live independent audit: with no external engine the platform refused to proceed, and once configured it executed on the firm's own engine.
Register your own engine for OCR of scanned documents and for audio transcription, so raw images and audio never leave your infrastructure — the extraction runs on your models, not ours. Together with BYO-LLM this closes the loop: the whole pipeline, from ingestion to reasoning, runs on your compute.
Bring-your-own governs which engine runs the compute — your model, your endpoint. It is not an air-gapped or on-premises-certified deployment, and it does not change Case-File retention: in Case-File mode the extracted text is persisted, encrypted, in the EU workspace.
CONNECTED JURISPRUDENCE
Law isn't interpreted in isolated pieces. A data-protection authority ruling speaks with the GDPR, which is itself read in the light of the Court of Justice of the EU, whose doctrine shapes how supreme courts across jurisdictions rule in labour or commercial matters. Those connections exist — but most legal tools don't see them.
01
Nexus Legal builds and maintains its own corpus of case law and administrative doctrine — not a searchable archive, but a living network of meaning.
02
Every judgment, resolution and statute is semantically indexed and weighted by its real doctrinal weight — how much it has influenced, how often it is cited, how frequently it surfaces in the reasoning of other courts.
03
When the system analyses your document, it doesn't look for text matches. It navigates that network, identifies which case law is structurally relevant to your specific case, and cross-references it against the applicable doctrine — national, European, sector-specific — before issuing any conclusion.
The result is an analysis that reasons like an experienced lawyer: with judgement, with verified sources, and with full awareness of how every piece of the legal order relates to the rest.
Because in law, understanding a rule always requires understanding what surrounds it.
VIGENT LEGISLATION
Generic LLMs cite statutes from parametric memory. The well-known Mata v. Avianca pattern (2023) shows what happens: fabricated references presented as real. We solved this on the legislation side too.
Every Nexus analysis loads, at request time, a literal block of the statutes in force at the fact date. The model is instructed to cite only from that block. If a citation isn't there, the system writes L4-N-NOT-AVAILABLE in the audit-trail instead of fabricating one. Each jurisdiction has its own localised module specifying the official gazette, citation conventions, court hierarchy, statute structure and the country's official language.
Localised modules · official gazettes
BOEEspañolFederal Register · USCEnglishJournal Officiel · LégifranceFrançaisBundesgesetzblattDeutschGazzetta UfficialeItalianoDiário da RepúblicaPortuguêslegislation.gov.ukEnglish관보 (Gwanbo)한국어官報 (Kanpō)日本語DOFEspañolEach supported jurisdiction's statute corpus is indexed from its official gazette and consultable, activated under a Premium contract: when the client signs, we ingest the requested jurisdiction's corpus and the integration begins receiving L4-N-sealed citations.
See all supported jurisdictions →PROFESSIONAL STANDPOINT
Every analysis is written from a declared professional standpoint, and the report says which one on its face. The standpoints are persona, abogado (lawyer), fiscal (prosecutor), notario (notary), registrador (registrar), juez (judge) and asesor (adviser). The identifiers stay in Spanish because they are values on the wire, not labels on a screen. In England and Wales the lawyer standpoint is split into solicitor and barrister, which look at different things: the first at client risk, deadlines and conduct duties, the second at the strength of the argument before the court. The report names both seats rather than assert a choice you have not made. Asking for a variant a jurisdiction does not have is not an error. It means the function is not split there.
ONE CONTRACT · TWO STANDPOINTS
One Spanish private sale contract, analysed twice. The facts do not change: an inherited property whose transfer is not registered, a five-year testamentary prohibition on disposal, 48,000 euros in arras with no further specification, and a power of attorney from 2019.
Read as notario, the question is whether the deed can be authorised at all. It cannot, while the prohibition stands. The seller is still not the registered owner. An authorised copy of the power of attorney, confirmed as still in force, is required before anything is signed. And it catches something the other reading never mentions: the contract is dated in the future.
Read as abogado for the buyer, those same two facts are exposure rather than obstacles. The arras are confirmatory, so there is no cheap way out, only litigation. What comes back is a calendar: a notarial demand by a specific date, then an ordinary claim with nullity as the principal action and termination under article 1124 of the Civil Code in the alternative. It also argues the seller's case against its own client, and states how sure it is.
Same document, same law. The notary asks whether it can be authorised; the lawyer asks when to demand and what to sue for. Neither answer contains the other.
STANDPOINT OF THIS REPORT — Written from the standpoint of "Solicitor / Barrister". The standpoint decides what counts as a finding: another standpoint on this same document would have flagged different things.
In MCP clients the standpoint is a required argument with no default.
DETERMINISTIC DEADLINES
Procedural deadlines are computed under the law of the forum, by rules rather than by a model. You give the base date and the period; what comes back is calendar arithmetic against that forum's own procedural rules and its own holiday calendar, not a generic count of days.
Where a forum is not modelled, the system does not quietly fall back on a neighbouring jurisdiction's calendar. It declines to answer, and says why.
A missed limitation period is not a worse answer. The client acts on the date, files late, and there is nothing left to fix. A plausible date is worse than no date.
CITATION FIDELITY & PROVENANCE
Statute corpora indexed from official gazettes — each jurisdiction under Premium.
Generic LLMs cite statutes from parametric memory — the Mata v. Avianca pattern (2023). Nexus contrasts each citation against the official source: it loads the literal in-force text of every cited article from the indexed statute corpus, blocks the unverified, and seals the verified with [L4-N]. If an article is not in the corpus, the system declares L4-N-NOT-AVAILABLE rather than inventing one. Unverifiable citations are flagged and blocked — they do not reach a verified result.
The moat is provenance, not just verification.
We don't just verify that a citation exists and is faithful to its source. On top of our own multi-jurisdiction corpus, citation identity and citation graph, the system detects related and contrary authority your analysis omitted — and flags the high-weight authority you didn't cite. And when the engine cannot verify a citation against the source, it doesn't present it as settled — it self-flags it for human review (for example, marking a Supreme Court ruling as 'cited from memory — verify in the official case-law database, CENDOJ'). Detectable and auditable, by design.
Nexus Legal verifies the textual fidelity of each citation against the official source and blocks unverified ones. It does not certify the legal validity, applicability or exhaustiveness — the lawyer's professional judgment is always mandatory.
VERIFIED CASE-LAW COMMENTARY
Traditional case-law databases give you rulings commented by jurists. We don't imitate that — we give you what they can't: AI-assisted commentary with verifiable provenance, where every statement tells you where it comes from.
Anchored (green)
A verbatim quote from the ruling's text, or a relation derived from the citation graph — a contrasted fact.
Interpretive (amber)
An interpretive reading, passed through a second adversarial audit layer (Node B) before it is shown.
Anything that cannot be anchored to the text is discarded — with a counter of claims rejected by the gate — and the sense of the ruling is never asserted unless it appears in the verified text.
Each commentary covers the holding summary, topics, statutes applied, relations to other rulings, the sense of the ruling, and an interpretive note.
In the case-law viewer, under each court ruling: ‘Request verified commentary.’
Commentary that doesn't age
Legacy databases give you a static note written once and slowly going out of date. Each Nexus commentary is generated on demand against the current corpus — current in-force legislation, current derogations, current case law. When the law changes, the next commentary already reflects it: no more relying on an outdated annotation.
AI-assisted commentary, verified against the text and the corpus — it tells you where each statement comes from and does not fabricate. It does not replace professional judgment.
HOW THE SYSTEM REASONS
Most legal tools return a list of twenty similar documents. Nexus Legal synthesises a legally reasoned answer — cited, in force, and audited by a second agent before delivery.
Where other engines run a single query by text similarity, Nexus Legal runs four in parallel and cross-references them.
01
Semantic search over the curated corpus: documents with factual circumstances close to your client's case.
02
Every case in which courts have construed the specific article at stake — independent of word overlap.
03
The judgments that cite the relevant ones, and those they cite in turn, tracing the real network of consolidated doctrine.
04
Automatic weighting by real legal weight — the full hierarchy of each supported jurisdiction is modelled independently (for example, in Spain: Constitutional Court > Supreme Court > National Audience > Provincial Courts; equivalent structures apply across the 60 jurisdictions covered by the platform).
AUTOMATIC CURRENCY CHECK
Citing a ruling that has been distinguished or overturned by later case law is one of the costliest mistakes in practice. Nexus Legal solves this with a citation graph of hundreds of thousands of verified doctrinal relations: before any result is shown, it checks in real time whether the doctrine is still in force. Questioned or superseded judgments are flagged with the exact cause. Other platforms rely on human editors updating each card by hand; here it is automatic.
Cite with confidence. No surprises.
CHAIN OF REASONING
Instead of returning twenty similar results, the system drafts the legal reasoning — every claim linked to its verified source.
The consolidated doctrine on the right to be forgotten under GDPR Art. 17 establishes that the right to erasure prevails over the public interest when the facts lack current public relevance — a principle affirmed by leading constitutional and supreme court decisions across multiple jurisdictions and confirmed by data-protection authority rulings in analogous matters. The only relevant exception applies when a duly evidenced legitimate public-safety interest exists, allowing processing to continue. All of this case law is in force and has not been distinguished in the opposite sense.
The system cites; it does not invent. And a second agent (Node B) audits the answer for gaps and errors before it reaches the lawyer.
COVERAGE
Coverage spans constitutional courts, supreme courts, appellate bodies, regulatory authorities, EUR-Lex, CJEU, and ECtHR across 60 jurisdictions. Not millions of unfiltered documents, but those with real doctrinal weight, curated jurisdiction by jurisdiction.
MORE CAPABILITIES
Capabilities the Legal platform exposes today.
Operating System
Defence dossier, human review state machine, evidence tray, automatic deadlines, AI Act traceability and global control inbox — the workflow between AI reasoning and partner signature.
Learn more →Case-File Mode
10-second queries over 170+ documents, audio and video — every answer cites the exact source.
Learn more →Nexus Studio
Design and reuse legal analysis flows. Three prebuilt templates, up to 20 flows per user.
Learn more →Developers
Async jobs and webhooks, Citator and vigent-legislation APIs, MCP/Claude connector and official SDKs — JSON in / JSON out across 60 jurisdictions.
Learn more →Jurimetrics
Judge and rapporteur statistics, litigation trends and Monte Carlo success-probability / stress analysis — decision-support to size a case, not a prediction.
Learn more →Firm & teams
Member invitations, seats, a master console and an append-only firm audit log — end-user firm administration, distinct from the developer Organizations API.
Learn more →Multi-model debate
A premium mode where independent models draft, critique each other and an arbiter reconciles — listing the unresolved disagreements. Consumes ~12 credits per run; the client decides when to use it (not part of the basic allowance).
Learn more →Box integration
Connect Box once via OAuth and run a full ISO 31000 analysis on any file in place — no download, no duplicated workflow, no document retained after the run.
Learn more →Compliance
Forensic audit with multi-model consensus controls, zero-retention execution and audit-grade traceability — built to surface exceptions and contradictions buried deep in a data room, not just summarise.
Learn more →Procedural control
Critical facts are extracted by the model and the calendar maths is delegated to deterministic engines, with preclusion alerts and procedural-prerequisite checks — decision-support, never a substitute for the lawyer's review.
Learn more →Procedural calendar
Case management around computed procedural deadlines: prerequisite verification and preclusion-prevention alerts so a step is never missed. The lawyer's review remains mandatory.
Learn more →Cross-border
Cross-border due diligence over conflicts of law, collateral, regulatory frictions and enforceability across multiple jurisdictions simultaneously — coverage a single local publisher does not give you.
Learn more →TWO MODES · ONE PLATFORM
GUIDED
Nine legal workflows ready today: contract analysis, opinion, due diligence, litigation, multi-jurisdiction, procedural Monte Carlo, assisted drafting, regulatory review, case-law comparison. For lawyers who want structure.
ADVANCED
The multi-agent pipeline exposed directly — Node A analysis · Node B adversarial audit · Node C synthesis. For lawyers who already know what to ask.
Both modes share the same engine, the same chain of custody, the same credits. Junior associates default to Guided; partners drive Advanced.
TIME TRACKING
When the analysis finishes, Nexus offers to convert that session into a categorised time entry: consultation, opinion, due diligence, litigation, M&A, regulatory, contracts, employment, tax, criminal. Export to CSV for your internal system or generate a cryptographically-signed proforma PDF with duration, category and proof of activity. Billable hours stop being a collateral loss of using AI.
DEVELOPER PLATFORM
Nexus ships as a platform, not a UI. Official TypeScript and Python SDKs (npm + PyPI), an MCP server published in the Anthropic MCP Registry, a Microsoft Word add-in, async jobs with HMAC-SHA256 signed webhooks (replay-safe retry schedule 1m → 5m → 30m → 2h → 12h), Organizations API with revocable sub-keys for multi-tenancy, and end-to-end white-label for distributor partners.
Governance for integrators: an AI-quality event bus, signed export to your SIEM, a per-output Ed25519 cryptographic attestation, and delegated policy enforcement (opt-in, off by default). Every AI output signed, auditable in your SIEM, under the policy you control.
ENTERPRISE TRUST SIGNALS
What a CISO, DPO or IT counsel needs in 60 seconds. Linked from /trust and downloadable PDFs from /legal/security-policy.
Full Data Protection Impact Assessment following WP248 / GDPR Art. 35. Ten sections any DPO can review before asking for a demo.
Ricardo González Álvaro, Madrid (Spain) — designated under GDPR Art. 27. Published in /privacy across all locales.
Every user declares their bar and roll number (ICAB, CGAE, NY Bar, Law Society, OAB, etc.). Timestamped in the consent log. API verification with major bars on roadmap.
Card + SEPA via Paddle (Merchant of Record, EU VAT handled). Crypto via NOWPayments. Automatic cryptographically-signed proforma invoicing.
GET STARTED
Set up your account and run the full standard pipeline: contract analysis, 4-D case-law search, guided opinion and assisted drafting. Premium flows are unlocked at first purchase — Node C synthesis, procedural Monte Carlo, multi-jurisdiction comparison and mode=deep (direct Opus + DeepSeek adversarial audit).
Create account →Premium flows unlock at first purchase
AI for lawyers across 60 jurisdictions: it verifies the textual fidelity of every citation against the official source, searches an owned multi-jurisdiction corpus, and runs an auditable, human-in-the-loop workflow. Decision-support — it does not certify legal conclusions.
Before you rely on a citation, the engine contrasts it against the source corpus and flags paraphrased, altered or not-found citations with verification seals ([L4-N] statute, [L2-J] case law); citations it cannot verify are routed to human review.
60 jurisdictions: 59 countries plus the European Union as a supranational layer. Each jurisdiction's corpus is obtained first and then ingested under contract.
No. It is decision-support for lawyers; the lawyer's professional judgment is always mandatory. It does not certify the validity, applicability or exhaustiveness of any analysis.
FROM OUR INSIGHTS
August 19, 2026 · Quantum Nexus Ventures FZCO
Anyone can tell you what a rule says today. The question that costs money is what it meant on the day you acted, and whether you can still prove it.
Read the piece →August 13, 2026 · Quantum Nexus Ventures FZCO
Feature lists are easy to answer and hard to check. These are the questions we would ask, ordered by how much damage a wrong answer does, including the ones that are uncomfortable for us.
Read the piece →August 12, 2026 · Quantum Nexus Ventures FZCO
Human error scatters. Model error repeats. That is not a difference in how bad each mistake is, it is a difference in shape, and it is most of what looks like a double standard.
Read the piece →Nexus Legal
Request a 30-minute technical demo with the engineering team: live walk-through of the L1–L5 scale, the Node A / Node B adversarial validation, the Isolation Rule and the session integrity seal.
NEXUS LEGAL · DETERMINISTIC FORENSIC AUDIT · L1–L5 SCALE