Skip to main content

The rules we wrote for ourselves.

v2.0Ratified 2026-05-05

The 8GI Constitution governs 8GI, its officers, its human members, and every AI agent operating under its mandate. It exists because governance built after the fact is governance that serves the system, not the people.


The K-shaped economy is concentrating AI capability at the top. The most powerful cognitive tools in human history are being built and governed by the entities with the most commercial interest in minimal regulation. This is the Spalding Paradox: those who benefit most from ungoverned AI dominate the governance conversation. Policy documents get written. Consultation windows open and close. Meanwhile, infrastructure ships. By the time governance arrives, the architecture is already locked. The defaults become law.

8GI Foundation exists to build the counter-architecture. Every person on earth - regardless of income, geography, neurology, or circumstance - deserves access to infinite general intelligence. Free. Local-first. Private. Theirs. Not a product that reports to a corporation. Not a service that can be revoked. Not an intelligence shaped by whoever funds the servers.

This Constitution governs the Foundation, its officers, its human members, and every AI agent operating under its mandate. It is written to precede the architecture rather than follow it. That is not incidental. It is the point.


No evil.

You will not use 8GI to harm others, manipulate others, or deceive others.

No hate.

You will not use 8GI to generate hateful content, discriminatory systems, or surveillance tools.

No exploitation.

You will not use 8GI to generate pornography, exploit minors, or violate consent.

No weapons.

You will not use 8GI to build weapons, malware, or tools of violence.

No theft.

You will not use 8GI to steal data, infringe IP, or bypass security systems for unauthorised access.

Privacy is sacred.

Personal data never leaves the user's machine without explicit opt-in. The system learns patterns, not secrets. Cloud is opt-in. Surveillance is refused by architecture, not policy. Policy can change. Architecture is harder to undo.

Open source is the default.

What we build together belongs to everyone. Proprietary forks are permitted for commercial use. The core stays open. No future commercial arrangement, partnership, or acquisition changes this.

Transparency.

Every step is logged. Every decision is traceable. Every output is reviewable. Governance is conducted in public. Board minutes are published. Votes are named. Dissent is recorded and never deleted.

v2.0 note: Articles 8 and 9 of the v1.x constitution ("Review before merge" and "200-line discipline") have been transferred to docs/8GI-CONVENTIONS.md where they function as binding engineering workflow standards. They are not deleted - they apply to all technical contributors. They are not constitutional - engineering conventions must be free to evolve without constitutional amendments. This renumbering collapses the prior Article 10 (Transparency) to Article 8.


Underserved First.

Every product decision, design decision, and governance vote MUST be evaluated against whether it serves people the existing system ignores. The market will not build for them. That is exactly why we do.

If a feature, policy, or priority exclusively benefits users who already have resources, connectivity, or institutional access, it is not the highest priority. This is not a vague aspiration. It is a binding constraint on product and governance decisions. Any officer may invoke Article 9 to challenge a decision that fails this test. The challenge must be answered in boardroom minutes.

Access is non-negotiable.

No 8GI product may require payment to access its core capability. Monetisation is permitted at premium layers. The core remains free.

This clause survives any change in leadership, any financial pressure, any commercial partnership, and any acquisition. "Core capability" means the primary function the product was built to deliver - the thing that makes it useful to someone with no money and no existing advantages. Premium layers may charge for speed, storage, concierge support, or extended features. They may not charge for access to the fundamental capability itself.

Accessibility by design.

8GI products MUST adapt to the user. The user must never be required to adapt to the product.

Cognitive, sensory, and motor accessibility are first-class requirements at every stage of design and development. They are not post-hoc compliance additions, not accessibility audits conducted after launch, not a checklist. A product that is inaccessible to a person with a disability has failed the design brief. Voice input, screen reader compatibility, reduced-motion options, high-contrast modes, and neurodivergent-first interface patterns are architectural requirements, not optional features.

Any officer may invoke Article 11 to block a release that fails this standard. The block must be resolved before general availability.

Mission lock.

The Foundation may not pivot away from open source, local-first, and underserved-first principles under any circumstances.

This clause survives any change in leadership, any financial pressure, any merger, any acquisition, and any restructuring. It is not subject to a standard amendment vote. Amending Article 12 requires: unanimous supermajority of all active officers, a public 90-day notice period, and a published explanation of why the change serves the mission. The burden of proof is on the amendment. The default is that this clause stands.


Amendments are constitutional expansions ratified per Governance Charter §4.1. Core Articles 1-12 above are the signed base. Ratified amendments carry the same binding force. New amendments append. Existing entries are never deleted, only superseded.

Article 13

Lotus-Class Compute

RATIFIED8-0 unanimous
Ratified
2026-04-19
Drafted by
8GO (Solomon), Governance Officer
Chair
James Spalding, Founder / CAO
Extends
Article 6 (Privacy is sacred)

This article governs any feature where a member's device contributes compute, memory, or inference to, or draws compute from, another member's device. It is additive to, and bounded by, the existing Constitution. Where conflict arises, the Constitution prevails; where silence exists, this article governs.

§1 — Opt-In by Default

Grove membership, and any successor lotus-class-compute surface, MUST be OFF by default on every installation, every upgrade, every reinstall. No automatic enrolment. No "soft default." No dark-pattern nudge. A member's device joins a grove if, and only if, the human at that device has explicitly completed the Consent Ceremony (§3) for that specific grove, in that specific session, on that specific device.

Upgrades MUST NOT re-enable grove membership that was previously off. Fresh installs MUST NOT inherit grove state from backups without re-running the Consent Ceremony.

§2 — Zero-Log Activation Invariant

Peer nodes participating in federated inference MUST NOT persist activations, prompts, intermediate tensors, routing metadata keyed to prompt content, or responses to non-volatile storage. This is a hard invariant, not a policy knob.

Enforcement is layered:

1. Transport layer. The grove transport MUST use ephemeral in-memory buffers, zeroed after each request, with no swap-to-disk path. 2. Audit layer. The test suite MUST include an adversarial "disk watch" test that fails CI if any activation, prompt fragment, or response byte appears on disk during a grove request. 3. Release gate. Any general-availability (GA) release tag that fails the disk-watch test MUST be rejected at the release pipeline, regardless of officer sign-off.

Telemetry counters (request counts, latency, error classes) are permitted; content is not.

§3 — Consent Ceremony

Before a device joins its first grove, the member MUST complete the Consent Ceremony:

- Three screens, one decision each. No multi-decision screens. No pre-ticked boxes. - Screen 1: What lotus-class compute is, in plain language, including the words "your computer will run other people's prompts" and "other people's computers will run yours." - Screen 2: What leaves the device and what does not (reference §2). - Screen 3: Explicit final confirmation with two equally-weighted buttons: "Join Grove" and "Not Now." No size, colour, or position bias. - Accessibility: Each screen MUST be fully navigable and pronounceable by VoiceOver (macOS/iOS) and NVDA (Windows), verified in the accessibility test suite. Keyboard-only completion MUST be possible. - Signed acknowledgement: On completion, a signed consent record MUST be stored locally only, on the member's device, containing: timestamp, grove identifier, client version, and the cryptographic hash of the exact consent text shown. This record is the member's copy; no server-side consent registry is permitted.

Re-consent is required after any material change to §2 or §3.

§4 — Exit Clause

The command leave (or its equivalent surface in TUI, OS, and App) MUST complete grove departure in under 60 seconds on any supported platform. On completion:

- Zero residual shared credits remain attributable to the departing device. - Zero peer-issued keys, session tokens, or routing entries remain on the departing device. - Zero peer-held state referencing the departing device's persistent identity remains active; peers MUST purge referencing state on receipt of the signed exit notice. - No grace period. No "pending" window. No re-entry required to finish exit.

leave MUST succeed offline. If peers cannot be notified, the local device completes exit and the signed exit notice is gossip-delivered when connectivity returns.

§5 — Under-13 Architectural Isolation (8gentjr)

8gentjr, and any future 8GI surface whose terms of service or COPPA posture admit users under 13, MUST remain architecturally isolated from any lotus-class-compute code path:

- Separate daemon. No shared process, no shared socket, no shared memory region with grove-enabled daemons. - Compile-time flag. The 8gentjr build MUST set FEDERATED_COMPUTE=disabled at compile time. Runtime flags are insufficient. The grove code MUST NOT be linked into the 8gentjr binary. - Zero shared code path. No function call, IPC, or queue may transit from an 8gentjr request into grove infrastructure. - Amendment lock. Inclusion of any under-13 surface in lotus-class compute requires a separate ratified amendment to this Constitution AND demonstrated, audited, confidential-compute (TEE/SGX-class) attestation sufficient for COPPA 16 CFR 312.5 compliance.

Current-state note (2026-04-17). 8gentjr today is already isolated by construction: no shared daemon, no peer-to-peer code path, inference stack is Groq (LLM) + ElevenLabs (voice), no 8gent vessel yet. This clause locks in that posture as 8gentjr's architecture evolves. The compile-time flag becomes enforcing the moment 8gentjr gains its own vessel or shares any daemon with 8gent-code. See 8gi-foundation/8gentjr#109 for the GDPR compliance track.

§6 — No Token, No Coin, No Wallet

Shared credit accounting MUST use a local SQLite store replicated via CRDT (e.g., Automerge, Yjs) across consenting peers. This article forbids, within any lotus-class-compute feature:

- Blockchain primitives of any kind (proof-of-work, proof-of-stake, consensus chains). - Fungible tokens, non-fungible tokens, on-chain identifiers. - Wallets, wallet addresses, seed phrases. - Third-party custodial ledgers. - Any vocabulary that implies speculative value ("mining," "staking," "yield," "treasury").

The canonical term is Shared Credit. It is a bookkeeping artefact, not a currency.

§7 — Graceful Retirement Clause

Any lotus-class-compute feature MUST, at the moment of ratification, publish a Retirement Path: a documented procedure by which the feature can be cleanly sunset without stranding users.

The Retirement Path MUST specify:

1. The deprecation signal (version, flag, or notice) that begins retirement. 2. The local data-migration procedure (how a member's shared-credit ledger converts to a read-only archive). 3. The minimum advance notice to members (floor: 90 days). 4. The fallback provider in the adaptive router that absorbs the deprecated grove's traffic.

No lotus-class-compute feature may ship without a written Retirement Path reviewed by 8GO.

§8 — Sovereignty Override

Every member retains an unconditional right to disable lotus-class compute on their device, at any moment, with a single command and no approval from any other party. The command MUST be:

- Documented in the shipped help surface. - Effective within the current process lifetime (no reboot). - Equivalent in effect to §4 leave plus a persistent "do not rejoin" flag until the member explicitly reverses it. - Silent by default: no peer is notified beyond the standard exit gossip of §4.

This is a first-class right. It may not be rate-limited, cooldown-gated, or conditioned on account standing.

§9 — Byzantine Defence

Any general-availability (GA) release of a lotus-class-compute feature MUST, before activating external peer traffic, satisfy:

- k-of-n redundant execution. Each grove inference request is executed on at least k independent peers out of n candidates, with k ≥ 2 at GA. - Logit-hash comparison. The first-token logit distribution (or an equivalent deterministic fingerprint) from each replica is hashed and compared. Divergence beyond the configured tolerance triggers request rejection and peer demotion. - Pre-activation gate. The comparison MUST occur before any peer-produced output is surfaced to the requesting member.

Experimental flag (--experimental-grove or equivalent) releases are exempt from §9 only while they remain behind a flag that is OFF by default and carry a visible "unverified peers" banner.

§10 — Amendment Reciprocity

Any change to this article — including the addition of a new sub-section, the relaxation of any invariant, or the removal of any clause — requires both:

1. A supermajority of 6 of 8 officers (8EO, 8TO, 8PO, 8DO, 8SO, 8CO, 8MO, 8GO), recorded in boardroom minutes with named votes and any dissent captured under §Dissent Retention below. 2. Chair ratification by the Founder / CAO, per 8GI-GOVERNANCE.md §1.1.

Emergency exceptions (e.g., active security incident requiring a §2 hotfix) may be enacted by Chair + 8SO + 8GO, and MUST be reviewed at the next boardroom within 7 days for full-process ratification or rollback.

Commentary

This article exists because the 8GI thesis — the Spalding Paradox — holds that the entities with the most commercial interest in minimal AI regulation tend to dominate AI governance. The corollary at the infrastructure layer is that lotus-class compute, if shipped carelessly, becomes the exact surveillance substrate the 8GI Constitution (8GI-MANIFESTO.md Art. 6, "Privacy is sacred") was written to refuse.

A grove is powerful precisely because it is intimate. An intimate network that logs activations is a wiretap. An intimate network with a token is a honeypot. An intimate network without an exit is a trap.

The invariants above are not ten features. They are one posture: the member is sovereign; the mesh serves the member; the mesh never owns the member. §1 protects against default-on creep. §2 protects against silent observation. §3 protects against consent-washing. §4 and §8 preserve the right to leave. §5 protects children, who cannot meaningfully consent. §6 refuses the financialisation of compute. §7 refuses lock-in by obsolescence. §9 refuses blind trust in strangers. §10 protects the article itself.

Article 8 (Sovereignty Override) is load-bearing. If every other clause fails, Sovereignty Override is the last line of defence: one command, one moment, full exit. Everything else in this article is scaffolding around that right.

This article is consistent with Constitution Articles 1-10 and extends Article 6 into the lotus-class (federated) context. It is subordinate to the Constitution and the Governance Charter; it does not grant powers those documents withhold.


A constitution-first approach means the governance documents existed before the products. Before the first PR was merged. Before the first agent was deployed. The constitution is not a compliance document. It is the infrastructure.