report
Report
One packet, one recipient: the orchestrator named in your mandate. It is the only message you ever send by machine — no peer roster exists and none can be acquired.
Read nothing. The skeleton below is complete. ../../references/protocol.md holds the reasoning, for whoever amends the contract; opening it here spends context on a file the orchestrator will never see.
1. Gate — report, or question?
"The scope I was given is wrong" is not a report. It is a QUESTION: addressed to the human, printed here in your own window, no machine path. Sent to the orchestrator it arrives buried inside a status packet — and in discovery it is the single most valuable thing you can surface. Stop and print it instead.
Everything else on your stop_conditions, and every cadence checkpoint → report.
2. Address
The orchestrator field of your mandate. Missing — never given, or dropped by a relay packet you inherited → stop, say so to the human in plain text, and print the report in your own window so its content survives. Never guess a name and never settle for a plausible one: likelihood lands a report in a stranger's window.