Operations guide#
How to install, authorize, run, and diagnose wastech-orchestrator in production. The orchestrator drives coding agents (OpenAI Codex CLI, Anthropic Claude Code CLI) through a deterministic pipeline and publishes the result to a Pull Request. It owns git (commit/push/PR); the agents only edit files in a dedicated clone. This guide is for the operator who runs it; the architecture reference is worc_architecture.md and the security policy is security.md.
The orchestrator never installs or authorizes the CLIs and never stores credentials. Authorization for git and for each agent is configured outside the orchestrator (see 2. Authorization).
Related guides:
- cookbook.md - practical recipes from workspace setup to recovery.
- configuration.md - every
config.yamlfield, default, and validation rule, indexed there across four topic pages. - task-authoring.md - task front matter, examples, and validation behavior.
The chapters#
The guide is six pages. Read them in order the first time; after that this page is the map.
| Chapter | Page |
|---|---|
| 1. Installation, Upgrading the orchestrator, 2. Authorization | Install, upgrade, authorize |
| 3. Preflight, command-set diagnostics, validating flows | Preflight and validation |
4. Running — run / watch, night runs, provider outages, rerun, finalize, the stop ladder |
Running tasks |
Structured logs, logs clean, runs clean, worc memory, Telegram |
Logs, state, notifications |
| 5. Git footprint and the audit commit, the PR body, auto-merge | Git footprint and publishing |
6. Diagnostics — reading what a run produced, 7. Recovery playbook — manual_action_required |
Diagnostics and recovery |