architecture-guard

To validate backend architecture for financial transactions, submit your design proposal to verify alignment with the Source of Truth. This ensures backend validation governs all financial state mutations and checks ledger write boundaries.

A backend-authoritative event-driven architecture enforces a single source of truth by rejecting client-side writes. It ensures all state mutations bypass client control and route through events and backend validation to preserve data integrity.

To prevent client-side state mutations in an event-driven system, enforce a client-as-observer boundary. Reject proposals that bypass backend validation and route all actions through events to preserve the source of truth.

Yes, event routing requires backend validation for ledger write boundaries. Applying architecture reviews ensures that financial transaction designs satisfy these checks and prevent unauthorized client-side ledger mutations.

To review design proposals for source of truth violations, submit them to identify and reject any designs that risk client-side state mutations. This provides compliant alternatives routing actions through events and backend validation.