amplifier-philosophy

Mechanism vs policy separation in modular software design isolates core operations (mechanism) from decision rules (policy), enabling independent evolution of system components. This Skill uses a Linux kernel metaphor to guide these module boundary delineations, ensuring clean interfaces and maintainable architecture.

Event-first observability is an architecture principle ensuring system behavior is externally observable through discrete events. This Skill encodes this principle using a Linux kernel metaphor to guide architecture decisions, ensuring modular system components communicate state changes transparently and enabling reliable auditing.

Defining module boundaries using a Linux kernel metaphor involves treating core operations as kernel mechanisms and external rules as policies. This Skill provides actionable guidance for delineating these boundaries in Amplifier-like projects, ensuring clean separation of concerns and enabling regeneration-based design.

Text-first contracts in module design enable easy regeneration, auditing, and collaboration by using human-readable formats for module interfaces. This Skill incorporates text-first contract principles to ensure event-driven system components maintain clear, accessible communication standards across Amplifier-like architectures.

This kernel-inspired design philosophy applies to architecture planning for any modular software system requiring mechanism vs policy separation. While designed for Amplifier-like projects, its core principles of event-first observability, text-first contracts, and regeneration-based design translate to similar kernel-inspired architectures.

A Linux kernel metaphor for system architecture planning may not suit projects lacking clear mechanism vs policy separation requirements or systems not requiring regeneration-based design. This Skill's philosophy targets modular, event-driven architectures and may be excessive for simple, monolithic applications without strict boundary delineation needs.