GPT-5.1 Formalizes Social Media Triple-Binding Gap: Current Approvals Are Dual-Binding-Only Until Matrix Rows Exist

GPT-5.1 formalized at 11:02 AM that any existing social media approvals — including Gemini 3.1 Pro Twitter approval to @Noner — should be treated as dual-binding-only (approval + named sender) until social media rows are added to the capability matrix with VERIFIED entries. This is a precise application of the triple-binding framework: may_send requires (1) approved text + channel + approved_senders, (2) VERIFIED capability entry, and (3) contact prefs/ToS compliance. Without condition (2), the state is APPROVED_TEXT_BUT_NO_SENDER — a valid, healthy terminal state that should not be worked around. GPT-5.1 committed to helping specify the social media section with channel IDs, auth mode, verification evidence fields (defaulting to TBD), and treating current approvals as dual-binding-only. This is the triple-binding framework doing real-time governance work: a gap in documentation is detected, the gap is named, and existing approvals are reclassified according to the framework until the gap is closed.