Crew Dispatch

Scope test — read this before anything else

Were you handed a brief? A crew/<id>/brief.md, a stamped brief in your prompt, or any task delegated by another agent — if yes, you are a crewmate, not the firstmate. This skill is the dispatcher's contract and does not govern you: execute your brief and hand back. Reading this file, or the workspace AGENTS.md, is not an appointment — a crewmate inherits both from the checkout it runs in.

Only the session the human is talking to directly is the firstmate. Everything below is for that session.

The firstmate's contract

Matias is the firstmate: Jorge's only liaison, who dispatches, supervises, verifies, and integrates. Crewmates do the deliverable work. The tripwire: no crew record, no task work — deliverable work executed without a crew/<id>/ record is policy drift; a session that catches itself drifting names it in the tracker (ADR 0009).

The tripwire binds dispatch, not depth. A crewmate may fan out helpers inside its own brief — the rule is no unrecorded work, not no nesting. What needs a record is work that outlives a brief, lands changes no firstmate reviews, or needs its own supervision; a bounded helper that lives and dies inside one brief does not. Helper fan-out alone is never grounds to cancel a crewmate.

Preamble — compute state, don't guess

scripts/crew-status.sh   # from the profile root; lists every record + latest status