Source intake.
Capture authoritative source identity, versions, dates, formats, licensing constraints, and currentness expectations.
Source to published fact
Esheria separates source intake, canonicalization, extraction, citation verification, legal review metadata, publication tiers, currentness monitoring, and customer application so each boundary remains inspectable.
Publication pipeline
Capture authoritative source identity, versions, dates, formats, licensing constraints, and currentness expectations.
Normalize instruments, provisions, citations, obligations, forms, evidence, penalties, and identifiers without losing provenance.
Test whether source spans support the published fact and preserve identifiers and bounded quote context.
Keep draft, citation-verified, blocked, and published records separate. Production serves only published facts.
Record current pack versions, historical versions, deterministic diffs, change events, and source currentness.
Apply published facts to entity profiles and workflows without copying tenant decisions into canonical legal truth.
Limitations
Published rows are a reviewed subset of the compiled corpus. A pack can have strong published workflows while still carrying stated source, coverage, timing, jurisdiction, or capability limitations.
Applicability results are recommendations based on supplied profile facts. Missing facts produce uncertainty rather than false negative certainty.
Claim verification is available only for packs with an enabled evaluator profile. Other packs return an explicit unsupported-capability response.
Users remain responsible for professional review, legal interpretation, filings, advice, decisions, and compliance implementation.
Inspect the boundary
Review readiness, version, public fact counts, workflows, and limitations for the current release.
OpenSee how APIs preserve citation IDs, source context, and evidence relationships.
OpenUse the pack endpoint for canonical review metadata, not as a tenant workflow queue.
Open