;;; -*- scheme -*-
;;; Anonymized phenom StageP.StageControlPMultiImpl, generated
;;; 2026-05-18. Pipeline:
;;;   nucleos parse -E -D -I<phenom imports> \
;;;     /home/paul/src/phenom/StageP/NewBehavior/StageControlPMultiImpl.dzn \
;;;     | nucleos anonymize -
;;; then `sed s/_217/anon_phenom_stage_control_p_multi/` to rename
;;; the top-level impl to a discoverable name, and `sed /^import/d`
;;; to strip the now-vestigial import lines (the preprocessor
;;; already inlined every imported file's content; the anonymizer
;;; renames the `.dzn` extension to `._13` which breaks lookup).
;;;
;;; Why this model exists: per-component verify benchmarking on a
;;; phenom-scale impl without exposing customer source. Top-3
;;; heaviest of the 147-component phenom corpus by verify wall —
;;; representative of the worst case the engine has to handle.
;;;
;;; Per-component verify numbers (single nucleos invocation,
;;; serial, this 32-core box, commit b69fd226):
;;;   wall:        ~1.4 s
;;;   lts-gen:      564 ms
;;;   check-comp:    95 ms
;;;   compliance:   558 ms (of which ltscompare 467 ms)
;;;
;;; Verify result: all checks pass (deterministic, illegal,
;;; deadlock, unreachable, livelock, compliance).
;;;
;;; The component provides 4 ports (`_191`, `_194`, `_173`, `_214`
;;; in anonymized form) and requires ~10 others — a realistically
;;; complex multi-port stage controller.

((skip-wfc) (queue-size-external 2))
