Lex Browse everything How it works For developers

Next architecture

the accepted target, its gates, and what has actually shipped

The accepted target architecture, with status read from the registry committed beside the implementation. Nothing on this page is implied to be live.

milestoneoutcomestatus
M1Truthful architecture narrative
Separate live architecture, target architecture, decisions and measured benchmarks.
building
M2Verified artifact publication
A pinned trust root verifies a signed manifest for every served artifact.
building
M3Expandable temporal EU corpus
Configuration selects domains while every accepted work retains all official dated expressions.
building
M4Deduplicated index
lex-index/3 stores repeated wording once without changing timelines, exact text or diffs.
building
M5Local hybrid retrieval
Keyword and local semantic retrieval fuse deterministically only after the public quality gate passes.
gated
M6Lawyer-facing scope filters
Jurisdiction, hierarchy, legal form, binding status, domain, language and date remain explicit.
building

Target path

Reviewed EU scope configuration
  -> every official dated FR/EN expression plus bounded legal relationships
  -> content-addressed text states and occurrence mappings
  -> FTS5 keyword candidates plus local compact semantic candidates
  -> date and hierarchy eligibility
  -> fixed reciprocal rank fusion
  -> the same exact provision JSON, timeline, comparison and UiEffect contracts

Hybrid retrieval remains gated until its public relevance, temporal, latency and memory thresholds pass. Missing official consolidation remains a named gap, never generated wording.

Program hybrid-eu/1, updated 2026-08-06, review status engineer-reviewed.