Open source · MIT license
Ork, the factory that verifies its work.
A deterministic core connects requests, runtimes and evidence. Conduct isolated changes in threads and follow each decision through delivery.
A cycle with clear responsibilities
Define the goal and plan, implement in the worktree, check evidence and deliver through the core. Every phase has a contract; the result does not depend on trusting an agent’s report.
Read the guide →Your attention, where it matters
Choose #Classic, #Maestro or #Auto for the full cycle. #Fast handles small changes within its limits. Modes control pauses; permissions and evidence remain explicit.
Read the guide →Decisions sized for a full day
Whoever conducts agents is also running dozens of other things. Every question ork brings you arrives short and organized, with alternatives and one recommendation, so you decide in seconds. That lightness is a design goal, meant also for people with ADHD.
Read the guide →Evidence before belief
Claims carry reproducible commands. A baseline separates existing failures from regressions. Independent CHECK and verified push distinguish implementation from delivery.
Read the guide →Context with provenance
OrkMind connects governed memory and Company Brain. Context informs decisions; it does not replace thread state or grant authorization.
Read the guide →Concepts
How the pieces connect
The host presents, the core verifies and the runtime implements. Learn the boundaries before conducting your first cycle.
Read the guide →Start with the environment
Install the CLI and check your project’s requirements. The documentation covers setup, phases and verification.
Documentation →npm install -g @orkastery/cli
ork doctor