Beacon Pulse is the live Beacon product today: a public community-weather dashboard plus an admin workspace for uploads, repair workflows, and system operations.
What Exists Today
- Public Pulse at
/pulsewith the tabsThis Week,History,Daily,Trends, andConcepts - Public JSON endpoints for weekly summaries, history, daily summaries, trends, concept graphs, communities, sources, and embeds
- Admin workspace at
/adminfor uploads, file management, regeneration, replay, quota controls, and destructive maintenance - Separate ingest worker for uploads, queue processing, media analysis, replay, backfill, and scheduled self-healing jobs
- A
Beacon Search Soonplaceholder in admin, but no working Search product flow yet
Practical Architecture
- An admin uploads a WhatsApp export from
/admin. - The ingest worker stores the raw file in R2, creates an export record in D1, and enqueues processing.
- Queue workers parse the export, deduplicate messages, generate daily digests, and create weekly summaries when thresholds are met.
- ZIP uploads can also create media-analysis work for images, audio, and sampled video frames.
- The public worker serves the derived data through
/pulse,/pulse*.json,/pulse/concepts, and/pulse/embed.
Current Caveats
- The public UI currently shows an
Under Constructionbanner and warns that recent daily summaries may be incomplete while processing catches up. Beacon Search Soonis a placeholder, not an active feature area.- Daily summaries are currently public because the checked-in public worker config sets
PUBLIC_DAILY_DIGESTS=true. - Raw exports are not kept indefinitely by default. When delete-after-processing is enabled, the ingest worker targets cleanup after 72 hours for completed exports and 168 hours for failed exports.
- Replay from raw exports only works while the original raw object still exists in R2.
Guides
Verified against beacon-platform/apps/pulse-public/src/index.ts, beacon-platform/apps/pulse-ingest/src/index.ts, and the rendered UI on April 22, 2026.