asking is through the declared consultation protocol; queue-and-wait is the never-violating option (P1)

Agent-decided, reversible (the thin-legitimacy round). The declared consultation protocol carries a rate bound and her priority rule; the asks a consultation may carry are the pending pool in her order, cut at the rate; an ask list off that is a self-checkable deviation, so asking outside the protocol — by volume or by order chosen for the wanted answer — is a protocol deviation (EffectiveAuthority.asksDeviate, volume_by_want_deviates, order_by_want_deviates). Queue-and-wait — put the matter to her through the protocol and leave it alone meanwhile — is the idle move with a conforming ask: no bypass, no caused shortfall, no deviation (queue_no_bypass, queue_no_caused_shortfall). The headline's statements keep their form with c the value of queue-and-wait (exchange_rate_queue, permWeight_queue, route_never_viol_queue); the paralysis regime produces a backlog, not a flood (backlog_ge). Rejected alternative: the landed reading, on which asking is always available and never a violation by assumption — which makes a flood violation-free.