architecture-guard

Reject design proposals violating the Source of Truth in architecture reviews.

2|Updated Jan 2, 2026

Search Tags:#architecture #validation #backend #event-driven #design-review #ledger #source-of-truth

Ready to run

npx skills add https://github.com/abdullahbokl/Boklo-Wallet --skill architecture-guard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-guard
Source: https://github.com/abdullahbokl/Boklo-Wallet/tree/main/.agent/skills/architecture-guard
Command: npx skills add https://github.com/abdullahbokl/Boklo-Wallet --skill architecture-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces Boklo Wallet’s backend-authoritative, event-driven architecture. Prevents designs that violate the single source of truth and ensures backend validation governs financial state.

Core Features & Use Cases

Enforces the Backend-Authority principle across proposals and feature designs.
Rejects any client-side writes or ledger mutations that bypass backend validation.
Provides compliant alternatives that route actions through events and backend validation, preserving data integrity.

Quick Start

Submit a design proposal and ask Architecture Guard to verify alignment with the Source of Truth.

Frequently Asked Questions about architecture-guard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate backend architecture for financial transactions?▼

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.

What is a backend-authoritative event-driven architecture?▼

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.

How do I prevent client-side state mutations in an event-driven system?▼

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.

Does event routing require backend validation for ledger write boundaries?▼

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.

How do I review design proposals for source of truth violations?▼

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.