The .0n Standard
The universal configuration format for AI orchestration. Like .env for environment variables, .0n is for AI config. One format. Every client. Zero fragmentation.
Every revolution starts with a standard format.
The best infrastructure is invisible. Just like .git made version control universal, .0n makes AI orchestration config portable and universal.
Version Control
Standardized how code is tracked, branched, and shared. Before Git, every team had their own system.
Environment Config
Standardized how apps read configuration. One file, every framework, every language.
AI Orchestration
Standardizes how AI tools are configured, connected, and automated. One format, every client.
Everything lives in ~/.0n/
A single directory on your machine holds all your AI orchestration configuration. Portable. Sharable. Version-controllable.
~/.0n/ ├── config.json # Global settings ├── connections/ # Service credentials │ ├── stripe.0n │ ├── slack.0n │ └── openai.0n ├── workflows/ # Automation definitions │ └── invoice-notify.0n ├── snapshots/ # System state captures │ └── crm-setup.0n ├── history/ # Execution logs └── cache/ # Response cache
Five types. One header. Infinite possibilities.
Every .0n file starts with a standard $0n header that declares its type, version, and name.
| Type | Purpose | Example |
|---|---|---|
| connection | Service credentials and authentication. Store API keys, OAuth tokens, and connection settings. | stripe.0n |
| workflow | Multi-step automations. Define inputs, steps with service calls, and output mappings. | invoice-notify.0n |
| snapshot | System state captures. Export your entire CRM setup, pipeline config, or service state. | crm-setup.0n |
| execution | Task run history. JSONL logs of every workflow execution with timestamps and results. | 2026-02-11.jsonl |
| config | Global settings. AI provider, default service preferences, rate limits. | config.json |
Dynamic values with double-brace templates
Reference inputs, step outputs, environment variables, and built-in values. Resolution order: system > launch > inputs > step.output.
Before .0n, configuration was chaos
Every orchestrator invented its own format. Credentials were scattered. Workflows were trapped.
| Problem | .0n Solution |
|---|---|
| Every orchestrator invents its own config format | One standard format for all |
| Credentials scattered across .env, JSON, YAML | ~/.0n/connections/ -- one place |
| Workflows trapped in proprietary tools | Portable .0n workflow files |
| No execution history standard | ~/.0n/history/ -- JSONL by date |
| System configs cannot be shared or exported | Shareable snapshots with .0n format |
| Different config format per MCP client | Write once, deploy everywhere |
Start using the .0n Standard today.
Install the spec package to validate .0n files, or install 0nMCP to start orchestrating immediately.