inter-invariant

Cross-aggregate consistency is enforced by coordinating domain events between publisher and consumer aggregates to prevent conflicting outcomes. This approach uses inter-invariant patterns to ensure a consumer's invariant holds after a publisher event.

Coordinating sagas and TCC workflows with domain events requires shared event classes, subscriptions, and command handling. This implementation models cross-aggregate policies to track state and manage command flows across publisher and consumer aggregates.

Cross-aggregate invariants are needed in event-driven architectures to ensure domain events across multiple aggregates are coordinated to avoid conflicting outcomes. They enforce policies such as ensuring a consumer's invariant holds after a publisher event.

Implementing inter-invariant patterns involves wiring event subscriptions and adding required handlers, commands, and sagas. You review the SKILL.md, implement the subscription wiring, and follow repository examples for the quizzes module.

No specific dependencies are required to model cross-aggregate policies with sagas. The implementation relies on shared event classes and command flows within the module to coordinate event subscriptions and state tracking.