ALL-ARCH0001 · architecture_fitness_coverage
Measure declared architecture characteristics with executable fitness evidence.
This is a deterministic rule for all languages. Read its implementation.
Definition
Section titled “Definition”Divide declared architecture characteristics protected by an objective, executable check, retained result, current observation date, owner, and scope by all declared characteristics. The result must come from CI when configured. Documentation or tool presence alone does not count as executable coverage.
Evidence
Section titled “Evidence”Findings link each quality characteristic to its objective, check, retained evidence, scope, owner, observation date, and CI or repeatable review path. The value is the percentage of declared characteristics carrying current executable evidence.
Exceptions
Section titled “Exceptions”Characteristics that cannot be automated may use a declared repeatable review with retained
evidence when project policy permits it. A result older than maximum_age_days no longer
counts as coverage, since a fitness function nobody has run recently is documentation. Setting
require_ci to false accepts a check a person runs on demand, which is what a project without
continuous integration has to do.
Examples
Section titled “Examples”Eight of ten declared characteristics with current retained checks produce 80. A written
latency goal with no recent retained result does not count.
References
Section titled “References”- Cites “Building Evolutionary Architectures”, Fitness Functions
- Cites “Architecture Tradeoff Analysis Method”
- Cites “ISO IEC IEEE 42010”, architecture descriptions