For Florida law firms
The dispute preparation pack: the chronology, the issues with their sources, the requests to draft and the approved filing set
firm lane · Deterministic — no model call
Current availability
ShippedConfigured and enabled: the firm's staff, on a matter they can open.
- Where it lives
- The matter's Dispute pack door (/admin/matter/[id]/dispute-pack) · the Command tab's Dispute readiness · /api/admin/dispute-pack
- What unlocks it
- the firm's staff on the firm's matters, behind the matter's wall
Status is evaluated against this deployment's configuration by the capability-status service at build time; the catalogue's facts were last reviewed on the date shown.
Capabilities
- ShippedA chronology of every dated fact on the matter — its own dates (death, acceptance, letters, notice to creditors, termination), steps completed and windows passed, documents received, money in and out, statements executed, reconciliations recorded, requests and responses, limitation notices — oldest first, each naming the record row it came from; a moment is the day it was in Florida.
- ShippedThe issues: the dispute-readiness questions a court could ask about the record, with what is missing and what to gather, and the propositions ledger's statements with the sources that support or contradict each.
- ShippedThe requests to draft: each thing an issue says to gather, tied to its issue — drafts only; the pack sends nothing.
- ShippedThe people and institutions the record names — beneficiaries, the ledger's payees and payors, the recipients of limitation notices — with where each appears; a list to consider, never a claim that anyone is a witness.
- ShippedThe filing set: the matter's approved and released court files (probate filing sets and drafted documents), each re-hashed against its recorded SHA-256 and checked against Rule 2.520(a) from its own bytes — letter size, 1-inch margins, the 12-point floor and numbered pages for a Word file; the page size for a PDF, which says what it cannot check.
- ShippedOne archive: an accessible README, a CSV for each part, the filing set with its format checks, pack.json and a SHA-256 for every file — stored privately, answered as a one-hour link, and issued only once the audit record is written.
- ShippedEvery sentence the pack writes passes the readiness check's no-prediction tripwire; a read that fails makes no pack and names what could not be read.
Limits
- Preparation, not a prediction: the pack says nothing about any outcome, and it is not legal advice — the firm's Florida attorney decides what is used.
- An estate plan's instruments are not in the filing set: wills and trusts are not court filings here, and the public-filings foundation never takes them.
- Rule 2.520 is the statewide format; local practice (the circuit, the clerk, the division, the judge) adds its own — BenchPath and the court's pages are named on the page and in the archive.
- The chronology is what the record holds: an event the record does not date is not on it, and a record the firm has not entered is not inferred.
- The page shows the first 300 dated facts; the archive carries all of them.
What EstateDraftFL refuses
| Reason code | HTTP | What it means |
|---|---|---|
| forbidden | 403 | The session is not the firm's staff. |
| bad-request | 400 | The matter is not named. |
| not-found | 404 | The matter is not found, or the caller cannot open it. |
| unavailable | 503 | A part of the record, or the approved court files, could not be read just now — no pack was made; the message names which. |
| prediction-language | 500 | The pack's own wording failed the no-prediction check — no pack was made. |
| pack-unavailable | 503 | The archive could not be assembled or stored just now — nothing was issued. |
| audit-unavailable | 503 | The pack's audit record could not be written, so no link was issued. |
Evidence
- src/lib/dispute-pack/compose.ts
- src/lib/dispute-pack/summary.ts
- src/lib/dispute-pack/build.ts
- src/lib/dispute-pack/compose.test.ts
- src/lib/dispute-pack/route.test.ts
- src/app/api/admin/dispute-pack/route.ts
- src/app/admin/matter/[id]/dispute-pack/page.tsx
- src/components/dispute-pack/DisputePackView.tsx
Last reviewed 2026-10-03