Skip to main content

​
Summary

The onboarding assistant event catalogue — designed yesterday — was committed to choco-hq and immediately revealed a naming gap from the Wonka rebrand. Fixed the gap, then ran a full audit across all 20 GitHub organisations to find every repo affected by the new event system. Created 20 new issue tickets, updated 5 existing ones, and set up a Linear project with 6 milestones for the 8-week implementation.

​
Business impact

​
The event system is now the source of truth

52 events define exactly how onboarding, discovery, monetization, documentation, and compliance work across every Choco product. When a user starts onboarding, upgrades a tier, or redeems a Golden Ticket, every downstream system (billing, analytics, webhooks, search) reacts automatically. No more ad-hoc integrations.

​
Naming gap caught early

The recent Wonka-themed repository rename (ARCH-000) hadn’t been applied to the event catalogue. 34 references pointed to archived repos. Caught and fixed before any team started implementation — saving significant rework.

​
4 critical repos had zero tracking

The AI assistant (choco-assistant), observability stack, auth service, and MCP server had no issue tickets despite being core to the event system. The assistant alone handles 25 events. These gaps are now filled with structured EPICs linked to specific handoff contracts and SLA targets.

​
Cross-organisation alignment

Four repos outside choco-hq needed integration issues: the Kiln experiment engine (3 A/B test bindings), the Veritas prompt pipeline (fragment registration), the DDD event catalog (template import), and POSTIE (Wonka mythology arc alignment for campaign content).

​
Operational takeaways

  1. Linear project created — “Choco Event Catalogue Implementation” with 6 milestones targeting 2026-05-08 completion. 18 Linear issues mirror the GitHub issues for single-pane tracking.
  2. M1 is 50% complete — naming fix done, Protobuf definitions for 52 events are next (assigned to choco-contracts).
  3. Critical path: M2 (core producers) and M3 (core consumers) run in parallel weeks 2-5. The assistant and analytics pipeline are the highest-risk items — most events, most handoff contracts.
  4. Launch gate: M6 requires Grafana dashboards monitoring all 11 handoff contract SLAs before platform launch can proceed.

​
Action items

  • Begin M1 Protobuf definitions (choco-contracts#4) — blocks all downstream producers/consumers
  • Prioritise choco-assistant EPIC — highest event throughput, 5 handoff contracts
  • Schedule Kiln experiment binding review with cookr-hq (kiln#29)
  • Add post-rename CI gate: grep for archived repo names in architecture artefacts
See also: Technical detail