Add one durable domain

Grow responsibility, not Agent count

Several sessions in parallel can increase throughput, but they do not create accountability. Create a durable domain only when related outcomes need continuing context and one stable owner.

Crew shape follows responsibility:

• First Mate coordinates the Fleet and the human boundary;
• a Crewmate investigates or ships one bounded outcome;
• a Second Mate owns a continuing domain and supervises its own Crewmates.

Do not create a department merely to parallelize one Task. Do not keep recurring project work on First Mate because each individual change looks small.

Charter customer-support engineering

After several onboarding defects, the company decides that technical support deserves a durable domain:

Own technical support defects for the web product. Reconcile accepted support reports with existing engineering work, diagnose reproducible software causes and deliver reviewed fixes. Escalate customer data access, production mutation, credentials, cross-product scope and merge.

Start with one support source and one repository. The charter names outcomes, inputs, routine authority, escalations and observable success. It does not authorize billing decisions, broad customer-data access or production deploys.

Compose only what the owner needs

The support Second Mate receives the smallest reviewed bundle that supports that charter:

identity instructions
+ conditional Skills
+ verified harness and model
+ native settings
+ required capabilities
+ evidence of the resolved bundle

Permanent identity and safety belong in the nearest AGENTS.md; conditional judgment belongs in one Skill; deterministic mechanics belong in SQL or TypeScript. The harness keeps its native settings instead of being flattened into one universal AgentOS schema.

A diagnostic Crewmate gets a different bundle: project instructions, read-heavy source access and a report contract, but no source write or production capability. Capability follows the outcome. More tools merely widen the consequences of a wrong next action.

Once this domain can own one support report end to end, connect it to real-world signals.