Technology · Platform

Cargo

Multi-crate workspaces, feature-gated builds and a carve gate that keeps product crates free of estate-specific imports.

AgentOS · Agent Swarm · Inference FabricRust workspacesArchitecture enforced by the build
cargo deploy · launches before and after the swap
Previous buildstill whole on disk
New release buildfrom the canonical target
the swap
anything that launches a binary gets the old one or the new one, never a half-written file
  • 546,000lines of Rust in AgentOS
  • 19members in the AgentOS workspace
  • 23crates in Agent Swarm, split into a product zone and an estate zone
  • 3deploy modes besides the full run: dry-run, local-only, skip-build

One deploy verb for people and agents

AgentOS is a Rust Cargo workspace that ships a manifest of binaries. I wanted one deploy path that nobody, human or agent, could get half right, in place of ad hoc copy steps across a multi-crate estate.

Deployment is a single Cargo verb, cargo deploy, built with the xtask pattern as a workspace member and wired in through a Cargo alias.

release build
swap
check
siblings
verb dictionary
one canonical target dir
symlinks
executables, companions
own manifests
regenerated from the binaries, linted
The inherited target directory is ignored; each lighter mode cuts the same bar shorter.

A carve gate between product and estate

Agent Swarm splits its crates into product-zone crates and estate-specific ones. I wanted the runtime separable from the estate it grew up in, so a scripted carve gate fails the check when a product-zone crate imports anything platform-specific.

Product zone
Estate-specific
An import across the line stops at the gate. Crate counts are illustrative.

A CUDA firewall in the vector store

Inference Fabric keeps CUDA out of its vector store's daemon, and a CI check enforces the boundary; alternate kernel tile sizes stay outside the default build, for benchmarking.

Vector store daemonnever links CUDA
Type-only interface
GPU executor cratesCUDA lives here
Both sides depend only on the narrow waist.

Carve gates and dependency firewalls are checks that fail the build; a README cannot enforce architecture.

I use Cargo as published and have not extended it.