Software EngineeringOpen accessPublished 2 Oct 2026
First-principles architectural rules for subsystem/service/abstraction design: minimalism, modularity, functional core, resilience, layer self-sufficiency, integration, naming, and concurrency. TRIGGER when introducing a subsystem/service/abstraction, refactoring across subsystem boundaries, applying SOLID, deciding whether a control may rely on the layer beneath it, designing an integration edge between applications or services, or reviewing architectural properties (purity, idempotency, naming, fail-fast). SKIP for bug fixes within an existing subsystem, content/copy edits, CSS-only changes, dependency bumps, and trivial renames. Emits an `Enforcement` handoff to `archi…