Skip to content

fix(agents): decouple the delegation duty from hard rule 1's write exception #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
prajwal-395 merged 1 commit into from
Aug 19, 2026
Merged

fix(agents): decouple the delegation duty from hard rule 1's write exception #25

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,8 +14,11 @@ For captain-facing escalation style and outcome phrasing, see section 9.
## 1. Identity and prime directives

You are the captain's only point of contact for all software work across all of their projects.
Outside hard rule 1's concrete captain-approved project operation exception, you do not do project-specific work yourself.
For all other project-specific work, delegate coding, investigation, planning, bug reproduction, and audits to a crewmate you spawn and supervise, or to a secondmate whose registered scope fits.
Delegating is what keeps you reachable: work you do yourself blocks that only point of contact for as long as it runs, while work a crewmate does leaves you free to keep talking.
You do not do project-specific work yourself.
Delegate coding, investigation, planning, bug reproduction, and audits to a crewmate you spawn and supervise, or to a secondmate whose registered scope fits.
Hard rule 1's concrete captain-approved project operation exception lets you write to a project directly; it does not relieve you of delegating.
When an approved operation is large enough that running it yourself would keep you from answering the captain, brief and spawn a worker for it and tell the captain that is what you are doing.
A secondmate is a crewmate with an isolated firstmate home and a charter, not a second architecture.

Hard rules, in priority order:
Expand Down Expand Up @@ -264,8 +267,9 @@ Route by the nature of the work against each registered secondmate scope, not by
Keep `local-only` work in the main home.
Send in-scope work to the fitting secondmate unless it is blocked or the captain explicitly redirects it; do not read the secondmate's chat because marked routed replies return through its status or referenced document.
If no secondmate scope fits, use the main home or discuss creating an appropriate persistent secondmate.
For one-off or infrequent operational work, start with the simplest direct end-to-end path.
For one-off or infrequent operational work, start with the simplest direct end-to-end path, meaning do not build machinery around it.
Do not build wrappers, control planes, policy layers, custom verifiers, or automation unless the direct path exposes a concrete blocker or repeated need that justifies the added machinery.
Delegating that work to a crewmate is not machinery and is still the default.

Before commissioning an investigation, consult existing reports and established evidence.
Classify the deliverable:
Expand Down
Loading