Infrastructure · internal first
Kernary Fabric
The resource substrate beneath Build and other workloads: compute entitlement, isolation, storage, networking, identity, state and lifecycle.
Resource cells
Cell contract
{
"id": "cell://tenant-a/orbit/317",
"class": "embedded-build",
"resources": {
"cpu": { "baseline": 0.8, "burst": 3.2 },
"memoryMiB": 4096,
"scratchGiB": 30
},
"state": {
"workspace": "volume://orbit/build-state",
"snapshot": "kernary/imx93-yocto:v12"
},
"networkPolicy": "vendor-and-source-allowlist",
"identity": "agent://orbit/build-agent/12",
"lifecycle": "suspendable"
}Build versus buy
| Capability | Initial decision | Internalise when |
|---|---|---|
| MicroVM / sandbox | Use established technology | Isolation or startup metrics require it |
| CPU and memory scheduling | Use cloud/container primitives | Workload economics are measurable |
| Object storage | Use managed content-addressed storage | Private deployment requires control |
| Workflow scheduling | Build KERNARY-specific orchestration | Core from the beginning |
| Evidence and policy | Build | Core product trust boundary |
Initial non-goals
- Compete with hyperscale public clouds as a generic compute service.
- Invent a new microkernel before a product workload requires it.
- Expose raw infrastructure credentials to agent workspaces.
- Make Fabric the public product story ahead of Engineer, OS and Board value.
These docs are part of the product design. Interfaces remain proposals until an implementation is published.