Wire protocol

The wire protocol is the normative spec underneath grafOS. Most developers never need to read it — the SDK and CLI cover the everyday surface. But if you’re writing a foreign-language client, debugging an interop issue, or auditing the trust model, this section is the source of truth.

Top-level documents

• fabricbios-wire-encoding-v0 — frame headers, flags, message types, big-endian rules, full TLV catalog.
• fabricBIOS-design-document — the v0 normative spec for the firmware substrate.
• fabricBIOS-design-document-v1.1 — v1.1 supersedes v0 for new implementations.
• architecture — module + crate map for the reference implementation.
• terminology — the glossary you want to read first.

Resource model

• resource-types — Mem / Block / Net / GPU / CPU on the wire.
• resource-isolation-and-exclusivity — the three-axis policy model (capacity / execution mode / isolation-exclusivity) cells filter and score on.
• gpu-exclusivity-wire-format — exclusivity caveats for GPU leases.
• cpu-isolation-wire-format — isolation classes for CPU leases on bare metal.
• bare-metal-cpu-lease-semantics — what the fabric guarantees on bare-metal CPU leases.
• affinity-request-model — affinity-aware tasklets.

Scheduler + control plane

• hierarchical-scheduler — cell-scheduler / orchestrator architecture.
• scheduler-isolation-policy — admission filter + score pipeline; refusal vocabulary.
• control-plane-tls-plan — staged TLS rollout for control-plane traffic.
• token-gating-policy — capability-token caveat catalog.
• trusted-fabric-profile — operator-side requirements for production fabrics.

Data planes

• quic-stream-dataplane-profile-v0 — QUIC stream-based data-plane profile.
• premium-dataplane-methodology — methodology for declaring premium-tier data planes.
• rdma-revoke-semantics — lease revoke contract on RDMA-backed leases.

Golden vectors

The wire encoding is enforced by golden vectors at vectors/v0/ in the source tree. Any conforming implementation must reproduce them byte-for-byte. CI fails if a code change produces different bytes; regenerating is a deliberate operator action via:

cargo run -p fabricbiosd --bin vectors-gen
git diff --exit-code vectors/v0   # CI checks this is clean

The golden-vector contract is the strongest “wire compatibility” guarantee the project makes. It catches accidental encoding drift before it ships.