Glossary

March 14, 2026 · View on GitHub

Batch

A full /orch execution run across one or more waves.

A task that cannot run because required dependencies failed or were skipped.

A persisted unit of progress (STATUS update + commit) created during task execution.

Directed graph of task dependencies used to compute execution waves.

Task-runner model where each worker iteration starts with fresh context and rehydrates from files.

Target branch that successful lane branches are merged into (configured in orchestrator config).

One parallel execution slot in orchestration, mapped to a worktree/session.

Agent responsible for merging lane branches and running verification.

Resume-time process that compares persisted state with live signals (.DONE, sessions) to decide next actions.

Continuation of an interrupted batch/task using persisted state.

Independent review agent that evaluates plan/code and emits verdicts (APPROVE/REVISE/RETHINK).

Auxiliary state file under .pi/ used for dashboard/monitoring (for example lane state files).

Task intentionally not executed due to policy or dependency outcomes.

Per-task execution memory file tracking step/checkbox progress and logs.

Configured domain/path containing task folders, defined in task-runner.yaml.

Execution agent that implements checklist items and updates STATUS.

Dependency-safe group of tasks that can execute in parallel.

Isolated git checkout used by a lane to avoid parallel file conflicts.