Inspecting compiled semantics
No matching nodes
Choose up to two semantic kinds. One reveals its real traffic; two compare only direct authored relationships.
Choose a kind to inspect its nodes and touching relationships.
Semantic radar needs more MAP space.
Which parts may start a child process or touch the network?
A checker that can call out can be talked into a verdict. The architecture limits the three kinds of outside reach, a model, a mining tool and a network, to three named places so that the check path stays closed.
poly-new calls a model through Claude Code in print mode, to draft source, and every draft goes straight back through the pipeline. poly-mine starts polyx and polyness, never a shell, never with the whole environment, and never the polyx command that calls a model.
poly-io holds the HTTPS, SMTP and ingress code. poly-runtime itself imports no network module; the host passes poly-io's transports to the runtime, which hands a handler only a wrapper bound to the targets its effect declares.
The import-boundary script reads every source and fails on any import that crosses these lines, on a socket global, and on a network module named in a string.