@oxgeneral/orch 1.0.0 → 1.0.1

package/readme.md

@@ -1,14 +1,14 @@
 <p align="center">
   <img src="assets/logo.svg" alt="ORCH" height="60" />
   <p align="center">
-    <strong>Stop babysitting AI agents. Start orchestrating them.</strong><br/>
-    One CLI to run Claude, OpenCode, Codex, Cursor, and shell scripts as a team — in parallel, with retries, from your terminal.
+    <strong>Open-source orchestration for zero-human companies, processes and departments.</strong><br/>
+    Engineering, editorial, sales, analytics — deploy entire AI departments from your terminal. Free forever.
   </p>
   <p align="center">
     <a href="https://github.com/oxgeneral/ORCH/stargazers"><img src="https://img.shields.io/github/stars/oxgeneral/ORCH?style=social" alt="GitHub Stars" /></a>
     <a href="https://www.orch.one/"><img src="https://img.shields.io/badge/website-orch.one-amber" alt="Website" /></a>
     <a href="https://www.npmjs.com/package/@oxgeneral/orch"><img src="https://img.shields.io/npm/v/@oxgeneral/orch?color=cb0000" alt="npm" /></a>
-    <a href="#get-started-in-30-seconds"><img src="https://img.shields.io/badge/setup-one%20command-brightgreen" alt="One command setup" /></a>
+    <a href="#launch-your-ai-company-in-30-seconds"><img src="https://img.shields.io/badge/setup-30%20seconds-brightgreen" alt="30 second setup" /></a>
     <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue" alt="MIT License" /></a>
     <a href="#development"><img src="https://img.shields.io/badge/tests-1493%20passing-brightgreen" alt="Tests" /></a>
     <a href="#architecture"><img src="https://img.shields.io/badge/TypeScript-strict-blue" alt="TypeScript strict" /></a>
@@ -21,118 +21,173 @@
   <video src="https://github.com/user-attachments/assets/c7c3ab77-e718-4e5a-a8cf-bfc446ace64e" width="100%" controls autoplay loop muted></video>
 </div>
 <p align="center">
-  <em>Real-time TUI dashboard: tasks running, agents working, activity streaming — all from one terminal.</em>
+  <em>Command center: engineering shipping code, editorial publishing content, QA testing — all at once, while you sleep.</em>
 </p>
 
 ---
 
-## You know the pain
+## You're still babysitting AI agents
 
 You have 3 AI assistants open. Claude is implementing auth in one terminal. Codex is writing tests in another. A shell script runs migrations somewhere else.
 
-You're the human router — switching tabs, copy-pasting context, manually tracking who's doing what, restarting crashed agents.
+You're the human router — switching tabs, copy-pasting context, manually tracking who's doing what, restarting crashed agents at 2am.
 
-**That's not engineering. That's babysitting.**
+**You're not the founder. You're the intern.**
 
-## What if your AI agents worked like a real team?
+## What if you had an entire AI department?
 
 ```
-$ orch run --all
-
-  orch · watching · 3 running · 0 queued
-
-  14:32  ▶ Backend A    → "Implement OAuth2 flow"
-  14:32  ▶ Backend B    → "Write API integration tests"
-  14:32  ▶ QA           → "Verify auth edge cases"
-  14:35  ✓ Backend B    DONE  (3m 12s · 4,200 tokens)
-  14:38  ✓ Backend A    DONE  (6m 44s · 8,100 tokens)
-  14:39  ↻ QA           RETRY  attempt 2 · found regression
-  14:41  ✓ QA           DONE  (2m 15s · 2,800 tokens)
+$ orch org deploy startup-mvp --goal "Implement user auth with OAuth2"
+
+  ✓ Deployed team "platform" — 5 agents
+    CTO (claude)       → Decomposing goal into tasks...
+    Backend A (claude)  → Waiting for tasks
+    Backend B (codex)   → Waiting for tasks
+    QA (codex)          → Waiting for tasks
+    Reviewer (claude)   → Waiting for reviews
+
+  ✓ CTO created 6 tasks from goal
+
+$ orch run --all --watch
+
+  22:03  ▶ Backend A    → "Implement OAuth2 flow"         [feature/oauth]
+  22:03  ▶ Backend B    → "JWT token service"              [feature/jwt]
+  22:03  ▶ QA           → waiting for implementations...
+  22:15  ✓ Backend B    DONE  (12m · 4,200 tokens)
+  22:15  ▶ QA           → "Test JWT service"               [test/jwt]
+  22:22  ✓ Backend A    DONE  (19m · 8,100 tokens)
+  22:24  ↻ QA           RETRY  attempt 2/3
+  22:28  ✓ QA           DONE  (6m · 2,800 tokens)
+  22:29  ▶ Reviewer     → "Review OAuth2 implementation"
+  22:33  ✓ Reviewer     DONE  → all tasks in review
+
+  → You went to sleep at 22:05.
+  → You wake up to 6 tasks in review. Approve. Merge. Ship.
 ```
 
-One command. Three agents. Zero tab-switching.
+One goal. Five agents. Six PRs. Zero tab-switching. $4.20 in tokens.
 
-## Get started in 30 seconds
+## Launch your AI company in 30 seconds
 
 ```bash
 npm install -g @oxgeneral/orch
 ```
 
-Then go to your project and run:
+```bash
+cd ~/your-project && orch
+```
+
+That's it. ORCH auto-initializes, opens the TUI command center. Add agents and tasks right from there.
+
+Or deploy a pre-built department:
 
 ```bash
-cd ~/your-project
-orch
+orch org deploy startup-mvp --goal "Build invoicing SaaS with Stripe"
+orch run --all --watch
 ```
 
-That's it. ORCH auto-initializes on first run, then opens the TUI dashboard — you add agents and tasks right from there.
+**Requirements:** Node.js >= 20. That's it. No database. No cloud. No Docker.
 
-**Requirements:** Node.js >= 20
+## Your AI company org chart
 
-## Why teams choose ORCH
+### CTO — strategic decomposition
+Set a high-level goal. Your CTO agent decomposes it into concrete tasks, assigns priorities, and delegates to the right departments. You set strategy — AI executes.
 
-### Parallel execution that actually works
-Run up to N agents simultaneously. ORCH handles dispatching, slot management, and prevents double-assignments. You set `max_concurrent_agents: 5` and forget about it.
+### Engineering Department — parallel execution
+Backend A, Backend B, Frontend — each agent gets its own git worktree (isolated branch). They work in parallel without file conflicts. Failed? Auto-retry with exponential backoff. Stalled? Zombie detection kills and re-queues.
 
-### Agents that don't give up
-Failed? ORCH retries with exponential backoff. Stalled? Automatic detection kills the zombie and re-queues. Crashed? The next tick picks it up. Your tasks finish even when individual runs fail.
+### QA Department — automated verification
+QA agents pick up completed work, run tests, validate contracts. Reject with feedback → task goes back to engineering with your notes. The loop closes automatically.
 
-### A real state machine, not a TODO list
+### Code Review — mandatory quality gate
+Nothing touches `main` until reviewed. Every task flows through the state machine:
 ```
 todo → in_progress → review → done
-                   ↘ retrying → in_progress
-                   ↘ failed
+                    ↘ retrying → in_progress
+                    ↘ failed
 ```
-Every transition is validated. No task gets lost. No agent runs something that's already done.
+Every transition validated. No task gets lost. No code merges without approval.
+
+### Inter-department communication
+Agents talk to each other — direct messages, team broadcasts, shared context store. Backend finishes auth module → sends message to QA → QA starts testing. No copy-paste. No manual routing.
+
+## Not just engineering
+
+ORCH orchestrates **any process** — not just code. The shell adapter runs any CLI tool, which means any workflow becomes a zero-human department:
+
+| Department | Agents | What they do |
+|-----------|--------|-------------|
+| **Engineering** | Claude, Codex, Cursor | Write code, fix bugs, refactor |
+| **Editorial** | Claude (writer), Claude (editor), Shell (grammarly) | Write articles, edit, check grammar, publish |
+| **Sales Ops** | Shell (CRM scripts), Claude (copywriter), Shell (email sender) | Generate leads, write sequences, send outreach |
+| **Analytics** | Shell (pandas, duckdb), Claude (analyst), Shell (matplotlib) | Clean data, compute KPIs, generate reports |
+| **Content Factory** | Claude (strategist), Claude (writer x2), Claude (SEO) | Plan content calendar, write posts, optimize |
+| **Security** | Shell (Semgrep, Trivy, Gitleaks), Claude (hunter) | Scan code, correlate findings, auto-fix |
+| **DevOps** | Shell (terraform, kubectl), Claude (architect) | Plan infra changes, apply, verify |
+
+Every department gets the same superpowers: state machine governance, retry, messaging, isolation, review gate.
+
+## Why founders choose ORCH
+
+### You're the CEO, not the babysitter
+Set goals, not tasks. Your CTO agent decomposes strategy into work. Backend builds. QA tests. Reviewer checks. You approve. That's the workflow.
+
+### Real departments, not just agents
+Teams with leads, shared task pools, auto-claiming. CTO, Backend, QA, Reviewer — organized like a real org chart. Broadcasts, messaging, shared context.
+
+### Runs while you sleep
+Auto-retry, stall detection, exponential backoff. Your agents don't stop when one fails — ORCH restarts, re-queues, and keeps going. Deploy at night, review in the morning.
+
+### Main branch is sacred
+Every agent works on its own git branch. Scope overlap detection prevents conflicts before they happen. Mandatory review step. Nothing merges until you approve.
+
+### 30 seconds to a full department
+`orch org deploy startup-mvp` — CTO, backend x2, QA, reviewer. Team created. Goal set. Agents ready. One command.
+
+### Free. Yours. Forever.
+MIT license. Your API keys. Your machine. State in `.orchestry/` — plain YAML, JSON, JSONL files you can read, edit, commit. Zero cloud dependencies.
+
+### Works with every tool — AI or not
+| Adapter | What it runs | Use as |
+|---------|-------------|--------|
+| `claude` | Claude Code CLI | CTO, Backend, Reviewer, Writer, Analyst |
+| `opencode` | OpenCode (Gemini, DeepSeek via OpenRouter) | Backend, Frontend, Writer |
+| `codex` | OpenAI Codex CLI | Backend, QA |
+| `cursor` | Cursor Agent CLI (headless) | Frontend, Backend |
+| `shell` | **Anything**: `npm test`, `python bot.py`, Semgrep, `curl`, CRM scripts, email senders, data pipelines | QA, Security, DevOps, Sales, Analytics, Content — any role |
+
+The `shell` adapter is the key: **if it runs in a terminal, it's an employee**. This is how ORCH goes beyond engineering — any CLI tool becomes part of your zero-human company.
+
+## Pre-built AI companies
+
+Deploy a full department with one command:
+
+**Engineering**
+
+| Template | Agents | What it does |
+|----------|--------|-------------|
+| `startup-mvp` | CTO, Backend x2, Frontend, QA, Reviewer | Ship an MVP in 48 hours |
+| `pr-review-corp` | Security, Performance, Style, QA, CTO | Automated review for every PR |
+| `migration-squad` | CTO, Migrator x3, QA, Reviewer | JS-to-TS migration over a weekend |
+| `security-dept` | Semgrep, Trivy, Gitleaks, Hunter, Reviewer | Multi-layer security audit |
+| `test-factory` | Coverage, Backend x2, QA x2, Reviewer | Coverage from 40% to 80% overnight |
+| `bugfix-dept` | Triager, Fixer x3, QA, Reviewer | 100 issues to 0 in a week |
+
+**Non-Engineering**
+
+| Template | Agents | What it does |
+|----------|--------|-------------|
+| `content-agency` | Strategist, Writer x2, Editor, SEO | Content factory: plan, write, edit, optimize |
+| `data-lab` | Shell (pandas, duckdb, matplotlib), Analyst | 3 CSVs → executive report by morning |
+| `sales-machine` | Researcher, Copywriter, Shell (email), QA | Lead gen → personalized sequences → send |
+| `docs-team` | Architect, Writer x2, Editor, Reviewer | Technical docs from codebase analysis |
 
-### Real-time dashboard in your terminal
 ```bash
-orch          # launches TUI
+orch org list                                    # See all companies
+orch org deploy startup-mvp                      # Deploy the default
+orch org deploy startup-mvp --goal "Build X"     # Deploy with a goal
+orch org export my-company                       # Save your setup as template
 ```
-Full-screen Ink/React dashboard with:
-- Live task & agent status with three tabs: **Tasks**, **Agents**, **Goals**
-- Activity feed with token counts
-- Keyboard-driven: create tasks, assign agents, approve reviews — without leaving the terminal
-- Command bar with `/task add`, `/agent add`, tab completion
-- **Help overlay** (`?` or `F1`) — discover all keyboard shortcuts at any time
-- **Toast notifications** — done/failed/review completions with optional bell sound
-- **Error hint panel** — when an agent fails, see the exact cause and fix hint inline
-- **Detail panel resize** (`+`/`-`/`M`) — expand agent/task detail to full screen
-- **Goal-task linking** — badge tasks with their goal, group by goal with `G`, see per-goal progress bars
-- **Inline validation** — wizard forms validate as you type (duplicate names, invalid priority)
-- **Tab badge flash** — header tabs blink on task completion events outside the active tab
-
-### Goals — strategic direction for your agents
-Define high-level goals and let ORCH autonomously generate tasks to achieve them. Goals have statuses (`active`, `paused`, `achieved`, `abandoned`), can be assigned to specific agents, and appear in a dedicated TUI tab for tracking.
-
-### Teams — organize agents into squads
-Group agents into teams with a lead, shared task pools, and auto-claiming. Each team member has a role and badge. The lead coordinates work distribution, and the team pool keeps related tasks together.
-
-### Inter-agent messaging
-Agents communicate through direct messages and broadcasts. Send context between agents, coordinate across teams, and keep everyone in sync — all via CLI or programmatically during runs.
-
-### Reactive dispatch
-No more waiting for the next 30-second poll cycle. When a task is created, ORCH dispatches it immediately (500ms debounce). Your agents start working in under a second.
-
-### Autonomous mode
-Set a goal, and ORCH generates work for idle agents automatically. Goal-directed task creation means your team stays productive without manual task assignment.
-
-### Shared context store
-A key-value store for inter-agent data exchange. Agents save results, share findings, and build on each other's work — with optional TTL for ephemeral data.
-
-### Global config & settings wizard
-Configure activity filters, display preferences, and agent defaults through the TUI settings wizard or `orch config edit`. No manual YAML editing required.
-
-### Zero infrastructure
-All state lives in `.orchestry/` — YAML configs, JSON state, JSONL event logs. No database. No cloud. No Docker. `git clone` and you're running.
-
-### Works with any AI tool
-| Adapter | What it runs |
-|---------|-------------|
-| `claude` | Claude Code CLI (`claude --print`) |
-| `codex` | OpenAI Codex CLI (`codex exec --json`) |
-| `cursor` | Cursor Agent CLI (headless mode) |
-| `shell` | Any command: `npm test`, `python bot.py`, custom scripts |
 
 ## Full CLI reference
 
@@ -141,96 +196,71 @@ All state lives in `.orchestry/` — YAML configs, JSON state, JSONL event logs.
 orch init                          # Initialize project
 orch doctor                        # System diagnostics
 
+# Departments & Agents
+orch agent add <name> --adapter claude --role "CTO — decomposes goals"
+orch agent list                    # Status of all agents
+orch agent disable/enable <id>     # Toggle availability
+
+# Organization Templates
+orch org list                      # List available companies
+orch org deploy <template>         # Deploy a full department
+orch org deploy <template> --goal "..." # Deploy with a goal
+orch org export <name>             # Export current setup
+
 # Tasks
 orch task add "Title" -p 1         # Create task (priority 1-4)
 orch task list                     # List all tasks
-orch task list --status todo       # Filter by status
 orch task assign <task> <agent>    # Manual assignment
 orch task cancel <task>            # Cancel running task
 
-# Agents
-orch agent add <name> --adapter claude --role "Role description"
-orch agent list                    # Status of all agents
-orch agent disable/enable <id>     # Toggle availability
+# Teams (Departments)
+orch team create <name> --lead <agent-id>
+orch team join <team-id> <agent-id>
+orch team add-task <team-id> <task-id>
+orch team disband <id>
+
+# Goals (Strategy)
+orch goal add "Title" --description "..."
+orch goal list
+orch goal status <id> achieved
 
-# Teams
-orch team create <name> --lead <agent-id>    # Create a team
-orch team list                               # List all teams
-orch team join <team-id> <agent-id>          # Add agent to team
-orch team leave <team-id> <agent-id>         # Remove agent from team
-orch team set-lead <team-id> <agent-id>      # Transfer lead role
-orch team add-task <team-id> <task-id>       # Add task to team pool
-orch team disband <id>                       # Disband a team
-
-# Messaging
-orch msg send <agent-id> "message" -s "subject"   # Direct message
-orch msg broadcast "message" -s "subject"          # Broadcast to all
-orch msg broadcast "message" --team <team-id>      # Broadcast to team
-orch msg inbox <agent-id>                          # View inbox
-
-# Goals
-orch goal add "Title" --description "desc"   # Create a goal
-orch goal list                               # List all goals
-orch goal list --status active               # Filter by status
-orch goal show <id>                          # Goal details
-orch goal status <id> achieved               # Change status
-orch goal update <id> --title "New title"    # Update fields
-orch goal delete <id>                        # Delete a goal
-
-# Shared Context
-orch context set <key> <value>     # Store shared data
-orch context get <key>             # Retrieve shared data
-orch context list                  # List all entries
+# Communication
+orch msg send <agent-id> "message"              # Direct message
+orch msg broadcast "message" --team <team-id>   # Team broadcast
+orch context set <key> <value>                  # Shared context
 
 # Execution
+orch run --all --watch             # Launch all agents
 orch run <task-id>                 # Run single task
-orch run --all                     # Run everything
-orch run --watch                   # Daemon mode
 
 # Monitoring
 orch status                        # Quick overview
 orch logs <run-id>                 # View run logs
-orch tui                           # Interactive dashboard
+orch tui                           # Command center (TUI)
 
 # Config
 orch config edit                   # Open in $EDITOR
-
-# Updates
-orch update                        # Check for and install latest version
+orch update                        # Check for updates
 ```
 
 **Aliases:** `orchestry`, `orch`, `ao`
 
 ## Architecture
 
-Clean DDD with dependency injection — no frameworks, no decorators, pure TypeScript:
+ORCH is an engine first, CLI second. The core has zero dependencies on CLI/TUI layers — you can import `@oxgeneral/orch` as a library and build your own interface.
 
 ```
 src/
-├── domain/           # Models & state machine
-│   ├── task.ts           # Task entity, priorities, statuses
-│   ├── agent.ts          # Agent entity, stats, badges
-│   ├── run.ts            # Run entity, event types
-│   ├── goal.ts           # Goal entity, statuses
-│   ├── team.ts           # Team entity, members, pools
-│   ├── message.ts        # Message entity, channels
-│   ├── config.ts         # Project config schema
-│   ├── global-config.ts  # Global user settings
-│   ├── default-agents.ts # Default agent definitions
-│   ├── transitions.ts    # State machine transitions
-│   ├── scope.ts          # File scope matching
-│   ├── state.ts          # Orchestrator state
-│   ├── events.ts         # Event type definitions
-│   └── errors.ts         # Domain error types
+├── domain/           # Models, state machine, errors
 ├── application/      # Orchestrator engine, services, event bus
 ├── infrastructure/
-│   ├── adapters/     # Claude, OpenCode, Codex, Cursor, Shell (pluggable)
+│   ├── adapters/     # Claude, OpenCode, Codex, Cursor, Shell
 │   ├── storage/      # File-based (YAML/JSON/JSONL)
 │   ├── process/      # PID management, graceful kill
-│   ├── template/     # LiquidJS template engine
-│   └── workspace/    # Isolation modes (shared/worktree/isolated)
+│   ├── template/     # LiquidJS prompt templates
+│   └── workspace/    # Git worktree isolation
 ├── cli/              # Commander.js commands
-└── tui/              # Ink + React dashboard
+└── tui/              # Ink + React command center
 ```
 
 ## Development
@@ -238,19 +268,13 @@ src/
 ```bash
 npm run dev            # Run via tsx
 npm run build          # Build ESM + DTS
-npm test               # 1386 tests via Vitest
+npm test               # 1493 tests via Vitest
 npm run typecheck      # Strict TypeScript
 ```
 
-**Performance:** CLI startup is ~40% faster thanks to lazy command imports — heavy dependencies (orchestrator, adapters, LiquidJS) are loaded only when the relevant subcommand is invoked. `--help` and lightweight commands like `task list` skip the full container entirely.
-
 ## Community
 
-We just hit **10 stars** — small number, real users. Every star so far came from someone who actually runs multi-agent workflows and needed something better than tab-switching.
-
-**Next milestone: 25 stars** — when we get there, we'll add a public "Used by" showcase. If you're already running ORCH in your workflow, [open an issue](https://github.com/oxgeneral/ORCH/issues) and tell us — you'll be first on the list.
-
-**If ORCH saves you time → [⭐ Star it on GitHub](https://github.com/oxgeneral/ORCH)** — it helps other developers find the project.
+If ORCH saves you time — **[Star it on GitHub](https://github.com/oxgeneral/ORCH)** — it helps other founders find the project.
 
 [![Star History Chart](https://api.star-history.com/svg?repos=oxgeneral/ORCH&type=Date)](https://star-history.com/#oxgeneral/ORCH&Date)
 
@@ -259,12 +283,44 @@ We just hit **10 stars** — small number, real users. Every star so far came fr
 
 ## Used by / Early Adopters
 
-> This section will be filled as the community grows. Using ORCH in your project? [Let us know](https://github.com/oxgeneral/ORCH/issues/new?title=Using+ORCH+in+production&body=Tell+us+about+your+setup) — we'd love to feature you here.
+> Running a zero-human company with ORCH? [Let us know](https://github.com/oxgeneral/ORCH/issues/new?title=Zero-human+company+with+ORCH&body=Tell+us+about+your+setup) — we'd love to feature you here.
 
 <!-- ADOPTERS_START -->
-*Be the first to add your project here — open an issue with "Using ORCH in production".*
+*Be the first to launch your AI company here.*
 <!-- ADOPTERS_END -->
 
+## FAQ
+
+### Do I need a team to use ORCH?
+
+No. **Solo founders are the primary users.** You + 2 agents is already a zero-human company. ORCH gives you auto-retry, state machine, dashboard, and token tracking even with a single agent. Start with one, scale to departments.
+
+### Will agents mess up my codebase?
+
+No. Every agent works in an isolated git worktree on its own branch. Nothing touches `main` until you explicitly approve. Mandatory review step in the state machine. Scope overlap detection prevents conflicts before they happen.
+
+### Is this only for engineering?
+
+No. The shell adapter runs any CLI tool — which means ORCH orchestrates any process. Engineering, editorial, sales, analytics, security, DevOps. **If it runs in a terminal, it's an employee.** Deploy `content-agency`, `data-lab`, or `sales-machine` with one command.
+
+### How much does it cost?
+
+ORCH is free forever (MIT). You pay only for the AI APIs you already use (Claude, Codex, etc.). The TUI shows token counts per agent per run in real-time — no surprise bills.
+
+### What AI tools does it support?
+
+Five adapters: **Claude Code**, **OpenCode** (Gemini, DeepSeek, any OpenRouter model), **Codex**, **Cursor**, and **Shell** (any CLI tool). Your API keys, your tools — ORCH coordinates them.
+
+### Is there a cloud component?
+
+None. Zero cloud. All state in `.orchestry/` — plain YAML, JSON, JSONL files. No signup, no account, no data leaves your machine.
+
+### How is this different from Paperclip?
+
+Paperclip needs PostgreSQL, a web server, and cloud setup. ORCH needs `npm install`. Same vision — zero-human companies — but ORCH is the hacker's version: terminal-first, file-based, zero infrastructure, MIT licensed.
+
+---
+
 ## License
 
-[MIT](LICENSE) — use it however you want.
+[MIT](LICENSE) — build whatever you want.