Territories, ranked entry points and report contract v2

Territories replace modules as the reported unit: a non-overlapping tree of code areas with detail levels and a recommended detail. A territory splits when it is too big or when its child folders change independently; folders that change together stay together; every split carries a one-line reason. Tests attach to the territory of the code they test. Every territory gets a one-line description (manifest description, README, or its main files).
Entry points: a ranked list that answers "where does the design fail, and where do we start?", each with evidence, a plain-language verdict and a design move (move a boundary, extract a shared abstraction, break up a hub, split a hotspot, centralize a contract, stabilize an interface).
Report contract v2 (schemaVersion: 2) built around these: verdict, entryPoints, territories, coupling, files; inspect uses the same vocabulary; a migration table v1 → v2.

Navigation Menu