review-cartography

Security cartography validation works by spawning independent subagents to verify entry points, key components, flow sequences, and security notes against actual repository files. It corrects stale paths, adds missing handlers, updates frontmatter, and runs validation scripts to ensure format and reciprocal links remain accurate.

Overlap detection identifies redundant or intersecting flow maps by running specialized validation scripts across cartography files. It flags candidates for merging and extracts conditional sub-flows when content grows large, keeping security audit documentation maintainable and free of duplicated navigation paths.

Code review workflows handle stale flow mapping by applying automated corrections that fix file and symbol references, update metadata, and add missing entry points. They preserve original created timestamps while updating modified dates to maintain a reliable audit trail of documentation changes.

Yes, independent subagents can be spawned to read the code and verify security notes, flow sequences, key components, and entry points. They perform focused validation checks against the actual codebase, ensuring documented cartography matches the current repository state.

Cartography review updates reciprocal related links by adding cross-references across flow files and running validation to confirm the links are correct. It also updates frontmatter metadata while preserving created dates, ensuring navigation maps stay synchronized for auditors.

Cartography validation scripts should be run regularly as part of an audit to keep flow maps accurate after refactors, new handlers, or security fixes. Running them ensures documented entry points, flow sequences, and security notes match the actual codebase before reviewers rely on them.