- Project Overview - Main project documentation
- Specifications - Core system specifications
- Implementation Guide - Current implementation status and patterns
Defines WHAT the system does:
- inspectors.md - Inspector patterns and contracts
- analyses.md - Analysis types and workflows
- refactorings.md - Refactoring strategies
Describes HOW the system works:
- guide.md - Current architecture and implementation status
- patterns.md - Key design patterns and best practices
- archived/ - Historical implementation documents
Supporting documentation:
- ejb-migration.md - EJB to Spring migration specifics
- stereotypes.md - Stereotype definitions and usage
Inspectors analyze Java classes and emit tags/properties. See spec/inspectors.md.
The system uses a graph to represent:
- Nodes: Classes, packages, files
- Edges: Dependencies, relationships
- Tags: Analysis results attached to nodes
- Discover Java classes (binary or source)
- Run inspectors in dependency order
- Build graph with tags and properties
- Export results (CSV, GraphML, JSON)
When updating documentation:
- Keep specifications in
/spec- these define the contract - Update implementation details in
/implementation - Archive outdated plans rather than deleting them
- Maintain this README as the entry point