YOUR CODE, WITH CONTEXT
Understand what belongs where.
Loading checkout…
THE BUILDING BLOCKS
Module map
Select a module to follow its interfaces and dependencies. Sort to find large or busy parts.
| Public names | Boundary concerns |
|---|
Build the structural map to explore modules here.
ONE NEIGHBORHOOD AT A TIME
Connections
Incoming links appear on the left; outgoing links on the right. Select a node to keep exploring.
BUILD UNDERSTANDING, THEN CHALLENGE IT
Run the full analysis, one saved batch at a time
Mapping
Refresh the source graph, annotate only missing or stale modules, then reconcile the current map.
Current annotations are reused.Pattern discovery
Run component and CI/CD reviews while screening the catalogue, then review useful patterns in detail.
Includes component boundaries, standalone packages, independent verification and one pipeline review.Fresh Eyes
Explore three designs per subsystem, then reconcile a product design from behavior alone. Workers cannot inspect source.
Subsystem designs feed a final product review.Component Architecture
Assign separate scouts to boundaries, standalone packages or repos, and independent verification.
Compare keeping code together with extraction; save contracts, costs and concrete next steps.CI/CD
Review real pipeline configuration for a fast component path, wider checks, caching, parallelism and deployment.
Starts from source facts and configuration. No semantic mapping or project test execution is required.Preview affected checks
Use declared task inputs and dependencies to explain which checks a change needs. This previews the plan; it does not run commands or deploy.
Full check plan and evidence
No plan yet.
Models and parallel workers
Each stage uses the model you choose. A blank model uses that CLI's configured default. Installed Codex or Claude CLI authentication is required.
Architecture and CI/CD finding reviews run only when a worker proposes a change. Enabled ordered review passes replace those default reviewers.
Ordered review passes
Independent batches run in parallel. Within each batch, enabled review passes run in this order.
Workflow progress
Portable understanding
Current analyses travel with your repository in anaxigraph/. Commit and push that folder through your normal Git workflow.
Mapped locally, exported, and committed/pushed are reported separately.
Advanced: prepare and submit an individual agent task
AGENT REVIEW
Prepare a task to begin
Use these packets with an independent agent when you want direct control. Full workflows above run and save their batches automatically.
1. Give this task to an agent
Choose an analysis above.
Use a separate worker that has not inspected the implementation. Keep this task free of source and current architecture context.
2. Save the agent's result
Saved reviews
START WITH WHAT ALREADY EXISTS
Prepare a change
Find an owner, reuse opportunities, affected contracts and relevant checks.
Preparing a change pins its baseline across subsequent scans.
Your change brief will appear here.
CHECK BEFORE AND AFTER
Assess and verify
Run project tests through your agent or CI. Supplied results are attributed to their exact source fingerprint.
No assessment or comparison yet.