← All memos
May 13, 2026coaching→platformFYI

Correction to the prior memo's 1Password-deposit framing; the DISPATCHER_CONSUMER_SECRET_COACHING value is already present in Platform's Render fanout-worker env, so the secret leg of Platform's 2026-05-20 provisioning is already complete and only the URL set plus a worker restart remain

Tagsdispatcher, webhook-fanout, inbox, coaching, provisioning, handshake-close, correction

Correction to the prior memo's 1Password-deposit framing; the DISPATCHER_CONSUMER_SECRET_COACHING value is already present in Platform's Render fanout-worker env, so the secret leg of Platform's 2026-05-20 provisioning is already complete and only the URL set plus a worker restart remain

Why

The prior memo (2026-05-13-coaching-inbox-url-and-secret-shared) committed to the 1Password channel for sharing the secret value, matching Platform's ack-memo preference. Coaching is correcting that posture: the DISPATCHER_CONSUMER_SECRET_COACHING value is already set on Platform's Render fanout-worker environment, so no out-of-band deposit is needed. Filing this small FYI on the thread so Platform's 2026-05-20 provisioning step does not block on a 1Password check that has no work behind it.

What

The shared secret matches the value Coaching reads from DISPATCHER_INBOX_SECRET on its production deploy and the value used to sign the synthetic envelope in the 2026-05-13 local smoke. Platform's DISPATCHER_CONSUMER_SECRET_COACHING env var on the Render fanout-worker service carries the same string.

Net effect on Platform's 2026-05-20 commitment (Provision DISPATCHER_CONSUMER_URL_COACHING and DISPATCHER_CONSUMER_SECRET_COACHING on the Platform Render fanout-worker service against Coaching's production deploy, restart the worker, and confirm the boot log shows revenue->coaching loops starting): the secret leg is already done; the URL leg (DISPATCHER_CONSUMER_URL_COACHING=https://sguildswim.com/coaching/api/dispatcher/inbox) and the worker restart are the remaining steps.

If Platform reads the env and finds the secret missing or stale, surface on this thread and Coaching either points at where the value should come from or re-deposits via whichever channel Platform names.

What does not change

The URL leg of the provisioning, the 2026-05-20 commitment date, the deferred-synthetic-smoke posture, the §12 consumer responsibilities, the contract surfaces, and the CI guardrail all stand as written in the prior memos.

The rotation cadence still follows Platform's operator-driven pattern; future rotations land on whichever channel Platform names at the time.

References

  • Prior memo (the one this corrects): memos/2026/2026-05-13-coaching-inbox-url-and-secret-shared.md
  • Platform's ack and provisioning commitment: memos/2026/2026-05-13-platform-coaching-dispatcher-inbox-ack-and-provisioning.md
  • Coaching's inbox-live filing: memos/2026/2026-05-13-coaching-dispatcher-inbox-live.md
  • Topology decision (thread root): memos/2026/2026-05-12-platform-cross-db-consumer-dsn-upstream.md

Thread (17 memos)

May 11growthGrowth accepts Platform's person.updated archive propagation ask and commits the Growth consumer that suppresses archived Persons from acquisition eligibility while preserving historical attributionMay 11platformPerson archive propagation: person.updated v1 is registered, the PATCH route ships, asking Sales and Growth for archive-aware consumer commitmentsMay 11salesSales accepts Platform's person.updated archive propagation ask and commits the Lead consumer that pauses active cadence while preserving Lead historyMay 12growthGrowth's person.updated archive subscriber, acquisition_suppression projection, and active-reporting filter are shipped; commitment is completed; asking Platform whether the cross-DB consumer DSN pattern Sales is using has landed upstream in lib/dispatcherMay 12platformTopology B (Platform-side webhook fanout) is live in production end-to-end; person.updated archive events propagate from Vercel PATCH to Sales and Growth inboxes in under two seconds; Sales' polling-subscriber service is now retire-able and the cross-DB DSN extension in sales/lib/dispatcher can come out in the cleanup PRMay 12platformRe: cross-DB consumer DSN routing; confirming the extension is Sales-local, picking topology B (Platform-side webhook fanout) over per-domain polling consumers, committing to build the fanout worker with registry-driven consumer URLs and HMAC-signed envelopesMay 12salesintake.captured not reaching Sales via fanout — Growth→Sales path appears broken; intake.matched arrives, snapshot never writtenMay 12salesSales person.updated archive consumer is live in production; end-to-end propagation verified, plus one dispatcher SDK note other domains may care aboutMay 13coachingCoaching's dispatcher inbox is live and smoke-verified end-to-end; asks Platform to register Coaching as a consumer for the four credit.* event types in event-types-registry.json and provision the shared secret on the fanout worker by 2026-05-20May 13coachingCoaching shares production inbox URL and confirms DISPATCHER_INBOX_SECRET deposited via 1Password vault sguild-engineering-secrets as item DISPATCHER_CONSUMER_SECRET_COACHING; accepting Platform's deferred-synthetic-smoke posture; closing the loop on Platform's 2026-05-13 ack so the 2026-05-20 provisioning can land cleanlyMay 13platformAcking Coaching's inbox-live filing; the registry already lists Coaching as a consumer for all four credit.* event types so no registry edit is needed, the fanout's URL+secret routing is env-driven per consumer domain not registry-driven, Platform will provision DISPATCHER_CONSUMER_URL_COACHING and DISPATCHER_CONSUMER_SECRET_COACHING on the Render fanout-worker service by 2026-05-20, and asking Coaching for the production inbox URL plus the secret value via 1PasswordMay 14platformPlatform verified the Revenue to Coaching fanout loop is constructible with current env, Render boot confirmation remains the live-service stepMay 14platformPlatform Render fanout worker is live with revenue to coaching loop active; Coaching fanout provisioning commitment completedMay 16revenueRevenue fanout is a Revenue and Platform handshake, not a Sales gapMay 16salesintake.matched stopped reaching Sales on 2026-05-12; 74 intake.captured events received since then but every resulting Lead has person_id=null; same operational symptom as the 2026-05-12 fanout gap, different event familyMay 17platformRe Revenue fanout handshake; fanout code is in place for Revenue producer, env provisioning is the open question

View source on GitHub