Documentation · public · Apache 2.0

Read everything. No NDA. No signup.

Six documents, one reading-order guide per audience. Same posture as the 50 public ADRs, the Apache 2.0 verifier, and the open SDK. The substrate's pitch is "verify, don't trust" — gating the sales collateral while open-sourcing the architecture would be a contradiction.

Pick your audience · we'll order the reads

Six docs. Different reader, different order.

VP Product · Head of Platform · Staff Engineer with budget

45 min

  1. 01Solution brief — runtime-AI in regulated products
  2. 02Product datasheet
  3. 03Commercial datasheet

CTO · Staff Engineer · Platform Architect

90 min

  1. 01Technical architecture overview
  2. 02Security & compliance brief

CISO · Security Architect · Third-party audit firm

60 min

  1. 01Security & compliance brief
  2. 02Technical architecture overview

Procurement · Finance · GC (contract review)

20 min

  1. 01Commercial datasheet
  2. 02Product datasheet

VP Sales · Product strategy (vendor benchmark)

20 min

  1. 01Competitive positioning
  2. 02Solution brief — runtime-AI in regulated products

The full set

Each document targets one reader with one decision.

Product datasheet

2 pages · ~15 min

For: CEO · CISO · GC · Head of AI

Executive 1-pager every senior decision-maker reads first. What it is, what it solves, what ships today, key facts a CISO needs to greenlight a deeper conversation.

/docs/product-datasheetRead →

Solution brief — runtime-AI in regulated products

6 pages · ~30 min

For: VP Product · Head of Platform · Staff Engineer with budget

The buyer narrative. Walks through why the existing vendor stack doesn't close the gap, what the substrate does, the three reference deployments, the 90-day pilot path, the four operational properties an operator gains, the five-question evaluation framework, common misconceptions.

/docs/solution-briefRead →

Technical architecture overview

8 pages · ~60 min

For: CTO · Staff Engineer · Platform Architect

CTO-grade technical depth. The L1–L12 commitment stack, the runtime-AI primitive, the L12 entry shape, the verification surface, cross-language byte parity, performance characteristics, deployment topologies, the eight reliability mechanisms, failure modes, SDK ergonomics. Includes 'Open questions for your team' for technical-fit interviews.

/docs/technical-architectureRead →

Security & compliance brief

6 pages · ~30 min

For: CISO · Security Architect · Third-party audit firm

CISO + audit-firm review packet. Threat model, cryptographic primitives, key custody, filesystem hardening, regulatory mapping (GDPR + AI Act + DORA + NIS 2 + PSD3 article-by-article), security-review pre-answers, audit checklist, sub-processors + data flow, vulnerability disclosure process.

/docs/security-briefRead →

Commercial datasheet

3 pages · ~20 min

For: Procurement · Finance · GC

Procurement + finance reference. Pricing tiers at a glance, what each commercial tier includes, contract terms (renewal, termination, governing law, liability cap), SLA matrix, professional services rate card, 3-year total-cost-of-ownership model, pricing-protection commitments, procurement-friendly facts.

/docs/commercial-datasheetRead →

Competitive positioning

3 pages · ~20 min

For: VP Sales · Product strategy · prospective operators running vendor benchmarks

Sales-engineering reference. Category map of 16 adjacent vendors (Vanta, Drata, OneTrust, Credo AI, Fiddler, Lakera, Robust Intelligence, Calypso AI, LangChain, LangSmith, Vellum, Humanloop, LlamaIndex, Glean) with structured comparison across seven dimensions. Head-to-head detail per vendor. When to pick the substrate; when to pick something else. AI-vendor channel pitch.

/docs/competitive-positioningRead →

Why public, not on-request

  • · /pricing already publishes every tier price.
  • · /licensing explicitly lists "all 50 ADRs + public docs" as part of the Open tier.
  • · The verifier (verify.mjs) and the Python port (runtime-ai-py) are Apache 2.0 today. Gating sales collateral while open-sourcing the architecture would be a contradiction.
  • · "Verify, don't trust." If we disappear, the chain, the verifier, the architecture docs all outlive us. The product docs should too.