The engine

Read-only capture, with its current scope stated plainly.

Kolibri reads vendor-supported device interfaces, produces canonical evidence signed on the host before transmission, and leaves no running component after uninstall. The current release is NVIDIA-only C0 capture; the assurance ladder and continuous resident agent are not implied by the name.

Read-only · Offline-capable · C0 / NVML today

Posture

Four operating constraints.

The agent is built for the operator's constraints as much as the buyer's. Each property below removes a specific reason a data center would otherwise refuse to run it.

READS, NEVER WRITES

The scan path contains no call that writes to, resets, reconfigures, or stresses a device. Release controls scan for device-writing symbols, subprocess execution, and runtime mutation.

OFFLINE-CAPABLE

Scan and verification run fully offline and air-gapped. Submission to the registry is a separate opt-in step; isolation does not prevent local capture or verification.

SMALL DEPLOYMENT

The shipped probe installs with pipx on Python 3.10 or newer, needs no kernel module, and runs as a userspace process with read-only device access.

CURRENT SCOPE STATED

Live capture today is the C0 read-only path over NVML on NVIDIA hardware. Higher assurance, functional coverage, and the resident continuous agent are specified or in development, not presented as live.

What it reads

Named sources, read through vendor-supported interfaces.

The probe reads the device boundary. Raw values are measured evidence; rates, trajectories, threshold distances, and appraisals computed over them are derived. The current live implementation is NVML on NVIDIA hardware.

Device interfaces · measured condition facts

Identity and firmware

NVMLdevice registers

Model, UUID, serial, PCI topology, driver version, VBIOS version, and InfoROM state as software-read measured facts.

Memory and events

NVMLvendor event stream

ECC state, row-remap and retirement state, and Xid events where the source is present and readable.

Operating state

NVMLdevice sensors

Temperature, power, energy, throttle and violation clocks, clock residency, and utilization counters.

Fabric and configuration

NVMLsupported interfaces

PCIe and interconnect state, replay counters, ECC mode, compute mode, MIG layout, and persistence settings.

Architecture

What leaves the host.

The probe signs a canonical evidence bundle on the host before transmission. Under specified C2 operation, checkpoints, observation windows, health events, and periodic monitoring bundles are the transmitted record families. A raw high-frequency sample series is disclosed only under recorded scope when a relying party needs it for replay or dispute.

Capture and verification boundary
Operator premises Read-only capture on the customer host
Identitymodel / UUID / serial Conditionmemory / thermal / power FabricPCIe / interconnect ConfigurationECC / MIG / compute mode
Kolibri read-only capture EmitsCanonical signed evidence bundle
signed bundle leaves raw series stays by default
Append-only evidence store Registry + transparency ledger Relying partyRetained package + independent verification
The host signs before transmission. The stored bundle, signer lineage, ledger proof, signed root, and stamped artifacts form the verification package a relying party should retain.
Current assurance level

At A0, software-read identifiers and signer continuity provide operational identity, not hardware authenticity. The current probe and evidence architecture are operationally exercised in Voltry's field program; higher assurance and continuous coverage remain separately statused in the methodology's maturity matrix.