0n-spec 1.0.0 → 1.1.0

package/LICENSE

@@ -1,55 +1,26 @@
-Creative Commons Attribution 4.0 International License (CC BY 4.0)
+MIT License
 
-Copyright (c) 2025 0nORK
+Copyright (c) 2026 RocketOpp / 0nORK
 
-This work is licensed under the Creative Commons Attribution 4.0 International License.
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
 
-You are free to:
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
 
-  Share — copy and redistribute the material in any medium or format
-  Adapt — remix, transform, and build upon the material for any purpose, 
-          even commercially
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
 
-Under the following terms:
+---
 
-  Attribution — You must give appropriate credit, provide a link to the 
-                license, and indicate if changes were made. You may do so 
-                in any reasonable manner, but not in any way that suggests 
-                the licensor endorses you or your use.
-
-  No additional restrictions — You may not apply legal terms or technological 
-                               measures that legally restrict others from doing 
-                               anything the license permits.
-
-Notices:
-
-You do not have to comply with the license for elements of the material in 
-the public domain or where your use is permitted by an applicable exception 
-or limitation.
-
-No warranties are given. The license may not give you all of the permissions 
-necessary for your intended use. For example, other rights such as publicity, 
-privacy, or moral rights may limit how you use the material.
-
-───────────────────────────────────────────────────────────────────────────────
-
-Full license text: https://creativecommons.org/licenses/by/4.0/legalcode
-
-───────────────────────────────────────────────────────────────────────────────
-
-TRADEMARK NOTICE
-
-"0nORK", "0nMCP", ".0n", and "The .0n Standard" are trademarks of 0nORK.
-
-While this specification is freely usable under CC BY 4.0, the trademarks are 
-protected. This means:
-
-✓ You CAN create implementations of the .0n standard
-✓ You CAN describe your software as ".0n compliant" or ".0n compatible"
-✓ You CAN reference the specification
-
-✗ You CANNOT claim your implementation is "The .0n Standard"
-✗ You CANNOT use "0nORK" or "0nMCP" as product names
-✗ You CANNOT imply official endorsement without permission
-
-For trademark licensing: legal@0nork.com
+The .0n Specification (SPEC.md) is separately licensed under CC BY 4.0:
+https://creativecommons.org/licenses/by/4.0/

package/README.md

@@ -1,41 +1,32 @@
-<p align="center">
-  <img src="https://0nork.com/0n-logo.svg" alt=".0n" width="120" />
-</p>
+<div align="center">
 
-<h1 align="center">The .0n Standard</h1>
-
-<p align="center">
-  <strong>The universal configuration format for AI orchestration.</strong>
-</p>
-
-<p align="center">
-  <em>Like <code>.git</code> for version control. Like <code>.env</code> for config.<br/>
-  <code>.0n</code> is for AI orchestration.</em>
-</p>
-
-<p align="center">
-  <a href="https://github.com/0nork/0n-spec/blob/main/SPEC.md"><img src="https://img.shields.io/badge/spec-v1.0.0-blue.svg?style=flat-square" alt="spec version"></a>
-  <a href="https://creativecommons.org/licenses/by/4.0/"><img src="https://img.shields.io/badge/license-CC%20BY%204.0-green.svg?style=flat-square" alt="license"></a>
-  <a href="https://discord.gg/0nmcp"><img src="https://img.shields.io/discord/0000000000?style=flat-square&logo=discord&logoColor=white&label=discord&color=5865F2" alt="discord"></a>
-</p>
+```
+   ██████╗ ███╗   ██╗
+  ██╔═████╗████╗  ██║
+  ██║██╔██║██╔██╗ ██║
+  ████╔╝██║██║╚██╗██║
+  ╚██████╔╝██║ ╚████║
+   ╚═════╝ ╚═╝  ╚═══╝
+```
 
----
+# The .0n Standard
 
-## What is .0n?
+### The universal configuration format for AI orchestration.
 
-`.0n` (pronounced "dot-on") is a specification for AI-powered orchestration configuration.
+[![License: CC BY 4.0](https://img.shields.io/badge/License-CC%20BY%204.0-lightgrey.svg?style=flat-square)](https://creativecommons.org/licenses/by/4.0/)
+[![Version](https://img.shields.io/badge/version-1.0.0-blue?style=flat-square)](SPEC.md)
+[![Node.js](https://img.shields.io/badge/node-%3E%3D18.0.0-brightgreen?style=flat-square)](https://nodejs.org)
+[![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square)](http://makeapullrequest.com)
 
-It defines:
-- **`~/.0n/`** — The universal config directory
-- **`.0n` files** — Connection, workflow, and snapshot definitions
-- **Templates** — Variable interpolation syntax
-- **Schemas** — JSON schemas for validation
+[Specification](SPEC.md) · [Schemas](#schemas) · [Examples](#examples) · [CLI](#cli) · [Library](#library) · [0nMCP](https://github.com/0nork/0nMCP)
 
-**The Philosophy**: "Turn it on. It just works."
+</div>
 
 ---
 
-## The ~/.0n Directory
+## What is .0n?
+
+Just as `.git` revolutionized version control and `.env` standardized environment configuration, **`.0n`** establishes the universal standard for AI orchestration configuration.
 
 ```
 ~/.0n/
@@ -43,31 +34,16 @@ It defines:
 ├── connections/          # Service credentials
 │   ├── stripe.0n
 │   ├── slack.0n
-│   └── ...
+│   └── openai.0n
 ├── workflows/            # Automation definitions
-│   ├── invoice-flow.0n
-│   └── ...
+│   └── invoice-notify.0n
 ├── snapshots/            # System state captures
+│   └── crm-setup.0n
 ├── history/              # Execution logs
 └── cache/                # Response cache
 ```
 
----
-
-## File Types
-
-| Type | Purpose | Example |
-|------|---------|---------|
-| **Connection** | Service credentials | `stripe.0n` |
-| **Workflow** | Multi-step automation | `invoice-notify.0n` |
-| **Snapshot** | System state backup | `crm-setup.0n` |
-| **Execution** | Task run history | (auto-generated) |
-
----
-
-## Quick Example
-
-### Connection File (`~/.0n/connections/stripe.0n`)
+**Every `.0n` file has a standard header:**
 
 ```json
 {
@@ -77,194 +53,196 @@ It defines:
     "name": "Production Stripe"
   },
   "service": "stripe",
-  "environment": "production",
   "auth": {
     "type": "api_key",
-    "credentials": {
-      "api_key": "{{env.STRIPE_SECRET_KEY}}"
-    }
+    "credentials": { "api_key": "{{env.STRIPE_SECRET_KEY}}" }
   }
 }
 ```
 
-### Workflow File (`~/.0n/workflows/invoice-notify.0n`)
+**The philosophy: "Turn it on. It just works."**
 
-```json
-{
-  "$0n": {
-    "type": "workflow",
-    "version": "1.0.0",
-    "name": "Invoice and Notify"
-  },
-  "trigger": { "type": "manual" },
-  "inputs": {
-    "email": { "type": "string", "required": true },
-    "amount": { "type": "number", "required": true }
-  },
-  "steps": [
-    {
-      "id": "create_invoice",
-      "service": "stripe",
-      "action": "invoices.create",
-      "params": {
-        "customer_email": "{{inputs.email}}",
-        "amount": "{{inputs.amount * 100}}"
-      }
-    },
-    {
-      "id": "notify",
-      "service": "slack",
-      "action": "chat.postMessage",
-      "params": {
-        "channel": "#sales",
-        "text": "Invoice created for ${{inputs.amount}}"
-      }
-    }
-  ]
-}
-```
+---
+
+## Why .0n?
+
+| Problem | .0n Solution |
+|---------|-------------|
+| Every orchestrator invents its own config format | One standard format for all |
+| Credentials scattered across env files, 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 can't be shared | Shareable snapshots with `.0n` format |
 
 ---
 
-## Implementations
+## File Types
 
-### Official
+| Type | Purpose | Example |
+|------|---------|---------|
+| `connection` | Service credentials | `stripe.0n` |
+| `workflow` | Multi-step automations | `invoice-notify.0n` |
+| `snapshot` | System state capture | `crm-setup.0n` |
+| `execution` | Task run history | `2026-02-06.jsonl` |
+| `config` | Global settings | `config.json` |
 
-| Product | Description | Status |
-|---------|-------------|--------|
-| [0nMCP](https://github.com/0nork/0nmcp) | Universal AI API Orchestrator | ✅ Production |
+---
+
+## Schemas
 
-### Community
+JSON Schemas for validation:
 
-*Want to build a .0n-compliant tool? [Open an issue](https://github.com/0nork/0n-spec/issues) to be listed!*
+- [`schemas/config.json`](schemas/config.json) — Global configuration
+- [`schemas/connection.json`](schemas/connection.json) — Service connections
+- [`schemas/workflow.json`](schemas/workflow.json) — Workflow definitions
+- [`schemas/snapshot.json`](schemas/snapshot.json) — System snapshots
 
 ---
 
-## Specification
+## Examples
 
-📖 **[Read the full specification →](./SPEC.md)**
+Working examples of each file type:
 
-The spec covers:
-- Directory structure
-- File formats
-- JSON schemas
-- Template syntax
-- Security guidelines
-- Conformance testing
+- [`examples/config.0n`](examples/config.0n) — Global config with Anthropic provider
+- [`examples/stripe.0n`](examples/stripe.0n) — Stripe connection with env var credentials
+- [`examples/invoice-notify.0n`](examples/invoice-notify.0n) — 5-step workflow: find customer, create invoice, add line item, send, notify Slack
+- [`examples/crm-setup.0n`](examples/crm-setup.0n) — Full CRM snapshot with pipeline, 10 tags, custom fields, custom values, 3 workflows, email templates
 
 ---
 
-## Validation
+## CLI
+
+Initialize, validate, and test `.0n` files from the command line.
 
-### CLI Tool (Coming Soon)
+### Install
 
 ```bash
-# Install
 npm install -g 0n-spec
+```
+
+### Commands
 
-# Validate a file
+```bash
+# Initialize ~/.0n/ directory
+0n init
+
+# Validate a .0n file
 0n validate my-workflow.0n
 
-# Validate entire config
+# Validate entire directory
 0n validate ~/.0n/
 
-# Run conformance tests
+# Run conformance tests against examples
 0n test
 ```
 
-### Programmatic
+---
 
-```typescript
-import { validate } from '0n-spec';
+## Library
 
-const result = validate('./my-workflow.0n');
-if (!result.valid) {
-  console.error(result.errors);
-}
-```
+Use programmatically in Node.js:
 
----
+```javascript
+const { validate, parse, create, init, list, save } = require('0n-spec');
 
-## JSON Schemas
+// Validate a file
+const result = validate('my-workflow.0n');
+// { valid: true, type: 'workflow', version: '1.0.0', errors: [], warnings: [] }
 
-Schemas for editor autocompletion and validation:
+// Parse a .0n file
+const workflow = parse('~/.0n/workflows/invoice-notify.0n');
+// { type: 'workflow', name: 'Invoice and Notify', data: {...} }
 
-```json
-{
-  "$schema": "https://0nork.com/schemas/workflow.json"
-}
-```
+// Create a new .0n object
+const connection = create('connection', {
+  name: 'My Stripe',
+  service: 'stripe',
+  authType: 'api_key',
+  credentials: { api_key: '{{env.STRIPE_KEY}}' },
+});
 
-Available schemas:
-- `https://0nork.com/schemas/connection.json`
-- `https://0nork.com/schemas/workflow.json`
-- `https://0nork.com/schemas/snapshot.json`
-- `https://0nork.com/schemas/config.json`
+// Initialize ~/.0n/ directory
+init();
+
+// List all connections
+const connections = list('connection');
+
+// Save to file
+save(connection, '~/.0n/connections/stripe.0n');
+```
 
 ---
 
-## Why .0n?
+## Template Syntax
 
-### The Name
+The `.0n` standard uses double-brace templates:
 
-- **0n** = "On" = Turn it on
-- **0** = Zero friction
-- **n** = N possibilities
+| Syntax | Description |
+|--------|-------------|
+| `{{inputs.name}}` | Reference input parameter |
+| `{{step_id.output.field}}` | Reference step output |
+| `{{env.VAR_NAME}}` | Reference environment variable |
+| `{{now}}` | Current ISO timestamp |
+| `{{uuid}}` | Generate UUID |
 
-### The Vision
+---
 
-Every AI tool, every orchestration platform, every automation system — all speaking the same language. One config directory. One file format. Universal interoperability.
+## Implementations
 
-```
-~/.0n/          ← Your orchestration home
-├── stripe.0n   ← Works with 0nMCP
-├── stripe.0n   ← Works with Tool X
-├── stripe.0n   ← Works with Tool Y
-└── stripe.0n   ← Works with everything
-```
+| Product | Description | Status |
+|---------|-------------|--------|
+| [0nMCP](https://github.com/0nork/0nMCP) | Universal AI API Orchestrator — 535 tools, 26 services | Production |
+
+### Building a .0n Implementation
 
-**Write once. Orchestrate anywhere.**
+1. Use `~/.0n/` as the config directory
+2. Support the `$0n` header in all files
+3. Validate against the JSON schemas
+4. Pass conformance tests: `npx 0n-spec test`
 
 ---
 
-## Contributing
+## Community & Unlocks
 
-We welcome contributions to the .0n specification!
+The .0n Standard grows with the 0nMCP community. Every milestone unlocks new capabilities.
 
-### How to Contribute
+- **[0nmcp.com/community](https://0nmcp.com/community)** — Community hub
+- **[Unlock Schedule](https://0nmcp.com/sponsor)** — 7-phase roadmap from 535 to 5,000+ tools
+- [GitHub Discussions](https://github.com/0nork/0nMCP/discussions) — Questions and ideas
+- [Sponsor on GitHub](https://github.com/sponsors/0nork) — Fund the next unlock
 
-1. **Propose changes** — Open an issue with your proposal
-2. **Discuss** — Community feedback on the proposal
-3. **PR** — Submit changes to SPEC.md
-4. **Review** — Maintainer review and merge
+**Current:** Phase 0 — Foundation complete (535 tools, 26 services, 13 categories)
 
-### Guidelines
+---
 
-- Backward compatibility is critical
-- Keep the spec simple and readable
-- Include examples for new features
-- Consider security implications
+## The 0n Network
 
----
+The .0n Standard is part of the **0n Network** — an open ecosystem of AI-native tools.
 
-## Governance
+| | |
+|---|---|
+| **[RocketOpp](https://rocketopp.com)** | The agency behind the 0n Network. AI-powered systems that replace manual operations. |
+| **[Rocket+MCP](https://rocketadd.com)** | Universal control layer connecting AI agents to business tools. |
+| **[0n Network](https://github.com/0nork)** | Open-source AI orchestration infrastructure. |
 
-The .0n specification is maintained by [0nORK](https://0nork.com).
+---
 
-### Versioning
+## Contributing
 
-We follow [Semantic Versioning](https://semver.org/):
-- **MAJOR**: Breaking changes
-- **MINOR**: New features (backward compatible)
-- **PATCH**: Clarifications and fixes
+We want the .0n standard to become the **universal format** for AI orchestration config.
 
-### RFC Process
+**Ways to contribute:**
+- Propose schema improvements
+- Add example `.0n` files
+- Build a .0n-compliant implementation
+- Report issues or suggest features
+- Star the repo
 
-Major changes go through an RFC process:
-1. Create RFC document
-2. 2-week comment period
-3. Maintainer decision
-4. Implementation
+```bash
+git clone https://github.com/0nork/0n-spec.git
+cd 0n-spec
+npm test
+```
 
 ---
 
@@ -272,30 +250,20 @@ Major changes go through an RFC process:
 
 The .0n Specification is licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
 
-**You are free to:**
-- ✅ Use the spec in your products
-- ✅ Create implementations
-- ✅ Modify and extend (with attribution)
-- ✅ Commercial use
-
-**You must:**
-- Credit 0nORK as the spec creator
+The CLI and library code are licensed under [MIT](LICENSE).
 
 ---
 
-## Links
+<div align="center">
+
+### Turn it on. It just works.
 
-- **Website**: [0nork.com](https://0nork.com)
-- **0nMCP**: [github.com/0nork/0nmcp](https://github.com/0nork/0nmcp)
-- **Discord**: [discord.gg/0nmcp](https://discord.gg/0nmcp)
-- **Twitter**: [@0nmcp](https://twitter.com/0nmcp)
+**[Read the Spec](SPEC.md)** · **[Star this repo](https://github.com/0nork/0n-spec)** · **[Use 0nMCP](https://github.com/0nork/0nMCP)**
 
 ---
 
-<p align="center">
-  <strong>The .0n Standard</strong>
-  <br>
-  <em>Turn it on. It just works.</em>
-  <br><br>
-  <a href="https://0nork.com">0nORK — AI Orchestration Infrastructure</a>
-</p>
+Made with conviction by [RocketOpp](https://rocketopp.com) · [Rocket+MCP](https://rocketadd.com) · [0n Network](https://github.com/0nork)
+
+*"The best automation is the one you don't have to configure."*
+
+</div>