Making S.O.L.I.D. Principles Verifiable with AOK

For over 20 years, Robert C. Martin’s S.O.L.I.D. principles have been a guiding framework for software developers. However, adhering to these principles has always been based on trust and experience, with no way to objectively prove compliance. AOK (Architectural-Oriented Knowledge) changes that by embedding architectural intent directly into the code through structured metadata. This makes it possible to not only follow but also verify each of the S.O.L.I.D. principles. For example, AOK adds tags like @PURPOSE to clarify the Single Responsibility Principle and @ARCHITECTURE to show extension points for the Open/Closed Principle. The integration of AOK doesn’t replace S.O.L.I.D.; instead, it makes it possible to explicitly document compliance and ensure that the principles are followed. The article emphasizes that this move from implicit understanding to explicit, provable compliance is a major shift in how developers approach software architecture. AOK forces developers to analyze and justify their decisions, making it a concrete practice rather than abstract philosophy.