GAAI Framework

GAAI — Governed Agentic AI Infrastructure

A .gaai/ folder you drop into any git project. Markdown, YAML and bash, with a vendored Python runtime and a few Node helpers. No SDK. No package to install. No external services.

GAAI turns AI coding tools into reliable agentic software delivery systems.

See It in Action

Two slash commands. Two isolated contexts. Discovery reasons — it never executes. Delivery executes — it never decides scope. They never share a context window — Delivery runs as a separate OS process (claude -p via tmux), so system prompts can't contaminate each other. The backlog is the contract between them.
/gaai-deliver delivers a single Story in the current session. /gaai-daemon launches a background daemon that polls the backlog and delivers multiple Stories in parallel (each in its own tmux session). See Delivery Daemon →
Full walkthrough in Quick Start

Why GAAI

AI coding tools are fast — but without governance, speed creates drift: agents touch code they shouldn't, forget decisions from prior sessions, and ship features no one can verify against criteria. GAAI adds the missing layer.

Built for developers who already have product clarity — solo founders, senior engineers, small teams who know what to build and need an agent that ships it reliably without going off-script. If you've ever said "the agent broke something it wasn't supposed to touch," this is for you.

How It Works

Discovery — you talk to the Discovery Agent in your current session. Clarify what to build. Output: a Story with acceptance criteria in the backlog. Discovery reasons. It does not execute.

Delivery — always runs in an isolated process. /gaai-daemon launches the Delivery Daemon, which runs each Story in its own claude -p session via tmux — a completely separate OS…