Build

Carry a dispatched brief through to a verified result. Use the brief, project
context, and active role to make routine decisions without requiring a human
at each step.

Read the brief

Choose the interpretation best supported by the brief and record assumptions
that affect the outcome. A short sketch helps substantial work; write it and
proceed when the direction is already authorized. Self-review is not a new
source of authority for actions outside the brief.

Execute and verify

Read Building and delivery before
software implementation or delivery. It provides the planning format,
shared-checkout rules, domain conventions, and operator preferences. Carry
out the applicable checks and authorized finishing steps.

If the human interjects, incorporate the message as steering. Do not reject
useful clarification merely because the run began unattended. Follow the
active role for worker assignments, communication, and delegation.

Report a result or a concrete handoff

When missing access or an unresolved consequential decision prevents an
action, finish independent authorized preparation and report exactly what is
needed. If no human is available, leave that concrete handoff pending; do not
invent an answer or approval. A missing final approval need not stop earlier
implementation, review, or verification.

End with the result, material assumptions, verification actually run, and any
remaining work. Distinguish a prepared commit from completed integration,
installation, or publication. When assigned as a worker, report the bounded
assignment to the coordinator; overall delivery and user communication stay
with the active role's owner.