{"id":"none-return-collapses-distinct-failure-modes","text":"S3 and map routing both return None for all failure conditions (missing objects, unreachable destinations, unknown inputs), collapsing distinct error causes into a single sentinel value that simplifies callers but makes failure diagnosis impossible.","truth_value":"IN","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["s3-get-returns-none-for-missing","maps-no-exceptions-none-returns"],"outlist":[],"label":"S3 returns None matching HTTP 404 semantics; maps returns None for missing nodes, unreachable targets, and unknown geocodes — both APIs eliminate the need for exception handling but prevent callers from distinguishing \"not found\" from \"error computing result\""}],"dependents":["error-boundaries-are-module-local"],"metadata":{"last_reviewed":"2026-06-06T06:26:57","review_result":"pass"},"created_at":"","updated_at":"","reviewed_at":"","verified_at":"","retracted_at":"","explanation":{"steps":[{"node":"none-return-collapses-distinct-failure-modes","truth_value":"IN","reason":"SL justification valid","antecedents":["s3-get-returns-none-for-missing","maps-no-exceptions-none-returns"],"label":"S3 returns None matching HTTP 404 semantics; maps returns None for missing nodes, unreachable targets, and unknown geocodes — both APIs eliminate the need for exception handling but prevent callers from distinguishing \"not found\" from \"error computing result\""},{"node":"s3-get-returns-none-for-missing","truth_value":"IN","reason":"premise"},{"node":"maps-no-exceptions-none-returns","truth_value":"IN","reason":"premise"}]}}