In the self-help lane EstateDraft runs no model at all. Every statute, citation, and clause in your packet is fixed, source-locked text drawn from the official Texas statutes — the Estates, Property, Family, and Health & Safety Codes and the Texas Constitution, and every answer is yours, typed as written — never generated by AI at request time. So your plan can’t cite a made-up statute or hallucinate the law the way generic AI tools can.
EstateDraft is Texas-only software, is not a law firm, and does not provide legal advice. It does not select a document for you, apply the law to your situation, or review your entries; the Texas corpus is loaded verbatim and SHA-256 byte-verified. This software is not a substitute for the advice or services of an attorney.
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.
Operative clauses come from a fixed clause library keyed to the statutes; your answers land in the named article typed as you wrote them. No model phrases, fills, or invents a clause.
The provenance invariant fails the build on any cited section the Texas corpus does not hold, and EstateBench re-runs the determinism, rules, and byte-exact quote checks on every release.
Keep in mind: A page or document that cites a section outside the corpus fails the build. Capabilities, limits and refusals
The engine, measured
Every release runs a deterministic evaluation suite in CI — zero model spend, reproducible from the repository: 469 checks across determinism, the Texas rules matrix, corpus resolution, retrieval selection, the audits, the agents, execution ceremonies, byte-exact statutory quotes, and the red-team library. Latest committed result: 469/469 passing (commit 73bced9). Methodology and the full table →
0 tolerated — a cite resolves against the hashed corpus or renders as a visible verify flag
100% catch required on the red-team corpus — instrument text from a chat surface kills the response
Byte-exact against the hash-pinned corpus (the Phase-8 verifier) — a drifted word fails the build
Same inputs, same documents, byte-stable — asserted on every drafting fixture, every release
These bars are held as a live accuracy SLA for released Texas work: the numbers above are recomputed on every release's eval run and checked against production audit rows as they accrue.
No. EstateDraft assembles operative legal text deterministically from a fixed clause library, and every statute is verified verbatim text retrieved from the Texas corpus. In the self-help lane no model runs at all: your answers are typed into the named article as you wrote them. Firms license Claude Opus 4.8 inside a gated workstation, and there too it never authors the statute, citation, or operative clause.
Every Texas statute 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.