System Overview

What this platform is

• Privacy-first community analytics on Cloudflare Workers.
• Beacon Pulse (production): ingest WhatsApp exports, generate daily/weekly summaries, serve public APIs and embeds.
• Beacon Search (planned): RAG over community documents.

Sources: beacon-platform/README.md, beacon-platform/docs/architecture.md

---

Service directory

Service	Purpose	Tech stack
Beacon Pulse	Ingest exports and publish public summaries	Workers + D1 + R2 + Queues + Workers AI
Beacon Search (planned)	RAG over community docs	Planned (no production code yet)

Sources: beacon-platform/README.md

---

System context diagram

flowchart LR
  AdminUser -->|/admin| PublicWorker
  PublicWorker -->|/upload,/files| IngestWorker
  IngestWorker -->|PUT export| R2
  R2 -->|ObjectCreated| Queue
  Queue --> IngestWorker
  IngestWorker -->|digests/summaries| D1
  IngestWorker -->|AI calls| WorkersAI
  PublicUser -->|/pulse*| PublicWorker --> D1
  PublicWorker -->|fonts| GoogleFonts

Sources: beacon-platform/docs/architecture.md, beacon-platform/AUDIT_REPORT.md

---

Primary data flow

1. Admin uploads a WhatsApp export via /admin (public worker) which calls ingest endpoints.
2. Export is stored in R2 and a queue message is emitted.
3. Ingest worker parses, deduplicates, and generates daily digests.
4. Weekly summaries are generated from daily digests and stored in D1.
5. Public worker serves aggregated summaries via JSON and HTML endpoints.

Sources: beacon-platform/docs/architecture.md, beacon-platform/docs/operations.md

---

Navigate this vault

Folder	Purpose
overview	System-wide overview and decisions
platform	Shared contracts (security, privacy, API, ops)
services	Per-service docs
releases	Release notes