NAMMU
Resources · Blog
Every jurisdiction gets its own system-prompt persona, its own legal-safety guardrails, and its own normativa retrieval collection. Here is how the two-layer prompt assembly, the deterministic routing pipeline, and the Nexus.PJ jurisprudence copilot all fit together — and where the honest gaps are.
Inventum P5
Engineering · Galictis-Legal
July 10, 2026
Once a case is classified and its documents are segmented, Trayectorias overlays the correct statutory roadmap for that specific jurisdiction and process type with actual evidence from the case. Here is how the templates, status inference, two-view split, and seven empty states all fit together.
A Costa Rican expediente export is a wall of pages — demanda, resoluciones, notificaciones, sentencia, all concatenated. Before any analysis can run, Nammu must split it into typed, navigable units. Here is the two-phase pipeline that does it without an LLM on every page.
Once a case is classified, which analyses actually turn on — and which ones don't yet, and why? A transparent map of every analysis gate, the legal reasoning behind each one, and the known gaps we are honest about.
Before any AI analysis runs, Nammu must answer two questions: which legal branch governs this case, and which procedural track is it on? Here is the three-tier waterfall that gets it right — and auditably explains why.
Every page of every legal document you upload is classified and routed to the most appropriate extraction engine — in parallel, without blocking your workflow. Here is how it works.
