Assignment ADR-0053/delivery/009, coordinator 01a0e095-f279-7fd0-a8ef-92ce8f9547fc/local. Root authorized one fresh bounded Phase B using reviewed entryb4e7ab8f, profile2e5f0ae1 and packet757ecc6b. Authorization is retained in Platform's .tmp/adr-coordination/ADR-0053/delivery009-root-review.json. Original c9 and every earlier claim/result remain unchanged. Root remains sole canonical publisher/indexer.
Original acquisition outcome
Fresh window a669d93a-1a6f-4249-8db8-642c9ec94331 used one fifteen-minute server-bound credential, actual same-credential direct/pooler verified-CA authentication and exact OID13362275. All five denial checks passed. Preflight verified original28 env/settings, native complete artifacts, full five aliases and enabled five cron definitions. Diagnostic dpl_13zDT8K69bqaenc4aAHbNmYb2j3p was READY at source5f9ea287c19e5d9466f6b85eea362302f9f33eb9 and all572 regular uploaded file IDs matched. Staging preserved aliases and cron bindings; all seven exact env IDs were removed before invocation.
Diagnostic promotion and expected alias/cron effects passed. The sole signed approval has nbf1791023613 and exp1791023733, total120 seconds. One owner approval row was written and exactly one acquisition POST occurred. Writer returned code1, passedfalse, unknowntrue, HTTP404 with bounded x-vercel-id cle1::iad1::82xkq-1791023624630-552d122f7faa. The retained read-only provider request log at2026-10-03T10:33:44.630Z records serverless/MISS, exact canonical POST and fixed stage sdk_integrity, outcome denied. No distinct request-ID header was recorded.
This narrows the deployed denial to SDK integrity. The underlying mismatch remains unknown. No reserved or completed audit row exists; SDK exchange, deployed restricted DB/TLS proof, workload/epoch/resource and production readiness are unproven. No retry, replacement signature, TTL extension, Phase C, Platform exchange or business/recipient call occurred.
Original result and provider log evidence: docs/adr0053-workload-proof/results/2026-10-03-observable009-original.json, SHA256 f50af35061e8edc8b81abd00bfdb9b4a01ec6779d77f35b4eca249f953d80228. It pins the untouched custody state, raw audit and provider captures separately from cleanup.
Separate cleanup and expiry
Exact READY cleanup dpl_6kMSVcQWqehL1sT6xAb78DjRrbPi, source5c36fd2021069d766b17f97032b4266c8d0b4f5a, was promoted once. All five original alias targets were restored. Provider cron enabledAt1777675566542 and disabledAtnull stayed exact; five definitions and original cleanup hosts/deployment binding were restored, with only provider-generated updatedAt changing. Fresh final read-only API checks verify Ready/source, all aliases, full cron metadata and original28 env/settings hashes. No cron repair was needed.
Exact role is NOLOGIN, passwordNULL, proof grants revoked and zero sessions, with creator/admin and PUBLIC baseline preserved. There were no unknown sessions or blanket drains. Canonical route returns404 both without and with the formerly approved header. Both retained URLs return302 protection redirects, which do not establish route absence there. Existing approval expired at2026-10-03T10:35:33Z and was checked at10:35:36.138Z. Normal custody exit returned0, closed pools and cleared live RAM keys/credentials. The new diagnostic remains retained; its deletion has not been authorized.
Separate cleanup evidence: docs/adr0053-workload-proof/results/2026-10-03-observable009-cleanup.json, SHA256 d1d388fed78b0874ae4bdd6b5bf483db46a65dd84000f3084d4d8a49ffb374d4. All production proof and financial/activation gates remain open. Any further work must preserve this completed claim and begin with read-only SDK integrity diagnosis, not another request.