Venue Kit
One registry and planner for every place work can run.
- Status: alpha (what this means)
- Language: Rust
- Kind: cross-platform
- Has real code today: Yes
- Source: not public yet
- Name: provisional; it may change
What it owns
Venue Kit describes and plans over the places work can run: a machine, a VM, an API provider, a cloud pool you can rent from, a peripheral behind a host. What each is, how to reach it, what it has, what it can do, what it will accept, what it costs, and who may use it. It is a Kubernetes Resource Model vocabulary rather than a new format: Node, Endpoint, NodePool, ContractClass, ContractClaim, Placement and Budget in the API group node.slashbuilder.com/v1alpha1, with PriorityClass and Lease accepted verbatim from Kubernetes. Kubernetes (and DRA, Karpenter) is treated as the standards body: its names, shapes and semantics are followed unless a divergence is recorded with a reason.
Every answer is Yes, No or Unknown, and an Unknown says what would settle it. Nothing is trusted because a document says so: each manager writes its own observation, the effective view is computed on read and keeps disagreements visible, and work that carries data classes needs both a use grant and the data owner’s egress grant or the answer is Unknown.
What it will not do
- Running the work, or provisioning anything: Venue plans and records, something else provisions
- Inference, storage, messaging: those are their own Kits, which sit on top of or beside this one
- Containers and other workloads (many, short-lived; their names and images describe the estate): another layer’s job
- Changing a machine: accounts, keys, sudo, packages, policies.
Related Kits
Identity Kit, Storage Kit, Inference Kit, Interface Kit, Manifest Kit, Score Kit
Reference docs
No reference docs yet.