Psyclone 2.2.0: Builders — a declarative bake pipeline
Bringing a distributed real-time system up used to be the quiet, fragile part of the job — a script here, a hope there, and no real visibility into what happened between “start” and “ready”. Psyclone 2.2.0 changes that with Builders: a first-class, observable pipeline for baking a system into existence.
A Recipe with a real identity
Every bring-up in 2.2.0 is driven by a Recipe that carries a stable string RecipeID from start to finish. That identity flows through every message the bake produces — five correlation entries ride on each one — so you can track, correlate and reason about a bring-up across the whole system instead of squinting at interleaved logs.
Two clean streams: status and data
The bake stream is split into two typed channels. A .status stream carries progress-only acknowledgements — where the bake is, right now. A .data stream carries the actual payload: lossless, sequence-numbered, with gap detection so a missing sequence is a hard error rather than silent data loss. It reassembles through a bounded buffer with per-batch acks, so a slow consumer can never blow up memory.
Control you can trust
Bakes are steerable while they run. Per-verb control types (BakeControl.Cancel / Restart / Pause / …) are governed by an issued-by allow-list and a monotonic control sequence, with cancel-supersedes-pause ordering so conflicting commands resolve predictably. Interactive steps honour fail | pause | skip on timeout, and “blue-edit” knobs let you adjust a running Recipe on the fly.
Builders are the foundation the new Startup Supervisor is built on — and together they make Psyclone bring-up something you can watch, control and depend on.
Psyclone 2.2.0 is available now on the download page. Full detail in the Psyclone documentation.
