How to Read These Docs

This documentation is structured for precision. Here's how to navigate it effectively.

Documentation Principles

1. Precision Over Marketing

Every claim is verifiable. Every guarantee has an enforcement mechanism. We don't make statements we can't prove.

2. Show, Don't Tell

Code examples are executable. Diagrams represent actual system behavior. When we say something works a certain way, we show you how.

3. Failure Is Documented

We document what happens when things break. Every capability has a corresponding failure mode. See Incident Posture for the full failure playbook.

Reading Paths

Choose your path based on your role and goal:

Evaluator Path (2-3 hours)

You're considering ΔOS and need to understand what it does.

1. What is ΔOS? — Core concept
2. What ΔOS Is Not — Category boundaries
3. Guarantees — What we actually promise
4. Intent — The fundamental unit
5. Authority Boundaries — Who decides what

Developer Path (4-6 hours)

You're integrating ΔOS into your agent infrastructure.

1. Developer Quickstart — Get running
2. SDK Reference — API details
3. Intent — Understand the model
4. LIMs — Policy evaluation
5. Architecture: Components — System design

Security/Compliance Path (3-4 hours)

You need to assess ΔOS for your security and compliance requirements.

1. Guarantees — Security-relevant properties
2. Authority Boundaries — Control model
3. Audit Trail — Immutability and verification
4. Incident Posture — Failure handling
5. Data Handling — Data flow and retention

Section Overview

Overview

Start here. Understand what ΔOS is, what it isn't, and how to evaluate it.

Concepts

Core abstractions: Intent, LIMs, Evidence, Judgments. Read these to understand the model.

Architecture

System design: Components, data flow, audit trail, integration patterns. Read these to understand how it's built.

Developers

Integration guides, SDK reference, examples. Read these to build with ΔOS.

Models

Value attribution, measurement methodology, confidence bands. Read these to understand how we quantify impact.

Governance

Guarantees, incident posture, SLOs, billing mappings. Read these to understand operational commitments.

Glossary

Precise term definitions. Reference when terminology is unclear.

Callout Types

We use callouts to highlight important information:

Component Types

Guarantees Table

Shows properties with their enforcement mechanisms and verification methods.

Truth Table

Compares capabilities or properties across categories.

Authority Boundary Diagram

Shows the separation of responsibilities between humans, the system, and LIMs.

Failure Narrative

Documents what happens during specific failure scenarios with capability status and recovery paths.

Finding Information

Search

Use the search bar to find specific terms or concepts.

Glossary

Every domain-specific term has a definition in the glossary. When you see unfamiliar terminology, check there first.

Cross-References

Pages link to related content. Follow these links to build complete understanding.

Feedback

If something is unclear, missing, or incorrect:

1. Check if there's a related page that addresses your question
2. Check the glossary for term definitions
3. If documentation is genuinely unclear, that's a bug—let us know

We maintain these docs as a source of truth. Accuracy matters.