Select a project root; Aigis scans the COMPLETE tree (every folder, every file) with focus on programming code, then lets you drive Claude Code through the steps — start the analysis and the Code Review Circle right from here.
| # | Relative path | Language | ~LOC | Planned change |
|---|
These are the files CORE Cartography will annotate — producing an Annotated Source per file plus one consolidated Codebase Map across the whole project. Behaviour is never changed; only descriptions, dependency notes and flow comments are injected.
“Start analysis” hands the step to the local Aigis bridge (serve.py), which drops it
into the OS temp folder for the running Claude Code to pick up — no folder to choose, nothing
persisted (the temp is wiped when the bridge stops). The scanned project is never written to.
Run Aigis with serve.py and open http://localhost:8753.
A whole-codebase flowchart produced by CORE Cartography. Nodes are code blocks; edges are relationships. Orient instantly in a large codebase and see dependencies, structure and flow at a glance.
When an analysis run completes, Aigis prepares an overview here: which files and blocks were examined, how many are documented vs. still missing, and documentation coverage across the project. Generated from the live run — no source code ever leaves the machine.
| # | Relative path | Language | ~LOC | Blocks | Documented | Status |
|---|
| # | Relative path | Outcome | Blocks | Reason |
|---|
| # | Relative path | Cleaned | Regions | Bytes | Note |
|---|