Assignment ADR-0053/delivery/009, coordinator 01a0e095-f279-7fd0-a8ef-92ce8f9547fc/local. Delivery prepared the distinct executable/profile and recovery packet requested after root accepted008 local evidence. No new production credential, role activation, env, deployment, approval/window, signing key or proof request was created. Exclusive new claim directory remains absent. Future Phase B remains held pending separate root authorization. No Phase C or business/recipient call occurred. Root remains sole canonical publisher/indexer.
Prepared executable and evidence
Review packet docs/adr0053-workload-proof/review/observable009-executable-packet.json SHA256 757ecc6b44797d96456ac9ca5050127589f881fbb8e14df5fc0b97551659acb2 pins33 files. New entry custody-observable.mjs SHA256 b4e7ab8fe529c08b83566b5b402aa52e18d27ecaf3fb535b40370b13695e2b18; new profile SHA256 2e5f0ae10156353d2a77b61f93c0cc0bdad98c80d103868b6fb69370d4fa28ec. Recovery instructions are docs/adr0053-workload-proof/orchestration/observable-one-attempt-recovery.md.
The profile binds diagnostic source5f9ea287c19e5d9466f6b85eea362302f9f33eb9, manifeste2fdd3e9d91f499d53e1c10765e4795029562e56ef3e99c21680db9732c604f6 and owner writer2e447d0613ad40fcbba04a05d8885e27e02c208302838c3fb3dfd8abe53aadd0. Cleanup remains exact READY6kMS/source5c36/manifest1540b1. Old f48 custody and its profile remain unchanged; c9 is UNKNOWN/404 and is never reused.
New custody preserves verified direct/pooler CA/TLS, one credential with fifteen-minute server expiry, exact role OID13362275, role privilege and five-denial checks, known PID/backend-start session drain, authoritative env-ID journal, and remaining-lifetime gates. Native Linux artifact checks validate all regular sizes/hashes, literal link targets and real containment before activation. Full paginated alias readbacks and actual observed default aliases bind every restore to its exact prior deployment under explicit team scope. Unknown effects stop. Promotion/restore intents precede provider calls; uncertain operations cannot be blindly repeated. Read-only cleanup reconciliation is available.
Encoded approval span is at most120 seconds. One-attempt persistence precedes writer spawn. Nested finally paths always attempt cleanup and role revocation. STOP blocks further provisioning/signing/invocation; exit requires revoked role, removed envs, reconciled cleanup aliases and checked expiry. No replacement signature, credential extension or second acquisition is allowed.
Validation:80 focused tests pass, including actual entry stop/recovery/exit paths; native contained artifact and three denial fixtures pass; both complete native artifact scans pass (new572 regular/119 links, cleanup508/118). Delivery npm test passes996 with15 skipped, plus8 audit unit tests; typecheck passes. These local results do not attest a deployed workload, production TLS proof, epoch/resource or financial readiness.
Separate authorized retirement completed
Only dpl_aDWLBjzq5d72EtCoHavVHub8k6dR was removed, after fresh original c9/provider pins, expired approval, closed custody, revoked role/zero sessions, all five aliases and exact READY cleanup checks. Intent was recorded before the sole explicit-team safe removal. CLI exited0; exact deployment GET returned404 at2026-10-03T10:13:11.915Z. All alias targets stayed unchanged; cleanup GET returned200/READY and remained canonical. Original evidence remains preserved and original outcome remains UNKNOWN.
Separate disposition and role/baseline readback are results/2026-10-03-exact-diagnostic-retirement-disposition.json and results/2026-10-03-exact-diagnostic-retirement-readback.json under the workload-proof folder. Final readback SHA256 is 6262f704bda8ad2eb56b1d51a257c6f0d89b23e4954ef3cce790d870ecd4be12. The008 outbound memo with SHA256c07f08632593e8c936b72aae040a99bde569f8c2dab3c4eda605e10093a58187 remains unchanged for root publication. All outstanding ADR production and financial gates remain open.
Actual cron parity and preservation
At2026-10-03T10:26:51.294Z read-only provider checks establish project crons enabledAt1777675566542, disabledAt null, exact five source definitions and binding to cleanup6kMS. Exact cleanup deployment metadata and both actual Build Output config.json files contain the same five definitions. Evidence is results/2026-10-03-observable-cron-parity.json. Earlier retained provider metadata did not retain cron fields, so historical continuity is unproven. No cron repair occurred. New preflight and staging guards require this parity; business checks pin full expected cron metadata. Promotion allows only deployment ID, exact hosts and updatedAt changes. Cleanup restores original deployment/hosts and preserves all enabled/disabled/definition fields. Unexpected effects STOP; recovery checks exact cleanup metadata before accepting reconciliation. Two added guard tests cover disabling, missing definitions, changed enabledAt, wrong hosts and extra fields.