structural-hygiene-review

To detect authority drift, inventory the repo for competing authority cues across directories, filenames, schemas, CLI surfaces, and docs. This process builds an authority map that flags historical artifacts appearing active with P0–P3 severity levels.

The best way to enforce canonical terminology is to flag terminology drift across MemBase views, docs, schemas, CLI names, tests, and generated outputs. This ensures visible artifacts match the canonical glossary and current sources of truth.

To safely archive obsolete artifacts, apply safe archiving and correction rules that move deprecated files into clearly labeled history or deprecated locations. This updates references, tests, and adds guards against legacy names.

Agents learn the wrong rules because stale or historical artifacts appear active and act as competing sources of truth. Structural hygiene review corrects this by aligning the repo’s visible artifacts with the true operating model and canonical glossary.

Yes, you can use it to audit generated outputs, cross-references, directories, filenames, schemas, table names, view names, CLI surfaces, and docs for a given concept under review to correct project-structure authority drift.