askOdin — AI Judgment Infrastructure for Capital Allocation

Technical Registry  ·  Institutional IP Doctrine

Architecture & IP Registry

// THE askOdin PROTOCOL STACK

askOdin is not a software application. It is the verification layer that sits between the data room and the partner meeting.

Most AI tools wrap an LLM around the documents and summarize what was said. We separate extraction from evaluation. The LLM reads the messy human narrative; the core logic — patent-pending, deterministic, executed outside any probabilistic model — decides whether the math actually holds.

Four U.S. provisional patents and IPOS Section 34 clearance protect what does the deciding.

// The Deterministic Split

Extraction is LLM. Evaluation is Go. Separation is the audit trail.

Column 01 · The Trap

The Probabilistic Wrapper Trap

Standard AI diligence tools wrap an LLM around a data room and ask it to summarize the business. This is fundamentally flawed. Generative models are probabilistic; they are designed to applaud narrative fluency, not detect structural physics violations. They cannot be audited.

Column 02 · The Architecture

The askOdin Architecture

askOdin separates extraction from evaluation.

  1. 1. Extraction: We use isolated LLM layers strictly to parse unstructured text into structured, mathematical variables.
  2. 2. Evaluation: The RUNE Protocol™ takes over. RUNE operates like a deterministic chess or Go engine. It runs the structured variables through 40+ mathematical checkpoints, cross-referencing claims against our 780+ outcome-labeled benchmark universe.

The Audit Trail

Every claim parsed and evaluated generates a cryptographic per-claim hash. If an Investment Committee or LP challenges a Clarity Score™, we deterministically replay the compile step. The output is reconstructible, legally defensible, and IPOS Section 34 cleared.

The Protocol Stack

SYSTEM RUNE // LAYER 01

RUNE Protocol™

STATUS:[U.S. PROV. APP. NO. 63/948,559]
Layer
Domain-Specific Intermediate Representation Compiler
Function
The core interrogation protocol. RUNE strips unstructured financial narratives and translates them into a directed acyclic graph. It executes a 3-pass compilation (Syntax, Logical Physics, Regulatory Compliance) to automatically propagate "Brittleness Scores" and flag Compile-Time Errors before execution.
SYSTEM RAVEN // LAYER 02 SEALED

RAVEN Protocol™

STATUS:[U.S. PROV. APP. NO. 63/994,876]
Layer
Cross-Document Triangulation Engine
Function
The verification layer for heterogeneous data rooms. RAVEN cross-references claims across pitch decks, financial models, and supporting evidence to surface internal contradictions between documents — e.g., a narrative assertion in a PDF checked against the embedded formula in an Excel model.
Note
The architectural mechanics of RAVEN's triangulation engine are protected under U.S. Provisional Patent No. 63/994,876 and are not publicly disclosed. askOdin sells the verification, not the source code.
SYSTEM NORN // LAYER 03

NORN Protocol™

STATUS:[U.S. PROV. APP. NO. 64/011,252]
Layer
Temporal Semantic Drift Detector
Function
Chronological state tracking. NORN evaluates chronologically sequential documents to isolate the divergence between a "Presentation Score" (narrative assertion density) and a "Clarity Score" (structural logic integrity). It mathematically detects "Narrative Inflation" — when a founder's rhetoric escalates while their underlying business physics degrade.
SYSTEM JUDGE // LAYER 04

JUDGE Protocol™

STATUS:[U.S. PROV. APP. NO. 64/017,488] STATUS:[IPOS §34 NATIONAL SECURITY CLEARANCE]
Layer
Asymmetric Non-Parametric Calibrator & Runtime Circuit Breaker
Function
The deterministic immune system. LLMs optimize for persuasion; askOdin compiles for physics. If an underlying language model generates a novel probabilistic hallucination, JUDGE intercepts the payload, calculates an intra-document semantic delta, dynamically synthesizes a new logical constraint, and atomically hot-loads the rule into active memory. It permanently kills specific failures across all enterprise pipelines without requiring model fine-tuning.
Note
IPOS Section 34 clearance (issued March 26, 2026) establishes the JUDGE architecture as legally-vetted, sovereign-grade infrastructure.

Output Layer

The Defensible Audit Log™

Every deployment of the askOdin stack generates a mathematically traceable output. We do not issue probabilistic "recommendations." We issue a Defensible Audit Log that reconstructs the exact logic, precedent, and mathematical physics used to arrive at a judgment.

This is the standard of care required for modern fiduciary duty.

For Founders

Access Crucible

Run your deck through the same protocol stack an Investment Committee would require. Every audit generates a Defensible Audit Log.

Access Crucible

Aggregate View

Read the Q1 Macro Audit

The State of Venture Physics: Q1 2026. The protocol stack applied at scale across 60,000+ private market datasets.

Read the Q1 Macro Audit