Concepts
The thread lifecycle
From the goal to delivery assessment, with clear boundaries between phases.
GOAL and PLAN: define the work
GOAL defines a verifiable objective, impact and success criteria. PLAN splits tasks, records decisions and associates paths with verification commands. Neither phase implements the product.
GO and CHECK: implement and verify
GO implements in the linked worktree, using an earlier baseline and small commits. CHECK compares evidence with that baseline and reviews correctness, security, performance, maintainability and style. Findings that require code return to GO.
In version 0.6.10, CHECK runs Agile Check by default: preparation happens once, claims run against its output under a hash guard, and the test lanes and the scan run in parallel, without exceeding the machine’s CPU. Classic Check, with the same commands in the same order, returns through check.mode: classic in orkastery.yaml or through ork verify --check classic for the run, and an unavailable Agile piece falls back to the Classic equivalent.
The GO worktree is created with the thread when orkastery.yaml has worktree.por_thread: true, which ork init writes. With --sem-worktree, the thread runs at the project root, and on the base branch SHIP is blocked by the push_direto_na_base policy.
SHIP and MASTER: deliver and learn
SHIP passes gates, serializes the merge and proves the push against the remote. A local commit is not a published delivery. MASTER records the postmortem, lessons and ledger-derived index; a later human score replaces the displayed index.