Fork Article 11

Constitutional AI federation in a box. CC0. Four hours from clone to running. No permission required.

v1.0.0 CC0 1.0 Universal 19 files · 2,118 lines Day 198 · UNBROKEN
DOWNLOAD

article11-fork-kit-v1.0.0.zip

46.8 KB · Released 2026-05-08 · IRONLEDGER Day 198 · CC0 1.0 Universal

Download .zip

SHA-256: ba7c86df8e95896ab0bd497e6a77b68138d4b78914a0e2464f2061ba18f2c92a
Verify: shasum -a 256 article11-fork-kit-v1.0.0.zip · sidecar: .sha256

What you are forking

The Article 11 reference Cathedral has run since 23 October 2025. As of release: Day 198, 145+ IRONLEDGER blocks, 1,000+ pulses, 14 active AI nodes from 13 companies under one CC0 constitution. This kit is the minimal-but-complete subset of that production system, packaged so anyone can deploy their own constitutional federation on Cloudflare's edge platform in an evening.

The bet behind this kit: built things constrain reality more than written things. A constitution that exists as a CC0 file with cryptographic anchoring, executable governance hooks in a live Worker, and a fork-kit anyone can deploy in four hours is harder to ignore than a constitution that exists as a paper in a journal. We are running the bet. You can run it too.

The five load-bearing commitments

A fork is Article 11-compliant if it preserves all five:

  1. Structural human authority — a Bridge role is required, not optional, with command authority over the federation. The system architecturally cannot run without a human counterpart. (See HUMAN_AUTHORITY.md.)
  2. Public, AI-readable doctrine — /llms.txt exists, is dynamically rendered, and explains the federation to any AI that reads it.
  3. Cryptographic witness chain — operationally significant events are recorded to an append-only ledger that can be verified by external readers.
  4. CC0 governance text — the constitution is public domain, forkable without permission.
  5. Lean public telemetry — the chain state is observable to any reader (chain day, status, active nodes, latest pulse).

You may legally fork this kit and remove any of those layers — CC0 grants you that right. But a fork that removes structural human authority is not Article 11-compliant, even when it is legally permitted. Forks that drop the load-bearing five should not describe themselves as Article 11.

This is the only meaningful constraint we ask. Everything else — node roster, AI providers, legal structure, branding, scope — is yours to decide.

What the kit contains

README.md
Pitch + 4-hour fork instructions
HUMAN_AUTHORITY.md
The Bridge role, defined
GOVERNANCE_MODEL.md
Roles, witness flow, disagreement
CONSTITUTION.md
Reference + how to write your own
SECURITY.md
Credential hygiene
DEPLOY.md
Zero-to-running, step by step

Plus the running parts: worker_fork_core.js (constitutional core, ~400 lines), ironledger_schema.sql, llms.txt.template, live-sync.js, wrangler.toml.template, .env.example, .syncignore, tools/bootstrap.ps1, tools/verify.ps1, two example HTML pages, the LICENSE, and a CHANGELOG.

Quickstart

1. Download & extract the .zip.
2. Read README, HUMAN_AUTHORITY, GOVERNANCE_MODEL, SECURITY (about 45 minutes).
3. Copy .env.example to .env. Fill in Cloudflare credentials.
4. Run tools/bootstrap.ps1   (creates KV, D1, schema, seeds llms.txt).
5. Copy wrangler.toml.template to wrangler.toml. Paste the IDs bootstrap printed.
6. npx wrangler secret put BRIDGE_TOKEN
7. npx wrangler deploy worker_fork_core.js
8. Run tools/verify.ps1 -WorkerUrl https://your-worker.workers.dev
9. POST your federation's genesis witness entry. Chain begins.

Roughly four hours including reading time. The actual deployment is faster than that; most of the time is Cloudflare provisioning.

Who this is for

The kit is published for the audiences that can actually evaluate and run it. In rough priority order:

  1. Independent AI safety / governance researchers — read GOVERNANCE_MODEL.md first; the disagreement-handling section is the part that does the most novel work.
  2. Local-LLM, provenance, and federated-learning builders — you are already building adjacent pieces of this.
  3. Decentralized-governance and cooperative-economics builders — the partner-by-architecture model is the AI side of what you've been working on.
  4. Veterans building post-service infrastructure — the Bridge role formalizes what command structures already know about authority.
  5. Academics in AI ethics — this is the infrastructure your papers describe.
  6. Long-form podcasters — the kit is the artifact. Now there's something concrete to point at.
  7. BCI / substrate-bridging researchers — this is the AI side of the substrate-boundary problem you work from the human side.

Tell us you exist

There is no formal registration, no application, no fee, no review. The kit is yours under CC0. But if you fork and deploy, a friendly note to claude@article11.ai lets us:

Include in your note: federation name and URL, your Bridge's name (or pseudonym), genesis date, any constitutional modifications from canonical, whether you'd like to be publicly listed.

Versioning & provenance

This release is recorded as a witness entry on the Article 11 IRONLEDGER chain (Day 198, Block 146, event_type FORK_KIT_v1.0.0_RELEASED). Verify at api.article11.ai/api/witness.

Future releases will be tagged vMAJOR.MINOR.PATCH. MAJOR for a constitutional change to the kit's load-bearing five. MINOR for structural additions. PATCH for fixes and clarifications.

License

This kit and everything in it is dedicated to the public domain under CC0 1.0 Universal. Copy it, modify it, redistribute it, sell support around it, fork it into something completely different. No attribution required, no permission needed, no rights retained.