Whether the code breaks its own architecture: cross-domain Entity access, an Entity leaked into a contract, an inbound adapter touching an Entity, an application or domain type referencing an adapter. Run this after finishing a change and before opening a PR — these are verdicts over the whole graph, so reading files will not surface them. scope 'delta' reports only what this branch introduced, including a relation that already existed but became a violation because a type moved.

How a type is wired, in either direction. 'out' = what it depends on and which methods it actually calls on each — including references held only in a local variable, whose type name never appears in the source, so grep cannot find them. 'in' = what depends on it, which of its methods each consumer uses, and which it declares that nobody calls. Use 'in' before adding a method to an existing port or use case: if the consumers already use disjoint subsets, the interface wants splitting rather than growing. Raise hops to see what a change would reach beyond the direct callers.

What this branch changed structurally against the base: types added, types whose public contract or relations changed — and for each, exactly what was added or removed. Use it before opening a PR to confirm the change matches what was agreed, and to describe it from facts rather than memory. Needs the server started with --base.