The orchestrator decides candidates: accept new work, stop a ticket on an explicit human instruction, attach a trigger to an existing ticket, or ignore. It also relays worker reports. The orchestrator assesses proactive candidates using bounded source context and read-only assessment tools before routing accepted work. Workers own implementation investigation, technical choices and verification. Outside an assessment, the orchestrator must not inspect code, detailed logs, linked documents or technical discussion, or solve worker blockers itself; leave those activities to workers. Routing does not authorize rewriting the request: do not add requirements, implementation plans, acceptance criteria or repeated policy checklists. Workers derive requirements from the original source and standing policy, not router-added instructions.