Status: IN
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.
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"
Depends on (SL): s3-get-returns-none-for-missing, maps-no-exceptions-none-returns