Codebase-grounded schematic for containerized deployment options and attorney-reviewable workflows. Use of the platform does not create or guarantee privilege.
Primary persistence layer ensuring relational integrity across highly complex entity resolution graphs and multi-year transaction ledgers.
Production Compose uses Redis for cache-backed throttling and optional background-task transport. This is not represented as complete DDoS mitigation or durable queueing.
The current worker supports selected background operations such as optional SIEM forwarding. Financial imports and LIBR task adapters execute synchronously and require capacity testing.
Codebase-grounded schematics for how public surfaces, authenticated processing, report generation, and verification relate in the V1 single-claim LIBR path.
Distinct zones separate educational public pages from authenticated ingestion, deterministic report generation, and byte-exact verification.
flowchart TB
subgraph Public["Public zone"]
PP[Conversion pages and /verify/]
SP[Synthetic sample workpapers]
end
subgraph Auth["Authenticated app"]
UI[Cases accounts and claims]
ING[Ingestion and normalization]
end
subgraph ClioZone["Clio integration"]
OAuth[OAuth tokens encrypted at rest]
SEL[User-selected matter and document]
REV[Local extraction review job]
end
subgraph Gen["Report generation"]
LIBR[Deterministic LIBR engine]
RPT[ForensicReport and PDF render]
HASH[file hash and snapshot digest]
end
subgraph Vault["Evidence Vault"]
ED[EvidenceDocument storage]
end
UI --> ING --> LIBR
OAuth --> SEL
SEL -->|read-only download| ING
LIBR --> RPT --> HASH
RPT --> ED
SEL --> REV
HASH --> PP
SP -.->|demo bytes may not verify| PP
What it provesPublic copy stays bounded while financial review happens in authenticated zones. Clio currently reads one selected source into a local review job. Verification is a separate public gate on exact file bytes.
What can breakEndorsement language crossing from Clio into public pages. Snapshot-only verification messaging. Silent bulk ingestion. Missing file hashes. LIBR or ledger inconsistency undermines every downstream zone.
Selected financial records become a single-claim attorney-reviewable workpaper with provenance and integrity surfaces.
flowchart LR
A[Selected account] --> T[Normalized transactions]
T --> C[SeparatePropertyClaim]
C --> S[Disclosed LIBR settings]
S --> L[LIBR calculation]
L --> SN[Snapshot SHA-256]
L --> FR[ForensicReport]
FR --> PDF[Attorney-reviewable PDF]
PDF --> EV[Evidence Vault copy]
PDF --> V["/verify/ exact file hash"]
SN -.->|printed on workpaper| PDF
What it provesV1 is one inspectable pipeline: calculation-setting disclosure, deterministic replay, stored file hash, and public verification anchored to PDF bytes — not narrative alone.
What can breakTransaction ordering errors. Calculation settings absent from the PDF face. Ledger disagreeing with summary. Vault copy diverging from ForensicReport bytes. Multi-claim exports through the default V1 path.
User uploads a bank PDF. RateLimitMiddleware applies configured cache-backed limits. CaseContextMiddleware provides case context while each view must still enforce object-level permissions.
The file routes to EvidenceDocument. The system records a SHA-256 integrity reference and applies application-layer authenticated encryption at rest. The hash can detect byte changes; it does not authenticate origin or establish legal chain of custody by itself.
Native PDF extraction runs first where possible. Configured local or cloud OCR may produce candidate rows for degraded pages, with explicit consent where external processing is used. Reconciliation and human review are required before import.
Specialized apportionment assumptions, when used, must be selected and validated by counsel or a qualified expert. The V1 public workpaper path does not make a legal characterization.
The V1 workpaper applies the selected LIBR calculation settings to reviewed ledger rows and explicit source provenance. Alternative tracing methods require separate validation and are not represented as equivalent legal conclusions.
A ForensicReport PDF is generated with disclosed calculation settings, selected ledger rows, provenance references, and final-file SHA-256 integrity reference. It is designed to support professional review and does not claim SSFS compliance.