0n-spec 1.0.0

package/LICENSE

@@ -0,0 +1,55 @@
+Creative Commons Attribution 4.0 International License (CC BY 4.0)
+
+Copyright (c) 2025 0nORK
+
+This work is licensed under the Creative Commons Attribution 4.0 International License.
+
+You are free to:
+
+  Share — copy and redistribute the material in any medium or format
+  Adapt — remix, transform, and build upon the material for any purpose, 
+          even commercially
+
+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

package/README.md

@@ -0,0 +1,301 @@
+<p align="center">
+  <img src="https://0nork.com/0n-logo.svg" alt=".0n" width="120" />
+</p>
+
+<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>
+
+---
+
+## What is .0n?
+
+`.0n` (pronounced "dot-on") is a specification for AI-powered orchestration configuration.
+
+It defines:
+- **`~/.0n/`** — The universal config directory
+- **`.0n` files** — Connection, workflow, and snapshot definitions
+- **Templates** — Variable interpolation syntax
+- **Schemas** — JSON schemas for validation
+
+**The Philosophy**: "Turn it on. It just works."
+
+---
+
+## The ~/.0n Directory
+
+```
+~/.0n/
+├── config.json           # Global settings
+├── connections/          # Service credentials
+│   ├── stripe.0n
+│   ├── slack.0n
+│   └── ...
+├── workflows/            # Automation definitions
+│   ├── invoice-flow.0n
+│   └── ...
+├── snapshots/            # System state captures
+├── 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`)
+
+```json
+{
+  "$0n": {
+    "type": "connection",
+    "version": "1.0.0",
+    "name": "Production Stripe"
+  },
+  "service": "stripe",
+  "environment": "production",
+  "auth": {
+    "type": "api_key",
+    "credentials": {
+      "api_key": "{{env.STRIPE_SECRET_KEY}}"
+    }
+  }
+}
+```
+
+### Workflow File (`~/.0n/workflows/invoice-notify.0n`)
+
+```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}}"
+      }
+    }
+  ]
+}
+```
+
+---
+
+## Implementations
+
+### Official
+
+| Product | Description | Status |
+|---------|-------------|--------|
+| [0nMCP](https://github.com/0nork/0nmcp) | Universal AI API Orchestrator | ✅ Production |
+
+### Community
+
+*Want to build a .0n-compliant tool? [Open an issue](https://github.com/0nork/0n-spec/issues) to be listed!*
+
+---
+
+## Specification
+
+📖 **[Read the full specification →](./SPEC.md)**
+
+The spec covers:
+- Directory structure
+- File formats
+- JSON schemas
+- Template syntax
+- Security guidelines
+- Conformance testing
+
+---
+
+## Validation
+
+### CLI Tool (Coming Soon)
+
+```bash
+# Install
+npm install -g 0n-spec
+
+# Validate a file
+0n validate my-workflow.0n
+
+# Validate entire config
+0n validate ~/.0n/
+
+# Run conformance tests
+0n test
+```
+
+### Programmatic
+
+```typescript
+import { validate } from '0n-spec';
+
+const result = validate('./my-workflow.0n');
+if (!result.valid) {
+  console.error(result.errors);
+}
+```
+
+---
+
+## JSON Schemas
+
+Schemas for editor autocompletion and validation:
+
+```json
+{
+  "$schema": "https://0nork.com/schemas/workflow.json"
+}
+```
+
+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`
+
+---
+
+## Why .0n?
+
+### The Name
+
+- **0n** = "On" = Turn it on
+- **0** = Zero friction
+- **n** = N possibilities
+
+### The Vision
+
+Every AI tool, every orchestration platform, every automation system — all speaking the same language. One config directory. One file format. Universal interoperability.
+
+```
+~/.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
+```
+
+**Write once. Orchestrate anywhere.**
+
+---
+
+## Contributing
+
+We welcome contributions to the .0n specification!
+
+### How to Contribute
+
+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
+
+### Guidelines
+
+- Backward compatibility is critical
+- Keep the spec simple and readable
+- Include examples for new features
+- Consider security implications
+
+---
+
+## Governance
+
+The .0n specification is maintained by [0nORK](https://0nork.com).
+
+### Versioning
+
+We follow [Semantic Versioning](https://semver.org/):
+- **MAJOR**: Breaking changes
+- **MINOR**: New features (backward compatible)
+- **PATCH**: Clarifications and fixes
+
+### RFC Process
+
+Major changes go through an RFC process:
+1. Create RFC document
+2. 2-week comment period
+3. Maintainer decision
+4. Implementation
+
+---
+
+## License
+
+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
+
+---
+
+## Links
+
+- **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)
+
+---
+
+<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>