Offers, answers, fresh consent
The core never touches a colonist. It creates a proposal bound to one pawn, and only that pawn's decision handle can answer it: accept, refuse, counter or not now. Anything else, like a forged actor or an extra field, is rejected before it reaches the game. This is the character path; the player harness below has no consent step yet, which is what phase 2 C restores.
A counter executes nothing. If the core adopts it, it comes back as a revised offer that needs a fresh yes, with at most two revisions per thread. Replacing a stockpile haul with rescue needs fresh consent, confirmed exclusion from the haul, and an empty-handed pawn off the captured haul trip; already-carried cargo finishes natively before rescue can start. An answer that arrives after the work is already done lapses: it is kept as given, but starts nothing.
An accepted haul becomes a native intent; the ordered haul was retired. Rescue, building and cooking still use the older ordered model, one hand-built job that stops on low needs.
src/coordinator.ts · src/protocol.ts · src/native-intents.ts · mod/NativeIntents.cs · mod/Rescue.cs · mod/Production.cs