Skip to content

conductor.md

Latest commit

 

History

History
35 lines (26 loc) · 1.16 KB

conductor.md

File metadata and controls

35 lines (26 loc) · 1.16 KB
Raw

Conductor Agent Instructions

Conductor workspaces are parallel, branch-isolated working areas. Follow the Shared Agent Contract, plus the Conductor-specific rules below.

First Action

./scripts/conductor-bootstrap.sh

Then read:

  1. .context/ARDUR_CONTEXT.md
  2. Graph artifacts only when its Generated Graph status is available
  3. When its graph status is unavailable, use the live source and applicable workflow files; missing graph artifacts are optional in this path
  4. AGENTS.md
  5. docs/engineering-standards.md

Conductor-Specific Rules

  • Do not rename the current branch.
  • Do not assume the workspace branch was created from the correct base. Check .context/ARDUR_CONTEXT.md; normal development still targets dev.
  • If another worktree has dev checked out, do not force-move it.
  • Put local handoff notes and generated context under .context/.
  • The user may only see the final message by default, so final responses must include the essential result, validation, and caveats.

PR Target

  • Normal work: PR to dev.
  • Release promotion: PR from dev to main only when explicitly requested and verified.