Integrations

Add capability where an operational boundary is already clear. A focused integration should contribute one strong specialty, preserve the ownership of the systems on either side, and leave the route visible in the evidence. That discipline expands what a fleet can do while keeping delivery and convergence understandable.

These integrations share a clear operational boundary, and each one is optional; the core delivery and fleet systems remain fully operational on their own.

The run

The operator asks for a focused capability at an existing delivery or fleet boundary. The integration owns one seam—configuration rendering, a disposable VM, secret custody, or transport—while Railyard and Roundhouse keep route, trust, readiness, and proof. The turn is ownership staying explicit across the handoff. The run closes when the integration’s evidence returns to the lifecycle that requested it without becoming a second operating system.

• Chezmoi — deliberate dotfile reconciliation.
• Jev — model/effort selection and bounded decisions throughout delivery, enabled when TYPESAFE_API_KEY is present.
• Tart Xcode Runner — disposable macOS test VMs.
• 1Password — auth-artifact custody and verification.
• Tailscale SSH — optional transport acceleration.

The skills index cross-links the operational references that have their own reusable workflow; Chezmoi remains fully documented on its integration page.