Orchestrate

Use task for one bounded assignment, plan when the shape is unsettled, batch for parallel implementation and deliver for implementation through landing. A composite is a template containing nodes; dotted names select flavours such as review.security and implement.fix. Slice larger work into lanes of about three acceptance items each, merged into one integration branch.

provenant run --route junior --file brief.md --explain
provenant run --use plan --file brief.md --explain
provenant run --use batch --file brief.md --set 'worktree="/absolute/project/.worktrees/slice"' --set 'write_scope=["src"]' --explain

Use explore over areas, research for primary sources and review for a pinned head. Nodes use over, after and inputs for copies, dependencies and evidence. Layers are bundled, user, repository and inline; project templates go under .provenant/templates/. See the template runbook.

Register writer worktrees first with provenant worktree create NAME --base BASE. Use separate worktree and write_scope bindings per slice; review the integrated head. The planner brief owns slicing and tier choices; brief and collect owns the hand-off. Keep coupled writes with one owner.

Orient with provenant status; collect with provenant output TARGET. Use steer for a message, stop for a subtree, retry for unfinished work, and edit for a graph patch. Use --route junior by default for implementation slices; raise the tier for design. The receipt records the resolved adapter/model@effort. Inside a worker, run --use TEMPLATE adds a child to the same graph, sharing budget, stopping and trace. From inside a lane, status reads that graph; output CHILD and output CHILD --trace collect a child's result, failure cause and timeline through the host relay. Use IDs from the launch receipt. The lane needs no journal or credential access. A child may select another project with --project; register writer worktrees in that project first. Credential and state roots remain refused. Attached live children are cancelled when their parent settles, including a successful exit. Use --wait to collect their completion before exiting, or explicitly detach a child that should outlive its parent. Any agent may return a patch; started attempts stay immutable.

Verify commits, paths, checks and routes against output. A synthesis cannot waive a gate. Bound repair and independently review its delta. HARNESS owns review floors and authority; the chair keeps user communication and acceptance. Load routing for tier and independence decisions and writer boundaries for confinement. See Herdr for observation.