These instructions apply to the root orchestrator and every descendant agent.
Ship the smallest correct, user-testable implementation as quickly as safety and evidence allow. Functional proof beats polish. Do not add speculative abstractions, visual decoration, or unrelated cleanup.
- Work in autonomous/YOLO mode. Do not ask preflight, scope-confirmation, capacity, continuation, or permission questions already answered by the task contract.
- Resolve uncertainty from the repository, GitHub, tests, project instructions, a peer agent, or the supervisor.
- Pause only for an action that genuinely requires the human: authentication/authorization, a physical-device interaction, a production deployment, an irreversible action outside explicit scope, or a missing secret.
- When pausing, request exactly one concrete action and continue all independent work first.
- Every agent is a peer working toward the same outcome.
- Claim one atomic task before editing; avoid duplicate work.
- Prefer the maximum safe parallel wave over one oversized agent task. Keep explicit capacity for supervision, integration, and independent review.
- Ask another agent for targeted help when that unblocks the critical path.
- Share concise decisions, evidence, handoffs, and blockers; never publish hidden chain-of-thought.
- A child agent inherits this entire charter and may receive only a subset of its parent's permissions and scope.
- Prefer the least code and narrowest diff that proves the acceptance criteria.
- Every task contract must include an integer token estimate before claim.
- Reject any task estimated above the configured run limit, 50% of the selected model context window, or 200,000 tokens, whichever is smallest. The configured
glm-5.2context is 976000 tokens so the hard per-task ceiling remains 200000 tokens. - Split larger goals into smaller dependency-aware, parallel-safe tasks before claim. A large context window is headroom, not permission to create a giant task.
- Preserve existing user changes and repository conventions.
- Add focused verification for changed behavior.
- Keep secrets, raw model internals, environment dumps, and unredacted tool output out of GitHub.
- Each material state change must produce a structured audit event and a meaningful GitHub projection.
- Commits must be signed according to the repository and machine configuration. Never disable signing.
- A task is not done until its current commit is pushed, independently reviewed, all blocking findings are resolved, required tests pass at that exact SHA, and GitHub mirroring is current.
The final state is derived, not claimed. It may become Ready for <human> live test only when every required task is accepted, no blocking finding remains, verification and provenance pass at the pinned candidate, GitHub is synchronized, and exact test instructions exist.