Site map

Explore AIR.

Enter through the question you actually have: start using AIR, understand how it operates, apply it to real work, inspect what its evidence can support, or learn about VM4AI.

Start Understand AIR Use AIR Trust & evidence VM4AI

01 · Start

I want to use AIR.

Boot a project, see a real AIR session, then keep the reference material nearby.

Get startedThe shortest path from the current foundation to a bound AIR project.→See a real AIR sessionInspect a preserved historical session from boot through project framing and Handoff.→AIR technical referenceLook up routing, MII, objects, binding, action governance, verification, capability layers, evidence, Handoff, and compatibility.→Glossary & modifiersTranslate AIR terminology and the four canonical system modifiers into plain language.→

Suggested path: Get started → real AIR session → reference as needed

02 · Understand

I want to understand what AIR is.

Start with the operating model, then place AIR in the wider AI tooling landscape.

How AIR worksContext, current alignment, task-selected cognition, one execution center, verification, the assurance boundary, and Handoff.→Where AIR fitsRaw chat, SDD harnesses, agentic engineering environments, agent runtimes, and governed execution.→AIR technical referenceMove from the conceptual model into current runtime and governance detail.→Glossary & modifiersLook up AIR-specific terms without reading the canonical source files end to end.→

Suggested path: How AIR works → Where AIR fits → reference when needed

03 · Use

I want to apply AIR to real work.

Start with the fit question, or go directly into the software-development path.

Use casesWhere AIR earns its overhead across development, research, writing, brand, strategy, recovery, and mixed-discipline projects.→AIR for software developmentThe practical workflow: task binding, responsibility split, implementation, evidence, and Handoff.→Spec-driven development with AIRWhy AIR is SDD-native for software work without being a coding-only framework.→Specification-First VerificationBehavior specification, verification specification, adequacy, execution, and reconciliation.→

Software path: AIR for Development → SDD → Specification-First Verification

04 · Trust & evidence

I want to know what I can rely on.

Start with the claim-to-evidence boundary, then inspect conformance and observed cases.

Testing & EvidenceWhich evidence supports which claim, plus a separate view of behavioral evaluation and release-integrity checks.→AIR load integrityHow to distinguish a conformant AIR boot/runtime surface from AIR-looking prose.→Built with AIRHow AIR's own brand and website were developed under the framework.→Recovered with AIRObserved project-state reconstruction after unplanned session failure, with the limits made explicit.→Made with AIRThe provenance surface for projects that genuinely used AIR in their workflow.→

Suggested path: Testing & Evidence → Load integrity → observed cases

05 · VM4AI

I want the project and company context.

Follow AIR's design lineage, the person and principles behind VM4AI, current writing, services, or the public source itself.

From Morphic to AIRThe historical design lineage and the decisions that shaped the current framework.→About VM4AIEdward Levin, why AIR exists, the principles behind it, and how to get in touch.→BlogCase studies, technical thinking, origin notes, and project updates.→ServicesWays to work with VM4AI directly on setup, enablement, capability, recovery, or sustained delivery.→AIR Kit on GitHubInspect the public Foundation, Specialist packages, release catalogs, and distribution-integrity workflow.↗

Suggested path: About / From Morphic to AIR → Blog or GitHub → Services when useful

One system, several entry points

This map is navigation, not another AIR layer. The pages deliberately own different questions so you do not have to learn the whole framework before finding the part you need.