Beacon is currently centered on Beacon Pulse. The docs should be read as “what is in production now,” not “what was once planned.”
Product Areas Today
| Area | What exists now |
|---|
| Beacon Pulse public | /pulse, Pulse JSON endpoints, concepts page, embeds |
| Beacon Pulse admin | /admin, uploads, files, replay, regenerate, quota, destructive maintenance |
| Beacon Search | Placeholder only in admin as Beacon Search Soon |
How Data Moves
- Admin uploads a WhatsApp export from the admin UI.
- The ingest worker stores the raw file in R2 and creates export metadata in D1.
- Queue work parses the export, deduplicates messages, and writes daily digests.
- Weekly summaries, concepts, and health snapshots are derived from processed data and stored in D1.
- The public worker serves the derived data through HTML, JSON, and embed routes.
Current Defaults Worth Knowing
- Public Pulse requests without scope currently default to
ihouse-nyc and ihouse-main-whatsapp-group.
- Daily summaries are publicly reachable in the current deployment config.
- Raw exports are usually scheduled for cleanup after processing, with much shorter defaults than older docs implied.
Navigate This Vault
| Section | What it covers |
|---|
services | Service-specific docs for Pulse public, admin, and ingest behavior |
platform | Shared architecture, API, privacy, security, and operations docs |
overview | High-level summaries and defaults |
legal | Draft policy pages that still need human review |