Jurisdiction-scoped corpus
Official Jordanian documents are ingested, normalized, and versioned provision by provision. Retrieval is scoped to active jurisdictions — Jordan today, MENA as it is onboarded.
Jordan-first · jurisdiction-aware · source-verified
LKC turns validated legal documents into a searchable public corpus — then answers questions grounded only in retrieved provisions, with citable authority and an auditable trail.
Official Jordanian documents are ingested, normalized, and versioned provision by provision. Retrieval is scoped to active jurisdictions — Jordan today, MENA as it is onboarded.
Every answer traces to source provisions ranked by authority tier. Verification confirms the cited passages ground the output — no retrieved context, no claim.
Workflows run as versioned, sandboxed skills with approval and security gates. Every run is recorded append-only, and external skill use is governed by a provenance and license review.
Row-level security plus a retrieval view that structurally excludes private and matter data. The public surface can never mix with tenant data.
GET /api/v1/skills
POST /api/v1/skills/{id}/execute
POST /api/v1/legal/answerKey-scoped endpoints, jurisdiction and visibility enforcement, and rate limiting. Machine clients authenticate with scoped API keys — secrets never reach the browser.
Lawyer mode — matter-aware workflows, full citation trails, human-review gates.
Citizen mode — plain-language answers to everyday legal questions, grounded in the same public corpus.