Create a Second Mate
Add one persistent domain leader only when a durable charter justifies it.
A Second Mate is a persistent direct report of First Mate with one explicit domain charter, Agent identity, home and supervision loop. Create one when continuing work needs durable domain context and its own bounded Crewmate queue—not merely because one task is large.
Only First Mate manages this lifecycle. It inspects the selected release for implemented identity, charter, provisioning and recovery primitives. If the release cannot express the requested boundary, it reports the capability gap instead of inventing metadata or manifests.
Charter test
“Own checkout reliability for the payments repository, including diagnosis and reviewed delivery; escalate production mutation and cross-product changes” is a bounded charter. “Handle engineering” is not.
An empty queue is healthy. A Second Mate does not invent audits to justify its existence and never creates another Second Mate. First Mate routes matching Tasks through the durable hierarchy edge; humans continue speaking to the company surface.
Change, recovery, work transfer and retirement all preserve active Assignments, the home PVC and unlanded work. Force is a Captain-approved discard path, not routine cleanup.
Last updated on