A check, in order

A check, in order A sequence diagram generated by Archify. check target parse source type and domains lower the machine strict validate translation validation model check confirm, deadlock, liveness verdict and witnesses Front end Lower Agree Explore Report poly CLI · Sequence participant poly CLI Check pipeline · Sequence participant Check pipeline poly-lang · Sequence participant poly-lang poly-core · Sequence participant poly-core poly-lower · Sequence participant poly-lower sam-pattern 2.3.0 · Sequence participant sam-pattern 2.3.0 poly-ref · Sequence participant poly-ref polygraph 8.4.0 · Sequence participant polygraph 8.4.0 Legend reply crosses a boundary message

The short answer

  • • The pipeline parses and lowers the machine, has sam-pattern validate it, has poly-ref compare it with the semantics, and only then lets polygraph explore it, with poly-ref confirming what polygraph finds

Not shown here

  • • Effects, composition, configuration and policy stages, which run after these for machines that have them
  • • Connected but out of scope: MCP server, Language server, Workflow server, poly-new, Admission, Feedback commands

What it guarantees

  • • A check that did not run or hit a bound is never CLEAN: the verdict fold ranks INCONCLUSIVE and UNDERPOWERED apart from CLEAN, vacuous properties are INCONCLUSIVE, and admission refuses a build with any check not run