2. I notice that the Admistrator prompt indicates that it can push tags (per §8 of orchestration.md). I disagree with this now. I do not want the Administrator to write anything to the repository.
3. Per 2 above, I therefore would like you to re-consider §8 of orchestration.md to minimize the amount of branches and tags that are used in the communications. I do not want to impose unnecessary restrictions on the communication protocol between agents, since the git repository is the primary and authoritative communication method, and we have now a lighter weight method that uses 'git ls-remote *' and a plan to scale up with SSH-keys. However, I would like to review the existing plan in this regard so as to minimize detrius that needs to be cleaned-up after action of the agents. In my ideal, following a fully successful operation, for every issue entered in issue.md, there should be a branch and PR *or* a branch and an {slug}-escalate tag. The agents should be designed so that proper operation of the machinery removes all active tags.
4. Please also design a script that I can run after a dry-run effort to identify any tags that are left with a {dry-run-prefix} in the repository and an (optional) parameter to remove them in the repository.
