AIOC

aioc is a TypeScript SDK for agent systems where models can propose actions, but deterministic runtime components decide what is actually allowed to happen.

It is designed for applications that must retain full governance control over persistence, tracing, approval, and oversight concerns, instead of inheriting those decisions from the SDK.

Status

aioc is stable as of 0.1.0.

The current documentation mixes:

• stable runtime behavior you can use today
• draft RFC material for approval lifecycle and stabilization work that is still evolving

Stable Scope

aioc 0.1.0 stabilizes the governance-first runtime model as a dependable foundation for high-accountability applications: core APIs are compatibility-managed, audit artifacts and replay workflows are dependable, and the project has been validated through real implementation use.

Install

npm install @axiastudio/aioc

What You Get Today

• deterministic policy gates for tools and handoffs
• RunRecord audit artifacts with prompt snapshots and request fingerprints
• replay and comparison utilities for non-regression analysis
• provider setup helpers for Mistral and OpenAI

Technical Focus

The project currently focuses on three technical areas:

• controlled execution through policy gates for tools and handoffs
• structured auditability through RunRecord, prompt snapshots, and request fingerprints
• verifiable iteration through replay and comparison utilities

What This Site Covers

• a concise technical introduction to the runtime model
• the key public concepts you need to build with aioc
• a compact manual reference for the most important public APIs
• run-record and governance-oriented documentation in a navigable format

Source of Truth

The normative governance documents remain in the repository root under /docs.

This site is a documentation app living in /apps/aioc-docs and imports those documents into a browsable Starlight site.

Where To Go Next

• Start with Quickstart for the minimal setup path.
• Read Governance-First Design for the design position behind the runtime.
• Use Reference for the current public runtime surface.
• Use Run Records if you are evaluating auditability, replay, and regression workflows.
• Use Governance for RFCs, contracts, and privacy baseline documents.