For Florida law firms
Funding as evidence: each asset's way into the plan, its standing read from evidence with its basis — never from a box
firm lane · Deterministic — no model call
Current availability
ShippedConfigured and enabled: a firm's staff on the firm's estate-plan matters; an asset funds the trust of an approved, released version.
- Where it lives
- The firm's estate-plan workstation (/admin/estate-plans/[id], Funding) · the client's plan page (/estate-plan/[id], Funding your trust) · /api/admin/estate-plans/funding · /api/admin/estate-plans/funding/letter · /api/estate-plan/funding
- What unlocks it
- the firm's staff keep the funding record of their firm's estate plans; the plan's own client reads each asset's standing and may report one done
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
- ShippedThe approved trust's Schedule A seeds the assets to fund — each line exactly as the approved version prints it, checked against that version by the database; the firm adds any asset the Schedule does not list.
- ShippedThe firm determines how each asset reaches the plan: retitled to the trust, a beneficiary designation (its own track — never a title transfer), the General Assignment signed with the trust, or kept outside the trust with the firm's reason.
- ShippedEach asset's standing is read from its evidence, appended and never edited, each piece with its basis: the platform's record of an instruction, what the client reported, what the firm reviewed, what the institution confirmed in writing. A Schedule line is a listing, not funding; no field says an asset is funded.
- ShippedEvery request to an institution is a prepared action in the common outbox — written with the request in one step, its payload the request letter (the institution's requirements and forms; it changes nothing on its own) and its hash, held for the firm to send, and recorded as sent only on that action with its receipt.
- ShippedA document the record rests on is the matter's own, past its safety check, its stored bytes re-hashed against the hash the ingress recorded.
- ShippedA confirmation or a reviewed document is read against the asset — the trust's title (abbreviations such as TTEE, REV, LIV, U/A/D read in full), the trust's executed date (its completed signing record) and the account's last digits; any disagreement opens a review the firm's attorneys are told of, and only one of them closes it, with a reason.
- ShippedThe assignment track rests on the trust's completed execution record — the General Assignment is signed with the trust.
- ShippedThe client sees each asset, how it reaches the plan and its standing with the date it speaks of — never a note, a person, a document or a hash — and may report an asset done; the report is kept as the client's own until the firm reviews it or the institution confirms it, and the firm's attorneys are told of it.
Limits
- Firm matters only: the self-help service's funding packet (the institution letters, the general checklist and the worksheet the customer fills) is unchanged and keeps no funding record.
- The record does not contact institutions: a request is held for the firm to send by mail, courier, portal, fax, hand or email, and is recorded as sent with its receipt.
- A title comparison reads the trust's name, its executed date and the account's last digits; a designation naming individuals is read by the firm, not compared.
- A standing says what the evidence shows; whether an asset is properly titled or designated stays the supervising attorney's judgment.
What EstateDraftFL refuses
| Reason code | HTTP | What it means |
|---|---|---|
| auth_required | 401 | The funding record needs a signed-in member of the firm's staff (the client's view and report need the plan's own client). |
| invalid | 400 | A field could not be read — the asset, its track, a date (today or earlier), the method, a document (the matter's own, safety-checked, these bytes), the stated title, or a reason — nothing was recorded. |
| forbidden | 403 | The firm's staff keep the funding record. |
| not-attorney | 403 | Only one of the firm's attorneys closes a review. |
| not_found | 404 | The plan or the asset is not in the firm's view. |
| not-approved | 409 | The plan has no approved, released version naming the trust — funding is recorded against the approved trust. |
| already-open | 409 | A request to this institution is prepared and not yet sent — record it as sent first. |
| out-of-order | 409 | That step is out of order — a track changes only before anything passes between the firm and the institution; a review closes only while one is open. |
| closed | 409 | The asset is withdrawn (or kept outside the trust) — it takes nothing more. |
| matter_archived | 409 | The matter is archived — its records can be read, not added to. |
| unavailable | 503 | The plan, the asset, the version or the document could not be read — or the step could not be written — just now; nothing was recorded. |
Evidence
- supabase/migrations/20261001140000_phase13_funding_evidence.sql
- src/lib/funding/model.ts
- src/lib/funding/request.ts
- src/lib/funding/server.ts
- src/lib/funding/document.ts
- src/app/api/admin/estate-plans/funding/route.ts
- src/app/api/admin/estate-plans/funding/letter/route.ts
- src/app/api/estate-plan/funding/route.ts
- src/components/funding/FundingPanel.tsx
- src/components/funding/ClientFundingCard.tsx
- src/lib/funding/model.test.ts
- src/lib/master-plan-phase13-part5.test.ts
- docs/security/MASTER-PLAN-PHASE13-PART5-2026-10-01.md
Last reviewed 2026-10-01