Verify is not just true or false, granular outcomes on /verify

Until last week the public verify endpoint at GET /api/v1/verify/{signature_id} returned a single boolean: {verified: true} or {verified: false} . That works for the buyer's first-glance UX. It does not work for a regulator or a court trying to figure out what actually went wrong. An older trust-data-infrastructure design we read for context lays this out: their verify can return Valid Document, Invalid Signature, Incorrect Hash, Invalid Receiver Public Key, or Valid Document (Adulteration Not D