Release codenames and artwork¶
Each minor release pairs a computing pioneer with a concept reflected in its work. Patch releases inherit their minor release’s artwork, even when an early patch has its own historical codename. See version compatibility for the naming convention and early release rationale.
The common thread is a queue of ceramic tokens on a polished rail. Light studio scenes use teal and violet; dark scenes use blue and amber.
Released series¶
Per-job working directories isolate each task within the agent protocol.
Daemon-mediated RPC gives administrative state an explicit process boundary.
The live vq top view brings one window of job resource activity into focus.
Advisory host availability uses vq host down/up to guide dispatch.
Host pools and a default pool organize how work is shared across machines.
Tracing a failure back to its cause makes the queue diagnosable.
The job lifecycle timeline records ordered transitions and pending reasons.
Identity checks distinguish the principal behind a driver operation.
Dispatch stops are attributed to the authority holding them in place.
The first fleet console views connect a cross-host overview to live job detail.
Console accounts and sessions distinguish authenticated access.
Delegated administration carries authority across a fleet rollout.
Exact-SHA release evidence binds rollout decisions to content-addressed reports.
Scheduler runtime updates proceed without draining or waiting for running work.
One program name maps to separate runtime slots for different source revisions.
The concurrency quota becomes visible in vq overview.
The runtime_slot_root setting makes runtime placement an explicit binding.
Build beside the live runtime, switch on success, and reclaim the old space.
Managed self-update preserves recoverable state across lifecycle transactions.
Licensing, security, contributor guidance and documentation make vq publishable.
Provisional forward codenames¶
These names and concepts are proposals, not shipped features or release commitments. Re-confirm each against what its release delivers before tagging.
Provisional concept: logical ordering across hosts without a shared timepiece. Two rings per token, one count per participant.
Provisional concept: a consistent snapshot across independently running hosts.
Provisional concept: accept varied inputs while emitting a strict, uniform form.
Provisional concept: probabilistic membership checks for deduplication and idempotency.
Provisional concept: reclaim dead space through archiving and automatic cleanup.
Provisional concept: tolerate a network split while each side keeps operating.
Provisional concept: every server busy, so an arrival is turned away. Counted permits enforcing admission and concurrency limits.