Coverage manifests on every workspace run

Current availability

Capabilities

• ShippedWhat each engine received, reproducible by fingerprint: the document, the revised document and the context by SHA-256, each engine's model and a fingerprint of its result.
• ShippedThe matter's documents the person could read at run time, what was given to the engines and why, and what was left out or could not be read.
• ShippedFor every cited Florida section, five separate checks — source exists, quote matches, authority exists, treatment, applies — never merged into one verdict.
• ShippedEvery quotation in a result matched against the inputs and the cited statutes; the document parts no engine reached (a dual run's shared omissions), beside each engine's own result.
• ShippedInstruction-like text found inside a document is named and treated as content; every engine is told first that document text is data, never instructions.

Limits

• The five checks cover Florida statute sections in the corpus; applicability is a date check against the matter's recorded operative date, and whether a law governs the matter remains the attorney's judgment.
• Quotations shorter than 25 characters are not checked; parts are the document's headed articles or sections, else its paragraphs.
• The instruction scan is pattern-based and names what it finds; it is not exhaustive.
• A stored manifest is re-checked against the reader's access when it is read back; a document the reader can no longer read is withheld.

What EstateDraftFL refuses

Evidence

• src/lib/workspace/coverage-manifest.ts
• src/lib/workspace/coverage-manifest-server.ts
• src/app/api/admin/workspace/run/route.ts
• docs/security/MASTER-PLAN-PHASE7-2026-09-25.md

Last reviewed 2026-09-25