Learned routing and consented corpus capture in llm-router, followed by distillation and training inside the operator's custody domain. Routing and capture are built and publication pending. The first end-to-end test is code-review triage on a permission-clean corpus Caletta already owns.
Turn the intelligence you rent into capability you own.
Route model calls. Keep the consented record. Train on hardware you control. Retain the resulting model, with the policy and evidence to use it on your own terms.
The ownership loop
- 01RouteFrontier APIs + your own models
- 02LearnYour corpus, evals, and training
- 03KeepModel, policy, and run evidence
End-to-end loop in build. Read the current status ↗
Ownership has
an exit test.
Unplug from the frontier labs and reproduce a declared fraction of a real workload, at a declared quality bar, from the operator's own model, corpus, evals, and policy, with no Caletta service required. That fraction is the Sovereignty Ratio. It is reported for one task on named hardware, with the evaluator, cost, and held-out period attached. If the ratio does not rise, the rest is only better-instrumented dependency.
A custody domain is the set of machines the operator enrolls and controls: one laptop, a workstation, an on-prem cluster, or datacenter capacity under their administration. Apple silicon is the first measured substrate, not the architectural ceiling.
The Exchange Dial applies to each connection in both directions: what the operator sends, and what the operator accepts. Its named levels run from nothing, through metrics and weight updates, to derived signal and raw work. Weight updates are not treated as private by definition; adapters can leak training data, so each level needs its own evidence.
From model call
to owned capability.
owned runtime
route · distill · train · keep control
A pure-Go MLX runtime for inference and training, with Metal tracing. The mesh transport ships as mlx-go-iroh; the integrated training datapath is built and publication-pending. Current evidence includes a measured two-Mac adapter exchange and merge. The intended deployment range is operator-controlled laptops, workstations, clusters, and datacenter capacity.
cgo-free Apple bindings, static Go binaries, and clear trust boundaries.
Built, measured,
and still in progress.
Each project carries its own evidence and release status.
Explore the components.
- Operator custody first. A custody domain can be one Mac, an on-prem cluster, or administered datacenter capacity. Use hosted services where they fit; keep the corpus, evals, policy, and resulting capability portable.
- Evidence over claims. Network rows, screenshots, logs, traces, and notes are part of the product surface.
- Workflow before platform. Prove one real workflow with a reviewable run record before building the platform around it.
- Clear maturity labels. Shipped, built-but-publication-pending, loopback-proven, and research are different commitments, and we mark which is which.