atlas-integrity-check

To validate changed files against architecture mappings, gather today's changes and compare them to tasks/architecture-atlas/file-index.md to report any unmapped files. This ensures new modules are accounted for in the atlas during code integration.

If the architecture atlas file does not exist, the integrity check silently skips without error. This silent skip allows code integration workflows to proceed safely when the architecture atlas has not been bootstrapped yet.

To catch unmapped files during a release workflow, run an atlas consistency check that compares today's changed files against your file index. It flags any new modules or directories missing from the architecture atlas.

When unmapped files are detected in the file index, you should follow the guided remediation steps to refresh or update the architecture atlas. This ensures all new modules and directories are properly mapped to known systems.

You need to verify code changes against an architecture atlas during code integration and release workflows. This validation ensures that daily code changes and new directories are properly mapped to known systems before deployment.