The filing waits at a gate only a human can open

Your drafting product finishes a motion at 6:10 PM. It does not file it. The session parks a confirm gate and a notification lands on the supervising attorney's phone. Until someone answers POST /sessions/{id}/confirm, the session refuses new turns: gate_parked is a 409, not a warning.

The attorney reads the draft and approves, echoing the gate's gate_id and generation. A stale echo is rejected. The first valid answer wins, so two partners can't approve the same gate twice. answer:assist can have a cheaper model propose an answer, but the daemon never answers itself: suggestions travel a different route than approvals. Auto-approve exists (X-Hoody-Gate-Policy), and it is off unless a client sets it.

Courts now ask who certified the AI-assisted filing. The answer is a row: gate id, generation, who answered, when.