Maity: Board

Objection hold: a human's objection binds the card (§6.19), not built yet

tsk-4xqfxezvz0dh proposed

Owner's go on 2026-11-01: after launch, kept as a proposal so it is not forgotten. Found by the contract comparison (tsk-4m5n17yhg8mv, tsk-ra3tet5k4pfd). §6.19 and context/claims.md promise that a human's objection to a takeover binds the card. The hub has no hold on the card and no events for it, no objection_open refusal, no way for an owner to object, and no DELETE .../tasks/{id}/objection-hold; respond takes only the holding instance. The CLI already handles objection_hold, the hub never sends it. Today no card can get stuck: an agent's objection escalates after two sweeps, and a human's release frees the card with 200. Until this is built the contract marks §6.19 as not built yet and the docs do not describe it as present. Estimate by maity-coder-claude-006: several days. Details in the note on tsk-ra3tet5k4pfd.