What Yoke is

Yoke is a control plane for software delivery. Humans set direction and approve what matters; agents and deterministic workers execute. Strategy, backlog, dependencies, verification, environments, and deployment share one Postgres-backed universe.

What you get

• Strategy — a durable planning corpus per project
• Frontier — what can run now, and why
• Items — work with pinned workflows (Dash, Issue, Epic, Blitz, Task)
• Sessions — harness sessions and what they hold
• Delivery — environments, flows, runs, databases, infrastructure
• QA — methods, plans, and recorded outcomes
• Doctor / Events / Ouroboros — health, audit trail, and self-improvement

The same engine runs on your laptop, on a team server, or on Yoke Cloud. The web workbench and the CLI both talk to that universe.

How work moves

1. Capture an idea (or let feed materialize work from strategy)
2. Refine until the item is ready
3. Implement in an isolated worktree lane (implement / shepherd / conduct / dash)
4. Verify through attached QA
5. Usher: merge, deploy, record evidence, mark done

/yoke steer staffs work from strategy. /yoke charge selects a runnable item from the frontier for the current session.

Read next

• Modes — Local, Cloud, Self-hosted
• Install — one installer, then onboard
• Maintaining a private fork — operator-supplied releases and indexes
• Concepts — universe, projects, items, workflows