Model TypeScript system state as an append-only action log.
npx skills add https://github.com/AndreaCadonna/sbobuz-web-game-app --skill event-sourcing
Please help me install this Agent Skill. Skill: event-sourcing Source: https://github.com/AndreaCadonna/sbobuz-web-game-app/tree/main/skills/event-sourcing Command: npx skills add https://github.com/AndreaCadonna/sbobuz-web-game-app --skill event-sourcing
Event sourcing models state as a sequence of immutable events rather than mutable state, enabling a complete audit trail and deterministic replay for debugging and recovery.
Create an initial state, define a typed action log, and replay a sequence of actions to produce the final state.
High-intent search queries and answers about installing and using this skill.
To build an event sourcing system in TypeScript, model your state as an append-only action log using typed discriminated unions for actions. Use immutable reducers and a separate validator phase to guarantee deterministic replay outcomes and a complete audit trail.
The best way to structure reducers for an event-sourced game state is to keep them completely pure and immutable, separating validation logic from state transitions. This ensures the action log remains the single source of truth for deterministic replay.
You need snapshotting in an event-sourced state machine when managing scalable, long-running systems. Snapshots capture intermediate state to avoid replaying the entire action log from the beginning, significantly optimizing recovery and debugging processes.
Event sourcing works effectively with CQRS patterns in TypeScript workflows by maintaining an immutable action log as the source of truth. This combination provides a reliable audit trail and enables deterministic replay for complex state machines and workflow debugging.
Validation must be separated from reducers in a deterministic replay architecture to keep state transitions pure. If reducers handle validation, impure side effects break reproducibility, making the action log unreliable for audit trails and state recovery.
You can use event sourcing for workflow state management alongside game engines. Any domain requiring auditability, immutable state, and deterministic replay benefits from modeling system state as a sequence of typed events within an append-only log.
luyi985Model complex state logic using discriminated unions with literal tags.
justcoonSimulate agent crashes and verify recovery with the golem CLI.
mariotoffiaImplement CQRS with aggregates, domain events, and projections for read models.
pohlai88Stores state changes as a sequence of events for audit and replay.
