Where it stands · November 2026

A two-owner pilot, and what it does today

The manifest says what the federation stands for. This page says what its software does now, how, and how far each part has been tested. "Live" means running between the pilot's two nodes, not proven across a large federation.

Current implementation status: two-node pilot

PartStateTested
Two nodes (NVIDIA DGX Spark), each lending model capacity to the other livein daily use
Links with pinned certificates, confirmed by the owners livein daily use
Credits recorded on both sides, compared automatically livein daily use
Containerised tasks run for a partner livesince November 2026
Charter version 1, accepted and signed by both owners live—
No link without each owner's signature on the charter (model requests, tasks, pairing, relays) livesince 21 November 2026; both pilot owners have signed
Refusals under the charter, on model requests: every new instruction judged before it runs livesince 21 November 2026, on both nodes
Refusals under the charter, on tasks: judged before they are accepted, by purpose or likely direct effect livesince 21 November 2026
Owner overrides of a refusal, signed with the owner key (never for absolute points) liveon simulated nodes; none used yet
Relays (several hops), nodes behind NAT, discovery listings builton simulated nodes only
Warnings between partners (silence, models down, certificates near expiry) livein daily use
Lab installer and in-place upgrades builton test benches
Charter version 2under the owners' review—

Charter checks and refusals

Trust and privacy

Tasks for a partner

A node can run containerised tasks for a partner, through a subset of GA4GH TES. The receiving owner decides which partners may send tasks and which images may run, each named by its SHA-256 digest.

Credits

Relays, NAT and discovery