TL;DR. Single-document review cannot catch the contradictions that destroy private-market deals. The contradictions live between documents — exactly where manual review fragments. The askOdin RAVEN Protocol (U.S. Provisional Patent No. 63/994,876) reads the documents you upload from the data room as a single logic graph and surfaces cross-document deltas as citation-backed findings. This playbook is the operating manual for PE and M&A teams. Read the scope in section 5 first: this is pre-LOI triage, not a QoE.
1. The Data Room Is Adversarial by Design
Every artifact in a data room serves a purpose:
- The CIM is built to be persuasive.
- The financial model is built to defend the CIM.
- The disclosure schedules are built to cover the financial model.
This is not a moral observation. It is a structural one. The documents are produced by different parties, optimized for different audiences, and reviewed by different specialists. The contradictions live in the seams — and the seams are exactly where manual review fragments across associates, vendors, and counsel.
2. What the RAVEN Protocol Does
RAVEN ingests heterogeneous documents and processes them as a single, queryable logic graph. Every claim is mapped to its supporting evidence; every supporting evidence is mapped back to its source document. Contradictions across documents are surfaced as deterministic findings, each with originating citations.
The classic worked example is the WeWork S-1 Terminal Audit. RAVEN cross-referenced the pitch summary against the S-1 financials and surfaced the FATAL XDOC-001 delta — a 120% magnitude divergence between narrative TAM and reconciled reality — in under three minutes. A single-document review of either artifact would have confirmed what the artifact claimed. The contradiction lived in the cross-reference.
3. The Four Structural Signatures RAVEN Surfaces
3.1 Duration Mismatch
Long-term, fixed-cost liabilities (commercial leases, vendor contracts, take-or-pay agreements) backing short-term, highly volatile revenue (month-to-month, cancellable, consumption-based). The structural signature behind the WeWork collapse. RAVEN reconciles the lease schedule against the revenue mix and flags the divergence.
3.2 Revenue Reconciliation Failure
Deck-stated ARR versus financial-model bookings versus the revenue in the financial statements. When the three diverge, the deal team sees it before the IC. The “Ghost Revenue” pattern — “Booked but not Billed” entries treated as committed contracts — is among the most common findings in growth-stage SaaS audits.
3.3 Cap-Table Commingling
Entity-level cap tables that do not reconcile with stated post-money, or capital flows between affiliated entities that the operating narrative claimed were bilateral and segregated. The structural signature behind the FTX collapse. See the FTX Terminal Audit for the canonical worked example, and the JUDGE Protocol for the runtime circuit-breaker that floors the Clarity Score on detection.
3.4 Unit-Economic Mirage
SaaS multiples applied to service-tier unit economics. RAVEN flags the structural mispricing before it propagates into the LBO model. The cost-of-revenue line and the gross-margin line do not lie; the framing layered on top of them often does.
4. The Data Room Audit Workflow
4.1 Upload the documents
Upload the CIM and the documents supplied with it — the financial model, the financial statements, the disclosure schedules. Files are uploaded for each audit; there is no data-room connector or integration to set up. RAVEN parses each artifact, normalizes the schema, and constructs the logic graph.
4.2 Compile (under three minutes per audit)
The protocol cross-references every claim across the documents uploaded. Where a document the check needs is missing, the finding is reported as unverifiable rather than skipped.
4.3 Triage by severity
Findings are tiered Critical, Major, or Minor by the JUDGE Protocol inside Clarity. Critical findings — structural insolvency, cap-table commingling, duration mismatch beyond a configurable threshold — halt the workflow. Major findings populate the IC memo. Minor findings populate the back-of-memo appendix.
4.4 Generate the Defensible Audit Log
Every audit produces a Defensible Audit Log™ — the citation-grade record that survives a partner review, an LP inquiry, or a regulatory examination. This artifact is the durable institutional output.
5. What This Replaces
| Legacy workflow | RAVEN data-room audit |
|---|---|
| Multiple specialists cross-referencing 2–3 weeks | Single compile pass, under three minutes per audit |
| Inconsistent finding format across vendors | Normalized findings with severity tags |
| Cross-document contradictions surface during quality of earnings | Cross-document contradictions surface at compile-time |
| Memo built from analyst notes | Memo built from compiled evidence trail |
What it does not replace is the quality of earnings. Clarity is pre-LOI triage: it tests whether the CIM’s claims survive the documents supplied with it. It produces no QoE report, and it does no ledger or trial-balance reconciliation, proof of cash or working-capital peg work — that stays with your accountants and the QoE provider. The engine’s published record is on pitch decks and public filings; on CIMs it runs as a scoped pilot. See how a scoped pilot runs.
6. A Note on Intent
RAVEN does not allege intent. It surfaces structural contradictions. The mathematical signature that frequently precedes a fraud finding is the same signature that frequently precedes an aggressive-but-honest accounting interpretation. Whether the underlying cause is intent or error is a question for the deal team, counsel, and forensic accountants to resolve. The Defensible Audit Log preserves the trail so the right experts have the right evidence.
Adjacent Resources
- Solutions: AI Data Room Analysis for PE & M&A — the executive overview.
- Terminal Audit: WeWork S-1 (RAVEN flagship) — FATAL XDOC-001 worked example.
- Terminal Audit: FTX (JUDGE) — cap-table commingling worked example.
- Architecture & IP Registry — the full protocol stack.
Math does not change based on valuation, sovereign jurisdiction, or institutional FOMO.