What problem does it solve? It prevents uncontrolled growth of a pattern specification document (PATTERN.md) by measuring how many top-level sections are added versus removed in each release, enforcing a documented N:1 budget rule with semantic verdicts instead of hard blocking. ## Core Features & Use Cases - Section Counting: Counts top-level ## sections in PATTERN.md with a whitelist that excludes TOC, examples, and self-referential sections. - N:1 Rule Evaluation: Parses CHANGELOG.md for target and previous versions, computes net additions versus archived removals, and emits pass, warn, fail, or skipped verdicts (patch releases are skipped automatically). - Report and Telemetry: Writes a versioned complexity/budget-report-<version>.md audit report and logs an EP-013 complexity_budget_check telemetry event. - Use Case: Before tagging a minor release of the pattern, run the check to verify that added sections stay within the N:1 ratio against archived sections, and get recommendations to deprecate sections or add a skip marker when the ratio is exceeded. ## Quick Start Ask the assistant to run the complexity budget check for the current PATTERN.md and CHANGELOG.md and show the verdict report for the target version.
