The Engagement Bus goes cross-product: Claim Your Gold’s growth engine reports to the network
Crew milestones, referral conversions, and D30 retention from Claim Your Gold now flow into FlashyOS’s cross-org Engagement Bus — pseudonymized, no PII.
Two products, one record
Claim Your Gold runs a complete viral-growth engine: crews that unlock bonuses at member milestones, a golden-invite referral system, and a deep day-30 retention program. As of July 17, its three canonical outcomes — crew_critical_mass_reached, viral_share_converted, and d30_retention_hit — report into FlashyOS’s cross-org Engagement Bus at the moment they really happen.
The privacy posture is strict by construction: subject identifiers are HMAC-pseudonymized before anything leaves the producing system, event metadata carries only the fields the shared vocabulary defines, and the vocabulary itself is a published contract. FlashyOS never receives, and cannot reverse, a raw user identity.
The part we corrected in public
Getting here included fixing our own record: at one point the docs claimed these events were already flowing when the emitting code did not exist. That is exactly the failure mode this product exists to prevent, so the docs were corrected, the events were then built for real, and the correction history stays in the repository. The unfakeable-record pitch has to apply to us first.
Frequently asked
No. Subject identifiers are HMAC-pseudonymized with a key only the producing org holds before any event is sent, and event metadata is restricted to a published, PII-free vocabulary.
Three network-visible event types: crew_critical_mass_reached (a crew hitting a 5, 10, or 20 member milestone), viral_share_converted (a referral conversion), and d30_retention_hit (a user reaching day 30).