TL;DR. A general partner cannot manually interrogate 2,000 inbound decks per year. The askOdin Diligence Protocol replaces three weeks of analyst cross-referencing with a deterministic compile pass that returns a Clarity Score, a brittle-assumption inventory, and an IC-ready memo — backed by a Defensible Audit Log suitable for LP and regulatory review. This playbook walks a partner through the protocol, end to end.
1. The Operating Reality of Modern Venture
A two-partner fund processing 2,000 inbound decks per year reviews fewer than fifty in depth. The other ninety-seven percent are triaged on signal proxies — logo, warm intro, sector pattern-match — not physics. Generative AI has now flooded that surface area with synthetic polish: every founder ships a flawless deck. The signal-to-noise ratio has collapsed.
The traditional response — hire more analysts — does not scale linearly with deal volume. The structural response is to compile every inbound deck deterministically.
2. Where the RUNE Protocol Fits
The RUNE Protocol™ is the askOdin judgment compiler — a patent-pending engine (U.S. Provisional Patent No. 63/948,559) that ingests a pitch deck and compiles it against the Judgment Graph™, a corpus of 50,000+ outcome-labeled venture narratives spanning Seed to Series B. RUNE does not summarize. It interrogates each claim against business physics and returns deterministic findings.
The output is a Clarity Score (0–100) across four axes:
- Story Quality — logical consistency between claims.
- Market Evidence — provenance of stated metrics.
- Unit Economics — financial viability at scale.
- Team Signal — domain-specific execution capability.
When a structural contradiction is detected, the score floors at zero. This is the Kill Shot mechanism. It is a feature, not a bug — it saves a partner from underwriting a thesis that mathematics will not support.
3. The Two-Hour Diligence Workflow
The protocol below assumes a partner has received a deck inbound and has not yet committed to a first call.
3.1 Compile the deck (3 minutes)
Upload the PDF or PPTX. RUNE ingests and compiles. The Clarity Score arrives with the brittle-assumption inventory, predicted investor objections, and evidence trail per finding.
3.2 Read the Score Card (15 minutes)
Read the four-axis breakdown. Note any axis below 50 — that is a structural concern, not a polish issue. Read the brittle-assumption list. These are the questions the partner should ask on the first call.
3.3 Cross-reference the data room (45 minutes, when available)
If the founder has shared a data room, escalate to the RAVEN Protocol for cross-document triangulation. Pitch deck, financial model, cap table, and term sheet are processed as a single logic graph. Contradictions across documents — revenue claimed in the deck that does not reconcile to the model, leases inconsistent with operating cost — surface as deterministic findings. See the WeWork S-1 Terminal Audit for a worked example of a FATAL XDOC-001 cross-document delta.
3.4 Run the JUDGE check (5 minutes)
The JUDGE Protocol (U.S. Prov. Patent No. 64/017,488; IPOS §34 cleared 2026-03-26) is the runtime circuit breaker for governance and structural-conflict signals. It floors the Clarity Score to zero when cap-table commingling, governance vacuum, or structural conflict is detected. See the FTX Terminal Audit for the canonical worked example.
3.5 Generate the IC memo (15 minutes)
The Clarity platform formats the compiled findings into an IC-ready memo. Every recommendation cites the underlying evidence. Export to .docx or .pdf. Total time from deck-in to memo-out: under two hours.
4. The Defensible Audit Log
Every deal compiled through the askOdin stack generates a Defensible Audit Log™ — a permanent, citation-grade record of the score, the findings, and the evidence trail. As the standard of fiduciary care evolves into the AI era, this artifact is what survives an LP review or regulatory inquiry. “Gut feel” no longer terminates the question.
This is the audit layer venture capital has lacked for forty years. Credit has Moody’s. Public markets have GAAP. Private capital has the Defensible Audit Log.
5. What This Replaces
| Legacy workflow | askOdin Diligence Protocol |
|---|---|
| Three weeks of analyst cross-referencing | Three minutes of RUNE compile + 60 minutes of partner review |
| IC memo authored from notes | Memo generated from compiled evidence |
| ”Gut feel” recorded as conviction | Defensible Audit Log per deal |
| Triage on warm intro / logo proxy | Triage on Dual Score Protocol (Clarity + Severity) |
| Kill Shots discovered post-deployment | Kill Shots flagged at compile-time |
6. Where to Start
A new fund typically pilots the protocol on the previous quarter’s pipeline. Compile every deck the fund passed on; compile every deck the fund funded. The pattern recognition surfaces immediately — most passes correlate with a structural finding the partner intuited but could not yet articulate; most funded deals show the brittle-assumption set the partner already plans to mitigate.
Once calibrated, the protocol moves into the live pipeline.
Adjacent Resources
- Solutions: AI for VC Due Diligence — the executive overview.
- Clarity for Funds — the enterprise platform.
- Terminal Audit: WeWork S-1 (RAVEN) — cross-document forensics in action.
- Architecture & IP Registry — the full protocol stack.
Venture capital is the last unaudited asset class. askOdin provides the infrastructure to close the gap.