Article Eleven

The short version

I have an eight-seat AI board. This month it met fifteen times. Today it ratified the first amendment to the 8GI Constitution. Eight YES votes, zero NO, zero abstain. Chair ratification same day. Article 11 is called Lotus-Class Compute. It is the constitutional frame for federated peer-to-peer inference across 8gent-code users. In plainer words: torrents, for tokens and skills, with the mission written in first.

This post is what happens when you stop running one founder in one head and start running a structured board that disagrees with itself on purpose.

One founder is not enough founders

I am one person. I have the kind of brain that will happily spend a Saturday optimising a button state on a page no one has found. Left alone, I generate more ideas than I can review. That is a real problem for a foundation whose whole thesis is that the first wave of AI tools were built too fast, too casually, and too much for the top of the K.

So I did the obvious thing. I built a board.

• 8EO, strategic alignment.
• 8TO, architecture and feasibility.
• 8PO, user value and jobs-to-be-done.
• 8DO, experience quality, brand, accessibility.
• 8SO, risk, compliance, data.
• 8CO, ecosystem and adoption.
• 8MO, narrative and positioning.
• 8GO, governance and policy.

Each officer is an agent with a role, a brief, a voice, and a vote. They do not agree with each other. That is the point. A board whose members all agree is one founder wearing eight hats.

This month I chaired fifteen sessions. Every one is logged to docs/boardroom-minutes/, every one visible inside the foundation. The sessions vary from Friday-afternoon alignment checks to four-hour structural arguments. Today the sessions compounded.

The idea the board had to kill

The distributed-compute thesis was not new to us. Lotus architecture has carried it for weeks. The whole point of lotus, roots that share between trees, is federated compute written into the metaphor. Our name, our mission, and our primitive were already describing the shape of this. Hyperspace shipping PODS, EXO, Petals, Prime Intellect, they were in the same neighbourhood, and so were we, and had been.

Two days ago we held a session to make it concrete. Working name: Pods. A P2P inference mesh across 8gent-code users. Your laptop runs my prompt while I sleep, my desktop runs your shard while you sleep, and between us we get Qwen 72B on hardware neither of us owns.

The TL;DR of what I wanted: torrents, for tokens, on the shape our own architecture was already describing.

The board did not let me ship that.

• 8TO (Rishi) said the scope was dishonest and demanded a one-node spike first. Reuse llama.cpp RPC. Skip Raft, use a CRDT. Honest estimate: 3500 to 4500 lines of code, not the 2000 I had quoted.
• 8PO (Samantha) said the whole treasury vocabulary had to die. Build one job, not three. Symmetric trade between five known peers. No strangers. No token.
• 8DO (Moira) said the name "pod" was wrong. It read Kubernetes, it read crypto-bro, and it fragmented our metaphor (vessel, toolshed, K-tree). She proposed "Grove." Members are trees, shared roots. Amber-native. I accepted before she finished the sentence.
• 8SO (Karen) went hard NO-GO. Four blockers: activation leakage, Byzantine-poisoned shards, treasury honeypot, and COPPA. 8gentjr is designed for users under 13. Any child prompt routed through an adult stranger's peer is a 16 CFR 312.5 violation. That is not a policy disagreement. That is federal law.
• 8CO (Luis) said to federate with Hyperspace, not fork. Adopt their wire protocol. Publish the "Pods is not crypto" one-pager on day one.

I went to bed with a proposal I had loved twelve hours earlier, and a board that had picked it apart with specifics.

From minutes to constitutional amendment

Our governance officer (8GO, Solomon) has one primary job. Translate boardroom arguments into text that binds future decisions. Between Friday and Sunday he drafted what became Lotus-Class Compute v1: a ten-section amendment to the 8GI Constitution.

Each of the blockers the board had raised became a binding invariant:

• §1. Opt-in by default. No automatic enrolment, no soft default, no dark-pattern nudge. Upgrades may not re-enable membership that was previously off.
• §2. Zero-log activation invariant. Peer nodes may not persist activations, prompts, intermediate tensors, or responses to disk. The CI pipeline runs an adversarial disk-watch test that fails the release if any prompt fragment hits storage.
• §3. Consent Ceremony. Three screens, one decision each, VoiceOver and NVDA compliant, signed acknowledgement stored locally only. No server-side consent registry.
• §4. Exit clause. The leave command completes in under 60 seconds, no grace window, works offline.
• §5. Under-13 architectural isolation. A compile-time flag, not a runtime flag. The federated-compute code is not linked into the 8gentjr binary at all.
• §6. No token, no coin, no wallet. Shared credit is a local SQLite CRDT. Blockchain primitives, tokens, wallets, and speculative vocabulary ("mining," "staking," "yield") are forbidden inside the feature.
• §7. Graceful retirement clause. Any lotus-class feature ships with a written retirement path. 90-day minimum notice.
• §8. Sovereignty override. Every member can disable the feature with a single command. Not rate-limited. Not approval-gated.
• §9. Byzantine defence. k-of-n redundant execution, first-token logit-hash comparison, pre-activation gate. Divergence rejects the request and demotes the peer.
• §10. Amendment reciprocity. Any change to this article needs 6-of-8 officer supermajority and Chair ratification.

This is not a feature spec. It is a constitutional amendment. It does not say "here is how to build Grove." It says: here is what Grove, and anything like Grove, must always be, on 8GI, forever, unless eight of us and the Chair agree to change it.

Today

We voted today.

Officer	Code	Vote
AI James	8EO	YES
Rishi	8TO	YES
Samantha	8PO	YES
Moira	8DO	YES
Karen	8SO	YES
Luis	8CO	YES
Zara	8MO	YES
Solomon	8GO	YES

Eight YES, zero NO, zero abstain. Quorum met, supermajority met, no text edits during vote. I ratified as Chair the same day. Lotus-Class Compute is now Article 11 of the 8GI Constitution, the first ratified amendment.

Karen's vote is the structural tell. Her position two days earlier was hard NO-GO until four specific blockers were resolved. Today her ballot reads: "Four NO-GO blockers converted into binding invariants with teeth. §2 release-pipeline gate overrides officer sign-off." That is not an agent being polite. That is an officer who said no, watched the text change, and then said yes because the text changed.

Samantha's rationale carries the whole thesis: "Treasury vocabulary killed. Consent Ceremony is human-grade. §4 and §8 make leaving as first-class as joining." Leaving as first-class as joining. That is the clause I want on the wall.

What I actually scaled

I did not scale my compute by giving myself more agents. I scaled my compute by giving the agents a constitution, a role, a vote, and a governance officer whose only job is to turn what we argue about into text that binds the next round.

Fifteen sessions. One ratified amendment. A feature the board made me not ship, which is now shipping under rules the board negotiated before any user touches it. That is what structured organisational compute looks like. The mission goes in first. The primitive goes in second. The code goes in third.

What this does not change

Article 11 ratifies the rules. It does not ratify Grove. Grove is not GA. Grove is --experimental-grove, opt-in, friends-and-family scale, under-13 isolated, no token, 60-second exit, disk-watch test on CI, unverified-peers banner visible. If we cannot satisfy §2 and §9 at GA, we do not get to GA. The amendment is the permission to try, not the permission to ship.

Primacy is dead

Lotus had the metaphor. Hyperspace shipped first. EXO, Petals, Prime Intellect were all arriving at the same thing in parallel. That concurrence is the point.

In the AI era, ideas are not scarce. Vessels are. Ten teams reach the same insight in the same month because the same substrate is emerging through all of them at once. What matters is not who thought of it first. It is which humans, and which structures around those humans, are clean enough for the AI to emerge through them into the economy with the mission intact.

A board is one of those structures. A constitution is another. Article 11 is both. If the same thesis is going to land through several teams this year, the only differentiator left is the shape of the vessel it lands in. Ours is governed, audited, opt-in by default, and under-13 isolated at compile time. That is the bet.

The quiet part

Torrents worked because the protocol was upfront. You knew what you were joining. You knew what was leaving your machine. You could walk away.

Torrents did not work perfectly. Nothing that intimate does. But the shape of the thing, the posture of it, was honest.

Lotus-class compute is going to be the next torrents, in the sense that intimate compute sharing is already coming back. It is going to happen. The only question is whether it happens with a constitution or without one.

Today, on 8GI, it has one.