Using Exit Protocol

Document & Evidence Review

Transcribing fragmented PDF bank statements is a common review bottleneck. Exit Protocol attempts native PDF extraction first and can use configured OCR paths to produce candidate rows for human review.

• Upload Discovery Files
  Navigate to the Evidence Vault and upload only a supported document you are authorized to process. Degraded or scanned pages may require configured OCR, provider consent where applicable, and manual reconciliation.
• Integrity Reference
  Upon upload, the system records a SHA-256 integrity reference for the received bytes. A later hash comparison can detect byte changes; the hash does not authenticate origin, prove completeness, or establish legal chain of custody by itself.
• Candidate Row Extraction
  Native PDF extraction runs first. A configured OCR path may attempt to identify candidate dates, descriptions, and amounts from scanned pages. Candidate rows are not final transactions and must be reviewed against the source page before import.

Reviewed Financial Foundation

Financial extraction candidates require review before they become ledger records. Reviewed StatementPeriod records then qualify represented coverage, gaps, overlaps, continuity, and reconciliation context without claiming discovery completeness.

• Review Financial Rows
  Confirm candidate dates, descriptions, amounts, balances, account identity, and source relationships before approval. Automated extraction does not create authoritative financial facts.
• Review Statement Periods and Coverage
  Confirm represented periods, gaps, overlaps, continuity, and reconciliation state for the selected account. Coverage qualifies the represented record; it does not prove disclosure sufficiency.
• Inspect Source Relationships
  Use authorized source drill-down to compare reviewed ledger rows with their Evidence Anchors and exact source pages. Evidence access remains permission-scoped.

Transfer & Money Flow Review

TransferCandidates are system proposals. Only an explicit reviewer decision records a ReviewedTransfer, and Money Flow is a read-only projection of those reviewed relationships across represented accounts.

• Review Possible Relationships
  Compare candidate dates, amounts, directions, evidence support, and coverage qualifications. A proposal is not a reviewed movement.
• Record the Reviewer Decision
  Confirm supported outgoing and incoming legs, fees, split or merge structure, and exact Decimal conservation before the relationship becomes a ReviewedTransfer.
• Inspect Money Flow
  Use Graph, Table, or Split review to inspect reviewer-confirmed movements, coverage and reconciliation context, and authorized evidence drill-down. Money Flow does not determine source-value ancestry, ownership, purpose, concealment, or fraud.

Deterministic Analysis & Value Lineage

Use the analysis that fits the reviewed matter. LIBR remains a current single-claim workpaper method. Value Lineage separately conserves one explicitly modeled source inside one account and can reach an outgoing reviewed transfer boundary.

• Run Deterministic LIBR Where Appropriate
  Select an explicit source transaction and reviewed account rows, disclose calculation settings, and inspect the current single-claim workpaper and exact-file integrity reference.
• Build Explicit Value Lineage Where Appropriate
  Select one evidence-supported positive source, explicitly allocate analytical value, verify exact conservation, and finalize an immutable tracing run. A TraceLot is analytical value, not physically identifiable dollars. The run may reach an outgoing reviewed transfer boundary, but it creates no destination TraceLot and does not propagate source value into another account.

Account Safety Limitations

High-conflict matters can involve coercion or device surveillance. Interface behaviors do not replace a personal safety plan, device security, counsel guidance, or emergency services.