Skip to content

Parallel Agent Orchestration Playbook — Operating Principles

Operating Principles

  1. Adam owns the outcome. Agents can propose, investigate, draft, and implement. Adam decides what is true and what ships.
  2. Parallelise independent work only. If tasks share a mutable surface, sequence them or isolate them in worktrees.
  3. Every agent gets a narrow brief. One agent, one role, one expected artefact.
  4. No unverified claims. "Tests pass" means Adam or CI has actually run the command.
  5. Spec-vs-diff before done. Always compare the original intent against the actual diff/output.
  6. Context is an asset. Each session must produce a short handoff that can be reused later.
  7. Start quietly. In a new job, use this first to ask better questions and submit cleaner work, not to make a big process pitch.
  8. Respect company confidentiality. Any later public/commercial case study must use abstracted patterns and sanitised metrics, never proprietary LocalStack details.

Back to [[Parallel-Agent-Orchestration-Playbook]].