archivist-structure-ownership-auditor

Auditing codebase architecture boundaries involves inventorying folders and imports to identify ownership violations and cross-cutting responsibilities. This process produces an actionable report mapping findings to owners and required structural changes.

Unclear folder ownership and cross-cutting imports happen when shared code blends responsibilities, files handle too many jobs, or runtime dependencies bypass documented architecture boundaries, causing architecture drift across the codebase.

Yes, you can inspect runtime and platform imports in feature code without modifying files. A report-only audit inventories imports and dependencies to surface architecture violations while leaving the codebase completely untouched.

Generate an architecture audit report by running an auditor against the target repository to inventory folders and imports. The output maps ownership violations, stale compatibility wrappers, and naming issues suitable for governance documentation.

A report-only codebase structure audit identifies ownership violations and architecture drift but does not edit or refactor files. It outputs findings to a reports directory, leaving actual code modification to developers.