brownfield-guard

Path convention enforcement validates file paths against project architecture rules and blocks creation in forbidden patterns like src/lib/* or lib/*. It ensures files are placed within relevant domain modules instead of generic utility folders, preventing file tree anarchy.

Canonical path resolution in code governance validates file locations by referencing architecture decision records and layer definitions. It checks new or modified file paths against these established project conventions to maintain structural integrity and prevent anarchy in the file tree.

File size validation checks file lengths and automatically flags any files exceeding 300 LOC for splitting. This code governance practice ensures individual files remain maintainable and adhere to established project size conventions.

Blocking agent file creation in src/utils/ requires convention enforcement that validates paths against forbidden patterns. When an agent attempts to create a utility file there, the validation blocks the action and instructs the agent to place it within a relevant domain module instead.

Yes, you can use path validation to maintain brownfield code governance without external dependencies. The validation operates by referencing architecture decision records and layer definitions internally to enforce canonical path resolution and prevent file tree anarchy.

You need path validation when your project risks file tree anarchy from files created in disallowed locations. It enforces project-specific path conventions, blocks forbidden patterns, and references architecture decision records to maintain structural integrity in brownfield environments.