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.
What can refuse or escalate an effect before the Polyaxion engine is asked?
A policy engine decides what a policy says. Several refusals do not depend on any policy, such as a stale retrieval or an exhausted budget, so they come first and cannot be overridden by an allow.
The runtime wires callbacks into the Effect worker when it loads a build. Memory and flow supplies the origin, one-item and freshness checks; Decisions and routing supplies the budget lookup and reservation; the grant and mandate checks read the live grants.
Because each check is final, a policy that would allow an effect cannot restore one of them. Only after all five pass does the worker propose the effect to the Policy gate.
Handler capabilities act after the gate. A handler receives only the wrappers its effect's labels and targets allow, bound to transports that poly-io supplies; poly-runtime itself imports no network module.