Discovered while closing #126 (core->infrastructure layer violation fix).
Both files were already over the repo's 500-line hard limit (coding-standards.md §4)
before that fix, and remain so after it (the fix added a small reverse-DI port to each,
~15-30 lines):
This is a High-stakes classification (>500-line file is itself one of the objective
High-stakes criteria in engineer.md Move 7), so shipping past it requires an ADR or a
follow-up ticket rather than silence — this issue is that ticket. #126's scope was the
layer-violation fix specifically; splitting these two files along a concern boundary
(e.g. wiki_classifier.py's admission gates vs kind-routing vs title-derivation; wiki_axis_
registry.py's default-seed data vs registry/lookup logic vs schema-file parsing) is a
separate, sizeable refactor and out of scope there.
source: measured via wc -l on cdeust/Cortex@refactor/core-layer-violations, 2026-07-15.
Discovered while closing #126 (core->infrastructure layer violation fix).
Both files were already over the repo's 500-line hard limit (
coding-standards.md§4)before that fix, and remain so after it (the fix added a small reverse-DI port to each,
~15-30 lines):
mcp_server/core/wiki_classifier.py— 916 lines (was 901 pre-3 violations de couche core→infrastructure : wiki_axis_registry, wiki_classifier, wiki_schema_loader #126)mcp_server/core/wiki_axis_registry.py— 705 lines (was 687 pre-3 violations de couche core→infrastructure : wiki_axis_registry, wiki_classifier, wiki_schema_loader #126)This is a High-stakes classification (>500-line file is itself one of the objective
High-stakes criteria in engineer.md Move 7), so shipping past it requires an ADR or a
follow-up ticket rather than silence — this issue is that ticket. #126's scope was the
layer-violation fix specifically; splitting these two files along a concern boundary
(e.g. wiki_classifier.py's admission gates vs kind-routing vs title-derivation; wiki_axis_
registry.py's default-seed data vs registry/lookup logic vs schema-file parsing) is a
separate, sizeable refactor and out of scope there.
source: measured via
wc -lon cdeust/Cortex@refactor/core-layer-violations, 2026-07-15.