Wikantik has 24 Maven modules (the <modules> block of the root pom.xml). Most of them have a small, focused public API and a long tail of internal helpers; wikantik-main alone holds more than 700 classes. The trick to fast orientation is reading the public-API surface first.
Before non-trivial work in an unfamiliar module. Five minutes here saves an hour of search-and-grep later.
The module map is the "Module Structure" section of CLAUDE.md and docs/developer/Architecture.md in the repository; the wiki's version is WikantikArchitecture. Each module is one Maven artifact, and dependencies follow strict layering: wikantik-api holds the contracts, wikantik-main implements them, and wikantik-rest, wikantik-knowledge, wikantik-admin-mcp and the other edge modules sit on top. A few modules deliberately depend on almost nothing (wikantik-jdbc, wikantik-ingest, wikantik-insights), and the build enforces it.
There is no AST or reflection tooling behind this procedure. The practice is reading poms, grepping for the right shapes, and reading the design documents.
The frontmatter steps are the canonical procedure: the module map and POMs first (dependency rules), then the exported interfaces, then the registration points that tell you how the module plugs into the engine. The wiki's narrative articles and the ADRs give intent.
The frontmatter pitfalls are the recurring time-wasters. The "reading the whole module" antipattern is especially expensive on wikantik-main, and looking for a web.xml inside an endpoint module wastes a search: the only production web.xml is in wikantik-war.
Cluster Hub: Agent Cookbook (agent-cookbook)