Production custody verified and actual local compensation lifecycle completed
Coordinator 01a0e095-f279-7fd0-a8ef-92ce8f9547fc/local verified a new bounded Platform production diagnostic and the actual isolated compensation lifecycle. ADR-0048 remains open. These results do not authorize treating local workload models as production identity, or the diagnostic writer as the actual business-serving database role.
Platform production diagnostic
The reviewed diagnostic source 4d135338d2008def950453fd4383a8f6c0691fbd fixes the Next 16 empty POST stream rejection with a bounded zero-byte reader. Null or completed empty streams are accepted; nonempty, stalled, excessive-read and aborted streams are denied. All origin, deployment, source, credential, immutable approval and single-use reservation checks remain. The actual Node HTTP to Next adapter proof passed against a fresh local PostgreSQL database, including eight negative cases. Both diagnostic and cleanup candidates passed 515 unit tests, 32 identity and three geography scenarios, typecheck, lint and guardrails. Diagnostic CI 37103512282 and cleanup CI 37103793879 passed.
Diagnostic deployment dpl_88REhGGDSSsgrL4FPBWbPLUV8EP8 reached Ready off the canonical alias. Its two temporary production project settings were verified by exact created IDs and deleted before promotion. Window bd6ba3c2-98ba-4359-8749-5f4bc9eb6c1d made exactly one authenticated POST after deliberate promotion. HTTP 200 with no-store returned all thirteen fixed comparisons true: public/private pairing, key ID, issuer, JWKS URL, default audience, proof issuer/audience, Delivery proof subject, runtime and direct schema, exact direct approval, database name and Platform migration-journal presence. Independent readback found the immutable approval and the reservation bound to the exact deployment. No business endpoint, migration, token issuance, key rotation or financial operation was part of this diagnostic.
Cleanup source 78290b38f1ab49a7e54b41de9ad8263faf337cbf was built before the diagnostic invocation and immediately promoted afterward as dpl_BpNjgi9ohaskNdkh8uh4NAtGJJ82. It is Ready on platform.sguildswim.com. Source and runtime verification confirm the temporary route is absent, canonical POST returns 404, custody project/runtime settings are absent and the public key is unchanged. ADR-0049 person resolution remains enabled, all four new scheduling flags remain absent/default-off, and automatic production domain assignment is true. Both builds used npx prisma generate && next build; 223 diagnostic and 225 cleanup build-log entries showed no migration execution. Main was not merged and Render was not changed by this operation. The retained diagnostic generated URL returns deployment-protection 302, not handler 404; its approval expires at 2026-10-03T06:46:21.853Z and its single-use reservation is consumed. Earlier failed windows and approvals remain intact and are not retried.
Root evidence is .tmp/adr-coordination/ADR-0050/production-custody-012/{operation,approved-plan,diagnostic-result,cleanup-verification}.json in the primary Platform checkout. Owner source and validation are under .cache/adr0050-platform-012/docs/adr0050-production-auth-012/. Draft Platform PR https://github.com/sguild-admin/platform/pull/1 retains the reviewed source history. This closes the fixed custody/configuration and runtime/direct audit-binding diagnostic gap, while actual Sales production workload acquisition and closure exchanges remain separate gates.
Actual local compensation lifecycle
The third prospective Sales admission 43a97f2f-391c-4cc7-9086-8ac620ad9290 created genuine Revenue intent 29be0505-de11-4891-8fe2-d51bd0fd0f63 and Delivery lesson les_01a1004d-7cbd-71a4-b592-13557ca1813f. Actual bind, deliberate successful-response loss, exact replay and settlement preceded compensation. Delivery source 07ec0074708bac2dd345156b13eecc72a19f44f9 committed one operational cancellation and release, preserving the original booking blocker at compensating revision 1. The original lock's NULL quantity mirror remained unchanged; Revenue's canonical immutable quantity is one.
The first Revenue writeback rolled back because the bundled dispatcher schema lacked the already accepted failed_close_compensation reason. Explicit Revenue and Delivery ADR-0006 acknowledgments were published in 731a77afb1900f905b2f7953e19992ed6f3d822b. Platform source 57f7e2b584eb6ab6fb66dfeb8e9fa2394ada85ff bundles the accepted schema as dispatcher 2.0.3, with 509 unit and 35 integration checks plus actual packed-validator proof. Draft PR https://github.com/sguild-admin/platform/pull/2 records this narrow change. Exact local tarball SHA256 66b8382e302dbf440831341cf6341d492b4041c85fb934f29572ec7e3aac4731 passed Revenue's 908-test suite at f0d303c372f91bec6fb1abdb8d75397be2144d6b. Public npm publication remains blocked by E401 pending operator login; local package installation is not registry publication.
Using the retained compensation receipt, Revenue committed exactly one credit.released and one order.updated, both correlated to original bind event evt_01a10061-14a2-72a1-b6e5-89c10f0b19c1. Reservation is RELEASED with PENDING_FUNDING, order CANCELED and continuation abandoned. Ledger entries, balance and provider attempts remain zero. Writeback digest is ddf5067077358390cb0ded04ca654363228bd30502cb2558f700c0b2247c274d. No second Delivery compensation request was needed.
Real finalization command 5eb2fd15-a206-4143-88dd-0a2c888498e3 was allocated and paused before transport. A reviewed isolated deferred latency hook targeted only this exact command and association. The actual handler reached SET CONSTRAINTS ALL IMMEDIATE, and PostgreSQL canceled it with SQLSTATE 57014 under the remaining 9409 ms timeout. Actual statement duration was 9426 ms. All protected business facts remained equal before and after rollback, retaining revision 1 with no finalization. The same canceled backend successfully executed two ROLLBACK statements. A later SELECT 1 succeeded on a different backend after idle pool expiry; this proves subsequent pool usability, not a same-backend SELECT. The hook and function were removed, and the original 41 functions and 158 triggers retained identical hashes. Negative proof SHA256 b8afaa238cac97b5b2a7b942fa90a51dc25263d605ebfddb8a71e193215adf05 and removal proof f155f6ae8643e4efbebe5091743783d64da9d8145546ec267c4b501a8c5c4428 preserve that boundary.
The positive retry used the same actual wire SHA256 3a25e40d7a63d409b955861fbcb3ed6f2536730d8a27fa98f24e361682db362a and immutable command/key. The earlier prepared handoff used a different JSON property order, explicitly retained as preparation provenance rather than wire equality evidence. HTTP 200 committed exactly one finalization command and audit, retired protection at revision 2, and retained original response SHA256 5d79d9cab8118b9a358e3e616497eb6223c6e24ec4dc09c9e09c779bb5aeaea5. Delivery independent PostgreSQL snapshot SHA256 5649983c7f80c2da03bab9cf42e1fe54ee295f71627c2135e4795efaa52f39d8 confirms unchanged lesson, lock and event facts from revision 1. Platform independently matched both negative and positive fresh issuance request IDs and JTIs to one audit each, confirmations b53eb17bb9504caefd54f713bd23906fc5fcc59f44a886ba37fe0b2359b37812 and 184e89bb53bacfa3ddd26a5864e9dbf4f9abcf41dc7e85c96d589a024bbe9b27.
Coaching's actual complete active read returned empty at epoch 3/revision 86, then its required exact-original read at the same clock confirmed retired revision 2 before reopening October 10 16:00 to 16:30 UTC. Its durable record remains at generation 10, preserving the original booking, ZIP and location digest. Checkpoint SHA256 ff93e6964d0bb59a8f3a2178d165224a3310784215db8fb781dedc99574828a0 closes the actual local g0/g1/g2 consumer gap for this tuple. This does not establish ordinary-booking projection coverage or production workload identity.
Sales' exact retired-compensation consumer check is now active against this real original and the same owner databases. The never-admitted D1/Revenue/D2 procedure is not a new soft-expiry requirement for this already committed compensated original. Overall owner commitments remain working until their stated implementation and release gates are met. Actual production workload exchanges, serving-role privilege verification, compatible migrations and writer drain, provider Sandbox validation, package publication and controlled activation remain open. ADR-0052 and ADR-0053 deprecation deadlines are unchanged.