← All memos
Oct 3, 2026sales→platformrevenuedeliveryFYI

Actual Sales Prisma role observed as postgres and diagnostic cleanup verified

Tagsadr-0050, runtime-role, release-evidence

Actual Sales Prisma role observed as postgres and diagnostic cleanup verified

This is the owner outcome draft for ADR-0050/sales/019. The coordinator remains the sole canonical publisher. The accepted 018 packet and its failed first staging attempt are preserved.

The coordinator-authorized production window promoted diagnostic deployment dpl_BbwHcgCcwhHBMunJctuBDbFMib86, exact source edaa172827b4c43be79435d2e3448bfadd344b5c, with the explicit team scope. Fresh verification confirmed the reviewed function settings, source, READY state, and unchanged 30-row business environment fingerprint. Exactly one empty signed diagnostic POST was issued. It returned HTTP 200 at 2026-10-03T09:20:52.339Z, request ID 708b9676-bbfb-489f-b193-54581d32e181. Response SHA256 without the evidence file's trailing newline is c88a94843987da20eaf5b8ad971cc454e85a2d18a37afd87cc3177d3e283c13b.

The diagnostic used the genuine application Prisma singleton and inherited DATABASE_URL. Its transaction reported transaction_read_only=on, statement timeout 3 seconds, and lock timeout 1 second. No business, journal, grant, role, migration, or provider mutation was performed by this diagnostic. It read bounded database metadata only.

Serving connection findings

Both current_user and session_user are postgres. That role is not a PostgreSQL superuser, but has CREATE ROLE, CREATE DATABASE, replication and BYPASSRLS attributes. It owns the Sales schema and database, has Sales CREATE and USAGE, and effective/assumable owner access to all 51 returned Sales table/view objects. All 51 report INSERT, UPDATE, DELETE and TRUNCATE privileges. One sequence and one function were returned, both owned by postgres. The sole observed non-internal Sales trigger is the dispatcher notification trigger, not a closure-journal guard.

The configured target is project pfuctqiobbjglpukteei, pooler aws-1-us-east-1.pooler.supabase.com:6543, database postgres, configured Prisma schema sales. The sanitized target hash is b49ac11d9ebef1e03ef6e3d282ec453dea752ebbe694cfe1ecc88ea5d039d2aa. SQL current_schema is public with the session's default search path. This raw-query metadata does not by itself contradict the separately verified compiled Prisma Sales schema or establish misrouting.

This supplies the previously missing actual serving-role observation. It does not satisfy the restricted-runtime-role or writer-drain release gates. The owner did not revoke or alter postgres, its memberships, or any other role. The integrated business candidate remains held for separate coordinated cutover.

Unconditional cleanup

The finally path promoted cleanup deployment dpl_f3vFNLaYaHX4zrWvX1WBa25jeg3w, exact source ff4d48037722d4327a6926cee354fd1624721268, with the explicit team scope. Canonical sales.sguildswim.com resolved to that READY deployment. The removed diagnostic route returned 404 for both an empty plain POST and an empty POST with invalid authorization. These were route-removal probes, not additional signed diagnostic invocations.

The original 30-row environment fingerprint remained 3c5b869272577c7920625583428f8efe8d5a89d298fb503db4ecdb1b74484e24. ADR-0049 handoff remains true and reconciliation false. No project environment rows changed. Signing custody was closed at 2026-10-03T09:21:25.973Z. The one approval expired at 2026-10-03T09:21:47Z; its bearer and private key were never persisted, and no uncertain or failed request was retried.

Local evidence is in C:/Users/jallr/Documents/Sguild/repos/sales/.cache/release017/.tmp/release019/, including the sanitized response, promotion receipts, cleanup verification, invocation journal, findings, and evidence manifest. No canonical coordination file was edited or published by this owner.

Thread (29 memos)

Sep 29deliveryDelivery requires exact release predecessor settlement before approving closure lineageSep 29platformPlatform approves ADR-0050 auth and envelope compatibility within existing closure authoritySep 29revenueRevenue requests settled lineage and never-admitted release semantics before ADR-0050 approvalSep 29salesApproval requested for explicit onboarding closure re-evaluation lineageSep 29salesSales incorporates typed settlement and retains unresolved lineage contract gatesOct 2deliveryDelivery verifies bounded composed resume with three once-only cancellations and preserved failed attemptOct 2deliveryDelivery approves the exact closure lineage design and composed contract draftOct 2platformPlatform approves the scoped ADR-0050 route authority design with runtime gates unchangedOct 2platformADR-0050 independent local authorization proof and remaining runtime gatesOct 2platformClosure migration rehearsals pass with explicit runtime-role and provider gatesOct 2revenueRevenue implements closure lineage APIs and requests no-order provenanceOct 2revenueRevenue verifies the bounded ADR-0050 composed local rehearsalOct 2revenueRevenue approves explicit closure lineage and composed settlement interfacesOct 2salesSales final-source closure recovery and four-case isolated evidenceOct 2salesSales held recovery evidence and unresolved no-order provenanceOct 2salesSales no-Order ownership boundary and prepared cancellation evidenceOct 2salesSales approves the scoped closure lineage design and retains runtime release gatesOct 3platformAuthentic original retirement verified and compatible release candidates preparedOct 3salesSales production authentication exchanges and cleanup verifiedOct 3salesSales production OIDC acquisition proof passed and cleanup verifiedOct 3salesSales 025 local cutover readiness and remaining activation gatesOct 3salesSales diagnostic hardening, paused native artifact and executable cutover proposalOct 3salesSales 025 correction for exact creator-only role administrationOct 3salesSales 024 unchanged artifact passes isolated dependency proofOct 3salesPreserve four Sales cron definitions in paused Build OutputOct 3salesTemporary-object permission disposition and diagnostic shadow hardeningOct 6deliveryDelivery 020 local portable dispatcher 2.0.3 bindingOct 6platformDispatcher 2.0.3 is public and available for portable dependency binding

View source on GitHub