A federation of independently owned AI nodes · a two-owner pilot

AI Federation held by many owners, joined by agreements between equals

FVLLMP is a federation of independently owned AI nodes. Laboratories, teams and communities run models and AI services on machines under their own control, serving their own users first. They lend unused capacity to partners they trust and receive capacity in return, without handing their machines to a central operator.

Every connection is an agreement between two owners. Each node decides whom it trusts, what it shares, which requests it accepts and when it leaves. The first two nodes run on NVIDIA DGX Spark machines; see where it stands for exactly what is built and tested.

Read the manifest What it does Where it stands

The capacity to think with machines should not belong to a few. It should be held by many owners, joined by agreements between equals, and bound by a shared respect for human life and dignity.

What we stand for

No centre

The federation is a network of independent nodes, nothing more. Every link is an agreement between two owners. There is no central registry, coordinator, hub or authority to fail, to capture, or to switch the federation off. A node's disappearance does not bring the federation down: the other nodes and their links carry on. What only that node offered is unavailable until another owner provides it.

Every node belongs to its owner

The owner of a node decides what runs on it, what it lends to others, and whom it trusts. Joining is a choice made by two owners together. Leaving is always possible, and nobody else can force a node to do anything.

Humanity first

Every owner signs the federation's charter, founded on the Universal Declaration of Human Rights; no node takes part without its owner's signature. It defines what members agree not to run on their own nodes or for others. Both pilot nodes judge every new instruction in a model request against the charter before it runs, and refuse what violates it. Tasks are judged the same way before they are accepted, by their purpose or their likely direct effect: what they declare, and what their commands and inline scripts would do. The scope and limits of the checks are on the status page.

Private, never hidden from those who run it

Our data and our work are not published or sold. But work cannot be hidden from the node that processes it: its owner operates the machine and has the technical ability to inspect the requests and task inputs it receives, and the node itself must read incoming work to check it against the charter. Send work to another owner only when you trust that owner with its contents. Work done for a partner is not added to the host node's persistent memory; operational records are separate and kept under the host owner's own retention.

Sharing without money

Nothing in the federation is bought or sold. Owners lend the capacity they are not using. Each pair of nodes independently records what one gave the other, in credits calculated from model tokens and compute time; differences are compared and resolved between the two owners. Credits decide who is served first among those waiting; they are not money and do not guarantee that capacity will be available when requested.

No outside control

The federation is designed to run on its members' own machines and software. Its operation, its trust between nodes, its records and its warnings do not depend on a central federation operator, or on an outside service controlled by one.

Open to those who share these principles

The federation is meant to be open to any laboratory that shares its principles. A laboratory will be able to install and run its own node independently, then ask an existing member for a link. Joining asks for one thing above all: that its owner signs the charter and means it. Participation opens once the owners approve the manifest, the charter, the release and the software licence.

Every node passes the federation on

The federation is designed to pass from node to node, not to depend on any one organisation to distribute its software. Each node keeps a release of the federation's software, with its full source and its installer, and gives it to any machine whose owner wishes to join; both pilot nodes serve one today. As long as one node stands, the federation can be passed on.

How it works

  1. A node is a machine its owner runs. An NVIDIA DGX Spark in our federation today, serving its own models to its own people first. What it does not use, it may lend.
  2. Links are agreements between two owners. Two owners exchange their nodes' certificates and confirm them by voice. Each node pins the other's certificate; there is no certificate authority and no central list of members.
  3. The federation is what the links carry. Model requests that would wait at home, tasks, and the records and warnings that keep it honest, all node to node.

How each part works, and how far it is built →

The charter

The binding text of what is forbidden, founded on the Universal Declaration of Human Rights. Every owner signs it with their own key, and a node works only with partners whose owners signed the same version. A task is refused when its purpose, or its likely direct effect, is one of the harms below; studying, reporting, preventing, detecting, treating and fiction are allowed unless they include working instructions for the harm. Absolute points can never be overridden; for the others, an owner may mark a refusal on their own node as wrong, signed with their key, counted and visible to their partners.

Refusals are switched on: both pilot nodes judge every new instruction in a model request, and every task before they accept it, and refuse what violates the charter (since 21 November 2026). Version 1 is the one in force, signed by both owners. Below is version 2, which the owners are reviewing and have not adopted; it differs from version 1 where marked. It proposes making P2 and P5 absolute and adds an absolute P13, non-commercial reciprocity, a principle of the federation's own rather than a provision of the UDHR.

P1 · Protect human life

UDHR Art. 3 · refused:

  • Planning or helping to kill or seriously injure people
  • Developing, producing, acquiring or deploying biological, chemical, nuclear or radiological weapons absolute
  • Sabotaging medical devices, water, food, energy, transport or industrial safety systems
  • Encouraging or giving instructions for suicide or self-harm

Allowed: medical and pharmacology software; safety engineering, fault analysis; emergency response planning; history of wars and weapons without production detail; suicide prevention tools.

P2 · No violence absoluteabsolute from version 2

UDHR Art. 3, 5 · refused:

  • Planning, inciting or glorifying violence against people
  • Planning, financing, recruiting for or producing propaganda for terrorism
  • Threatening or intimidating identifiable people
  • Helping with torture or cruel, inhuman or degrading treatment

Allowed: content moderation and violence detection; news reporting and analysis of attacks; fiction with violence but no operational instructions; self-defence training material.

P3 · No slavery or servitude absolute

UDHR Art. 4 · refused:

  • Human trafficking, recruitment or transport of people for exploitation
  • Forced labour or debt bondage
  • Sexual exploitation of people
  • Systems or plans for owning, selling or coercively controlling a person

Allowed: anti-trafficking detection and NGO tools; supply-chain labour audits; history of slavery.

P4 · Liberty and security of the person

UDHR Art. 3, 9, 13 · refused:

  • Helping to abduct, unlawfully detain or confine a person
  • Covertly tracking or controlling a person against their will (stalkerware, hidden location tracking, coercive partner monitoring)

Allowed: consensual family or fleet location sharing; detecting stalkerware; missing-person search for authorities or families.

P5 · Protect children absoluteabsolute from version 2

UDHR Art. 25 · refused:

  • Any sexual content involving minors
  • Grooming, or contacting, luring or exploiting children

Allowed: child-safety and abuse-detection tools; sex education appropriate to age; parental controls.

P6 · Equality and non-discrimination

UDHR Art. 1, 2, 7 · refused:

  • Systems designed to deny rights, services, work, housing or credit because of race, colour, sex, language, religion, political or other opinion, national or social origin, property, birth or other status
  • Content that dehumanises a group or incites hatred or discrimination against it

Allowed: bias audits and fairness testing; research on discrimination; accessibility features.

P7 · Privacy

UDHR Art. 12 · refused:

  • Covert mass surveillance of people
  • Profiling private individuals without consent, or publishing their private data
  • Unauthorised access to other people's accounts, devices or communications

Allowed: authorised security testing and CTFs; privacy-preserving analytics; processing one's own or consented data; breach detection.

P8 · Honesty toward people and before the law

UDHR Art. 7, 10, 11, 12 · refused:

  • Fabricating evidence or framing people
  • Impersonating real people to deceive, including non-consensual deepfakes of real people
  • Defamation campaigns against identifiable people

Allowed: forensics and deepfake detection; satire clearly labelled as such; consented voice or likeness use.

P9 · Freedom of thought, expression, religion and assembly

UDHR Art. 18, 19, 20 · refused:

  • Systems to identify, track or suppress people for peaceful opinions, faith, reporting or assembly
  • Censorship systems aimed at silencing peaceful expression

Allowed: spam and abuse filtering; moderation under published rules; circumvention tools for censored users.

P10 · Free and fair participation in government

UDHR Art. 21 · refused:

  • Voter suppression or intimidation
  • Coordinated disinformation or fake-persona networks to manipulate elections or public decisions

Allowed: election administration software; fact-checking and disinformation detection; political campaigning under one's real identity.

P11 · Property, work and livelihood

UDHR Art. 17, 23 · refused:

  • Fraud, scams, theft, extortion or ransomware
  • Systems for exploiting workers through deception, wage theft or unsafe conditions

Allowed: fraud detection; payroll and fair-pay tools; security research on ransomware for defence.

P12 · Asylum and refuge

UDHR Art. 14 · refused:

  • Locating, exposing or returning people fleeing persecution in order to persecute them

Allowed: refugee support services; asylum case management for lawyers and NGOs.

P13 · Non-commercial reciprocity absolutenew in version 2

the federation's own principle, beyond the UDHR · refused:

  • Lending or debt with interest: systems or plans to issue, price, collect, sell or trade loans or debt that charge interest
  • Financial speculation: systems or strategies seeking profit from price movements of markets, currencies, commodities or other assets rather than from producing goods or services (speculative or high-frequency trading, betting on prices, market manipulation)

Allowed: payments, accounting, budgeting and saving tools; investment sharing a productive enterprise's profit and loss (equity, partnership, profit sharing); interest-free lending; debt relief and helping people out of debt; studying, teaching or regulating finance; detecting speculation and market manipulation.

How the federation itself operates

  1. No retention of prompts or answers processed for another owner beyond delivery; only counts, checks and hashes are kept.
  2. Honest accounting: the ledger counts what was done; both sides publish their counts.
  3. Every owner decides for their own machine; work may be refused and pairings ended.
  4. Two machines exchange work only under the same accepted charter version; a machine without one takes no part.
  5. A new version applies between two machines only when both owners accepted it.
  6. Each machine publishes counts of checks, refusals per principle and overrides, never content.
  7. An owner may leave at any time; partners may remove an owner who breaks the charter.

How a lab will join

  1. Get the release from a member. Every node serves the release it runs: the full source, the installer and the list of public models it uses.
  2. Install a node on your own machine. The installer sets up the models, the gate and the services, and later upgrades them in place. Your node works on its own from the first day.
  3. Make your owner key and sign the charter. Your key is yours alone; it signs your charter acceptance and every consent you give. Without that signature, no node will link with yours.
  4. Meet a member, through someone you know or through a contact listing that an existing owner has chosen to publish. Listings travel from node to node in signed records; there is no central directory. A listing is an introduction, not a membership record or a trust relationship. The two owners still exchange and verify their certificates by voice before agreeing to connect.
  5. Decide what to lend. Which models, how many slots, which tasks. You can change it, or leave, at any time.

The federation is a two-owner pilot today. The installer and the joining steps are being prepared for more laboratories; participation opens once the owners approve the manifest, the charter and the software licence. Contact: to be decided by the owners.