Skip to main content

WhatsApp Event Submission MVP Phases

Last updated: May 12, 2026

Current position

The WhatsApp Event Submission MVP planning and implementation stack is complete through W9.

W1 through W9 established the runtime decision, schema, ingestion, outbound follow-up, evidence validation, candidate mapping, moderator recommendation model, shared connector interface, both dry-run calendar connector packages, hosted-dev smoke coverage, the operator runbook, the WhatsApp change request workflow design, and direct-write verification guardrails. Issues #86 through #106 are closed, and milestones W1 through W9 are closed.

Direct/live calendar writes remain disabled. Future live connector work should wait until a disposable staging target and scoped staging credentials are available for credentialed create/update/rollback tests.

Phase status

WaveFocusIssuesStatus
W1Architecture decision and tracker docs#86, #87Complete, merged to main
W2Source tracker schema, state model, routing, PII boundaries#88, #89, #90, #91Complete, merged to main
W3WhatsApp validator, webhook ingestion, outbound follow-up#92, #93, #94Complete, merged to main
W4Extraction, question generation, evidence URL validation#95, #96, #97Complete, merged to main
W5Candidate mapping and moderator recommendation snapshot#98, #99Complete, merged to main
W6Connector foundation and dry-run downstream packages#100, #101, #102Complete, merged to main
W7Smoke coverage and operator runbook#103, #104Complete, merged to main
W8Design change request workflow#105Complete, merged to main
W9Direct write capability verification#106Complete, merged to main

Completion note

Issue #106 adds the GLD direct write capability verification. The verification records read-only public REST discovery for GoLatinDance TEC and MiGente EventON, confirms no staging credentials were available, and keeps direct/live writes disabled.

Next step

Do not add live connector implementation issues until a disposable staging target and scoped staging credentials are available for credentialed create/update/rollback tests. The next active repo work is outside the WhatsApp stack: finish the remaining GLD Phase 5 hosted-dev/access documentation PRs, then continue the Phase 6A cloud source ingest lane.