Designs

Designs

Purpose

Design pages describe how WiSave.Expenses is built and why the major boundaries exist.

Use this section when the reader needs to understand architecture, event-sourcing mechanics, aggregate boundaries, projection behavior, or durable technical decisions.

Pages

• Architecture Overview - service shape, executables, class libraries, persistence boundaries, and main runtime flow.
• DDD And Aggregates - aggregate pattern, current aggregate roots, domain state, lifecycle states, and command/event surface.
• Event Sourcing And Event Flow - command-to-event and event-to-projection behavior.
• End To End Command Event Flows - hub for lifecycle-level command and event flow pages.
• Read Model Projections - projection runtime, handlers, read-side state, and replay considerations.
• Business Decisions - durable decisions that explain current architecture and compatibility constraints.

Placement rules

• Put current system design, component boundaries, and runtime behavior here.
• Put feature-specific business behavior in Features.
• Put step-by-step operational or developer instructions in Guides.
• Put mandatory practices in Standards.