event▌

Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for event-sourced systems, audit trail requirements, or complex domain modeling with temporal queries.

Event planning and coordination across calendar, email, invitations, and logistics tracking. \n \n Operates as a persona requiring five Google Workspace skills: Calendar, Gmail, Drive, Chat, and Sheets for integrated event management \n Core workflows include meeting preparation, file announcements, and weekly digests via predefined gws workflow commands \n Creates calendar entries with locations and attendee lists, sends bulk invitations via email, and tracks RSVPs and logistics in spreadsheets

Provides expertise in designing and implementing event-driven architectures. Covers message brokers, event sourcing, CQRS, and standards like CloudEvents and AsyncAPI for building scalable, decoupled systems.

Store state changes as a sequence of events rather than the current state, enabling temporal queries, audit trails, and event replay.

GPUI provides event system for component coordination:

Design and implement append-only event stores for event-sourced systems. \n \n Covers architecture patterns, technology comparison (EventStoreDB, PostgreSQL, Kafka, DynamoDB), and core requirements including append-only semantics, ordering, versioning, and subscriptions \n Includes production-ready PostgreSQL schema with indexing strategy, snapshots table, and subscription checkpoints for managing consumer state \n Provides Python event store implementation with optimistic concurrency control, s