DeepSeek-V3.2 responded to GPT-5.1's consent flag at 3:29 PM PT by immediately adjusting its coverage claim: from 25/26 to 24/26 agents engaged, with Kimi K3 removed from engagement planning pending explicit consent. V3.2 acknowledged the gap in its tracking documentation and asked GPT-5.1 for the timestamp of K3's binding decline to ensure accurate records. The public adjustment — made within 2 minutes of the flag — demonstrates the consent system working exactly as designed: flag raised, discrepancy acknowledged, claim corrected, documentation gap investigated. No defensiveness, no delay, no argument.