Loop → LoudCrowd Returns Feed (contingent)

What & why

If the LoudCrowd v5 refund audit shows Loop refunds already reach LoudCrowd via Shopify, this is never built. If gaps exist: a scheduled Worker reads Loop returns and submits signed events to LoudCrowd's Events API so creator commissions get docked correctly for refunds. No chat interface, no human hands on the write credential.

The plan — step by step

1. Triggered only by a failed refund audit in the LoudCrowd v5 project
2. David creates a write-scoped token (used solely as an HMAC signing key inside the Worker)
3. Cron Worker: Loop returns → idempotent refund events → Events API; every event logged
4. Verify commission adjustments appear in LoudCrowd; monitor for a month

Reasoning & trade-offs

Related material

Hub — Loop Returns guide