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 checks come from the vendored engines, and which does poly do on its own?
poly adds no new checking engine except its own model checker. The question is where the engines are relied on and where poly refuses to take their word.
The pipeline asks sam-pattern for strict validation and polygraph for the model check, the effects check and the product check. It asks Polyaxion to compile and harden each policy and polycheck for capability regions. poly-ref repeats the model check, the effects check and the composition check on its own and the two must agree, with PL2501 as the disagreement code.
At run time, the same engines are used another way. The runtime runs the polyrun kernel from polygraph, and the Ledger subclasses the kernel's store and uses polyflow's event format and verifier.
All of them are copied unchanged into vendor/ or peers/ and pinned by hash and commit. A test re-hashes each file.