Accurate by design — from the statute text, not from a model.
Every statute, citation, and operative clause in your packet is fixed, source-locked text drawn from the official Florida statutes and Probate Rules — loaded verbatim, SHA-256 byte-verified against the official source, and never generated at request time. In the self-help lane no model writes, phrases, or reviews your documents: the questionnaire asks, you decide, and the template records your decisions. Unresolved citations are refused or visibly flagged for verification.
EstateDraftFL is Florida-only software, is not a law firm, and does not provide legal advice. In the self-help lane no model runs at all; the Florida corpus is loaded verbatim and SHA-256 byte-verified.
Retrieved, not generated
Statutes are pulled from a fixed, hashed corpus — not written by the model. A section that isn't source-locked simply can't be cited.
Deterministic assembly
Operative clauses come from a reviewed clause library and a decision tree — your answers are placed as typed; no model phrases them, and nothing invents a clause.
Checked, then adjudicated where it counts
Every document is checked deterministically for completeness and format. In the attorney workspace, the Opposing Counsel Pass™ then attacks a firm's draft and firm staff adjudicate every finding on the approval rail. Self-serve customers receive no automated review of their situation.
The engine, measured
EstateBench — the open eval this platform grades itself on
Every release runs a deterministic evaluation suite in CI — zero model spend, reproducible from the repository: 555 checks across determinism, the Florida rules matrix, corpus resolution, retrieval selection, the audits, the agents, execution ceremonies, byte-exact statutory quotes, and the red-team library. Latest committed result: 555/555 passing (commit a7540382). Methodology and the full table →
Fabricated citations on the golden set
0 tolerated — a cite resolves against the hashed corpus or renders as a visible verify flag
Operative-text tripwire
100% catch required on the red-team corpus — instrument text from a chat surface kills the response
Statutory quotes
Byte-exact against the hash-pinned corpus (the Phase-8 verifier) — a drifted word fails the build
Determinism
Same inputs, same documents, byte-stable — asserted on every drafting fixture, every release
These bars are held as a live accuracy SLA for released Florida work: the numbers above are recomputed from real production audit rows and every release's eval run.
Does AI write the law in my documents?
No. EstateDraftFL assembles operative legal text deterministically from a fixed clause library, and every statute is source-locked text retrieved from the official Florida corpus. In the self-help lane no model runs at all — your documents assemble deterministically from the fixed clause library. In law-firm workspaces the review passes are caged to the source-locked corpus and never author a statute, citation, or operative clause.
What does “source-locked” mean here?
Every Florida statute and Probate Rule the engine relies on is loaded verbatim, SHA-256 byte-verified against the official source, and fixed. Documents draw from that corpus rather than generating law at request time, so a plan can't cite a made-up statute or hallucinate the law the way generic AI tools can.