| name | exeris-spring-mode-clarity-review |
| description | Prevent confusion between Pure Mode and Compatibility Mode in code, tests, and docs. Flags features that lack a mode label, compatibility behavior that leaks into the pure path, and docs that claim pure semantics while implementation is compatibility-driven. |
exeris-spring-mode-clarity-review
Purpose
Prevent confusion between Pure Mode and Compatibility Mode in code, tests, and docs.
Checks
- Feature is explicitly labeled as
PURE_MODE, COMPATIBILITY_MODE, or MIXED.
- Trade-offs are stated when compatibility semantics are introduced.
- Compatibility behavior does not silently become default pure path.
- Tests and docs reflect the same mode assumptions.
Failure Conditions
- mode is implicit/unstated
- compatibility behavior leaks into pure path
- docs claim pure semantics while implementation is compatibility-driven
Output
- mode classification
- drift findings
- minimal correction plan