For Florida law firms
Source-change impact: what each piece of work rested on, and what to review when that changes
firm lane · Deterministic — no model call
Current availability
ShippedConfigured and enabled: firm staff of the matter's firm; the rollback lever SOURCE_IMPACT_PROPAGATION=off stops new proposals.
- Where it lives
- /admin/matter/[id]/sources/changes · Today → Sources changed · /api/admin/source-impact · /api/admin/source-impact/review
- What unlocks it
- firm staff of the matter's firm; recording a review takes an attorney-level role, current firm terms acceptance and the firm's responsibility confirmation
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
- ShippedEvery newly sealed draft, every review and every approval records what it rested on: each statute section's text, the document version it read, and the intake answers — each by fingerprint, and an answer to exactly the sections whose text shows it.
- ShippedA revised upload, the weekly corpus-freshness check, a recorded statute change or a manual check produces one reviewable proposal per matter, naming each affected work and section with the passage before and now and the reason.
- ShippedSections a change does not reach keep their decisions; a change in answers no section shows is named as unknown scope.
- ShippedEach item is decided keep (the work still stands) or update (the work needs a human revision); decisions are final. Nothing is ever redrafted or regenerated automatically.
Limits
- Work sealed before 2026-09-25 carries no recorded sources; each scan counts it as unknown scope instead of passing it silently.
- A scan reads up to 400 recorded sources per matter, newest first, and says when it was partial; a statute change reaches up to 25 matters per pass.
- A statute is recorded against the whole document that relied on it — the corpus records which laws a document used, not which clause.
- An intake answer is tied to the sections whose text shows it; an answer no section shows is covered only as unknown scope.
- A proposal with a source that could not be read cannot be closed until the sources are checked again and read.
What EstateDraftFL refuses
| Reason code | HTTP | What it means |
|---|---|---|
| forbidden | 403 | The session is not firm staff. |
| attestation-required | 403 | Recording a review takes an attorney-level role and the firm's responsibility confirmation. |
| not-found | 404 | The matter or proposal is outside the caller's firm. |
| unreadable | 409 | A source could not be read, so the proposal cannot be closed yet — check the sources again. |
| undecided | 409 | Every changed or unknown-scope item needs keep or update first. |
| already-reviewed | 409 | The proposal was already reviewed; its decisions are final. |
| rate-limited | 429 | Source checks are limited per ten minutes; the reply names the wait. |
| scan-failed | 503 | The sources could not be checked just now — nothing was recorded, and it is not a clean result. |
| audit-unavailable | 503 | The decision's audit record could not be written; reload and retry. |
Evidence
- src/lib/impact/core.ts
- src/lib/impact/server.ts
- supabase/migrations/20260925220000_phase7_source_pins_change_sets.sql
- docs/security/MASTER-PLAN-PHASE7-2026-09-25.md
Last reviewed 2026-09-25