Loading…
Methodology
BenchPath's value is only as good as its discipline. These are the exact definitions behind the labels on every card, and the substantiation behind every public claim. If a claim isn't true, it doesn't ship — enforced by an automated release lint.
A document or page published by the court, clerk, or a judicial officer themselves — an administrative order, a division-instructions page, a judge's practice-preferences PDF, a printable directory. Not a secondary summary, not model knowledge, not a search snippet.
Set only after a live fetch of the official source, with the excerpt traced to the fetched text and a last-verified date recorded. Anything seeded from model knowledge sits at medium confidence with an open review task until it is live-verified.
The document behind a published rule is fetched, hashed (SHA-256), and the bytes are preserved in the repository so the quoted requirement can be reproduced from the exact source. This applies to the ingested procedure corpus — not to every registered source (the daily monitor detects change; it does not archive every page).
Two distinct things, labeled distinctly: (1) rule cards are reviewed before publishing as verified, with reviewer provenance shown; (2) any judicial-tendency synthesis is additionally review-gated — it publishes only with methodology, support count, and sources attached, after a human sign-off. Deterministic source rows (e.g. a quoted page limit) are QA-sampled, not individually re-adjudicated.
high = live-verified against the official source; medium = drawn from model knowledge or a secondary source, with an open review task; unverified = a known gap held as a placeholder, never presented as an answer. Every card shows its level and date.
A daily monitor hashes a normalized copy of each source and flags changes for review. When a statewide rule preempts local ones (e.g. AOSC26-12 / Rule 2.515(d)(2) over circuit AI orders), affected rules are linked to the controlling authority and banner-flagged — history is never deleted. Rescission/vacatur claims are made only after re-fetching the primary source.
Every material public claim, its substantiation, and whether it is shipped or planned. Counts render live from the database.
Every Florida circuit and county — 20 circuits, 67 counties — mapped, with each published rule linked to its official source.
LiveBasis: Computed live from the database (getStats): circuits, counties, published rules, sources. Structural coverage is complete; per-judge procedure depth varies and is shown on /coverage.
home hero, /coverage
Every published rule card shows its source citation, official link, confidence, and last-verified date.
LiveBasis: Enforced by the ingestion discipline; `high` confidence requires a live fetch of the official source. Rendered per card.
rule cards, everywhere
Verified Florida judicial officers in the directory (count rendered live).
LiveBasis: getStats().judges — count of published rows in `judges`. This is a ROSTER count, not a rulings-corpus count.
home stats, /intelligence, /coverage
A rulings corpus that adds evidence beyond written opinions; coverage is early and disclosed per report.
Rolling outBasis: judge_rulings (verified) + CourtListener connector. Coverage is thin and varies by judge; never stated as complete. 0 published judge_insights as of this writing — tendency synthesis is review-gated.
/intelligence
Analytical skills over the verified corpus, badged by real maturity (live / review-gated / pipeline).
LiveBasis: intel_skills registry; status reflects whether an end-to-end path renders real corpus data. Not '15 live AI engines'.
/intelligence
Daily source monitoring detects changes and opens review tasks.
LiveBasis: monitor-sources edge function + pg_cron; normalized-hash change detection with task dedup.
home, /sources
Rules and judicial synthesis are human-reviewed before publishing as verified.
LiveBasis: Reviewer-gated publication; see /methodology for what 'human-reviewed' means (queue vs. sign-off) and reviewer provenance on each card.
home, /intelligence, /methodology
Print / save as PDF from your browser.
LiveBasis: Browser print of the report page. A deterministic server-generated PDF artifact is NOT claimed.
/pricing
Firm seats, shared matters, white-labeled checklists, practice-group routing, and a scoped firm API.
PlannedBasis: Not yet implemented (matter RLS is user-scoped; no membership/seat/white-label flow). Marked '(planned)' until shipped.
/firms, /pricing
Change alerts on what you follow.
Rolling outBasis: In-app follows are live; email delivery and per-practice-group routing are rolling out (Phase 1.1).
/pricing, /firms
Found something wrong? Our corrections process has an expedited lane for judges, chambers, and clerks. See live totals on the coverage page.