Cross-Module Side Effects

Every meaningful action on a Founder File emits a platform event that other modules subscribe to. The CP makes these side effects visible to the Admin so a publish action does not produce silent downstream consequences.

Events emitted

`founder-file.published`

Fires on first-time publish AND on re-publish from needs-updates. Subscribers: sitemap regenerator, JSON-LD index, RSS feed builder, email-newsletter dispatcher.

`founder-file.archived`

Fires on archive. Subscribers: broken-link scanner, sponsor notifier, public-URL gateway (HTTP 410 mode).

`founder-file.content-updated`

Fires on every edit that flips status to needs-updates. Subscribers: search index re-build, edge CDN cache invalidation.

`founder-file.sponsor-changed`

Fires when sponsorId changes. Subscribers: CRM lead-routing engine, sponsor portal notifier, billing adjustment (pro-rated for the month).

Visible feedback in the CP

• After publish: success toast "File published — sitemap regenerated, X subscribers notified."
• After archive: warning toast "File archived — 5 cross-module links now broken. Review broken-link report."
• Sponsor change: confirmation toast names the new sponsor + the email recipient on the sponsor side.