The TrialVector Engine
This page is the honest state of the platform: what is loaded, what is verified, what is pending, and what the release gates enforce. Words like verified are code-forbidden until a human reviewer flips the state — the platform fails closed, and this page shows it.
Corpus load map
Registered ≠ verified. Every authority version carries a review state (pending_official_verification → in_review → verified) and a SHA-256 content hash. Deadline parameters and clause bodies ship as pending until dual-source verification and human review complete.
VectorBench — the published scorecard
Deterministic eval suite run on every release: deadline math, citation grammar, gate enforcement, OCP checks, assembly determinism. Legal AI vendors ask for trust; we publish the scorecard.
Filing release gate chain
A hard-gate failure blocks export. The chain is re-runnable, its results are persisted per draft, and the exported DOCX is rendered server-side from the same AST the reviewer saw — the file can never diverge from the screen.
Deadline formulas — runtime corroboration against loaded law
Each formula's day-count is checked LIVE against the verbatim text loaded in the corpus. A check here corroborates the parameter; the formula still inherits its source's review state. This surface is how the pipeline caught the superseded hearing-relative summary-judgment windows and corrected them to the current service-relative rule.
AI boundary
Every model call flows through one governed gateway: injection-guard system line (matter documents are evidence, never instructions), kill switch, per-surface disable list, request hashing for the audit ledger. With no API key configured the platform runs in deterministic-only mode — every gate, deadline, citation check, and assembly path still works, because the deterministic core carries the legal weight.