Constitution for a Humane Civilization
A Charter of Human Dignity, Stewardship, and Non-Coercive Order

A public design workbook for separating basic needs, markets, and public power so wealth cannot quietly become control over other people.

Start with a life, not a mechanism: a person may lose work, status, health, documents, popularity, or money and still remain a person whose hunger, shelter, medicine, and basic dignity matter. This project asks whether a society can protect that truth without crushing markets, local freedom, enterprise, dissent, or responsibility.

That is a serious claim, and this draft does not ask to be trusted because the aim sounds humane. It is a human attempt to design rules that serve people rather than dominate them. It must be judged by whether it protects the vulnerable, preserves dignity, tells the truth about failure, and remains open to correction.

• What this is
• If you're new
• If you're skeptical
• Reader app — open in browser · download desktop app · run from source
• Current status
• Plain-language rule
• The core separation
• The current architecture
• Architecture flow
• Document set
• Technical specifications
• Hardening history
• Major risks
• What this system is not
• What will go wrong
• Scale readiness checklist
• How to engage
• Fork, remix, or adapt this
• License

The Humane Constitution is a design for a society where everyone has a basic needs floor, markets still work, and public power cannot be bought.

The core problem is simple: when food, housing, medicine, business, and political influence all depend on the same money, wealth becomes power over other people's safety.

This is not a live government. It is not a finished rollout plan. It is a public working draft with stress tests, known failure paths, proposed fixes, and validation checks.

Start with the human case before the technical machinery:

1. One-Page Overview for the shortest public introduction
2. Life Under The System for one-year pressure stories about ordinary people
3. Rights Layer for the plain-language rights summary
4. How Big Companies Work Here for how profit can remain without hostage power
5. FAQ for common objections in plain language
6. White Paper for the fuller public explanation
7. Public Readiness Guide for status, skeptic, and audit paths

Start with the Public Readiness Guide. It states what the project claims, what is only designed, what still needs evidence, and which objections deserve the most pressure.

If the design feels too abstract, read Life Under The System first. The stories are not promises. They are concrete pressure cases for asking whether the rules would protect dignity under stress.

For deeper critique:

1. Claims & Evidence Register for claim status and proof gaps
2. Evidence Ladder for what counts as stronger proof
3. Abuse Case Library for bad-actor patterns
4. Pilot Evidence Roadmap for what must be tested before scale-up

The repository ships with a reader app: a clean, searchable way to read the whole project. It includes the main text, public explainers, annexes, threat register, patch log, and evidence documents.

This is the recommended path for most readers.

A hosted version of the reader is available at:

→ humane-constitution.vercel.app

Click the link. That's it. Nothing to install.

If you prefer a desktop window (works offline, no browser needed):

1. Go to the Releases page of this repository on GitHub.
2. Under the most recent release, find the file for your computer:
   • Mac: download the .dmg file
   • Windows: download the .msi or .exe file
   • Linux: download the .AppImage or .deb file
3. Open the downloaded file and follow the normal install steps for your system (same as installing any app).

If you're on a Mac and see a warning that the app is from an "unidentified developer," right-click the app and choose Open — this bypasses the warning for apps that haven't been submitted to Apple's store.

If you want to run the app from source — for example, to propose edits or work on the codebase — you'll need a few tools installed first. This path assumes familiarity with a terminal.

Prerequisites: Node.js 18+, Python 3.10+, and (for the desktop wrapper) Rust + Tauri prerequisites.

cd app
npm install
npm run dev          # opens in browser at http://localhost:5173
npm run tauri dev    # opens as a desktop window

npm run dev and npm run build both regenerate the corpus first via python3 ../scripts/export_corpus.py, so the reader always reflects the live markdown on disk. To regenerate manually: npm run generate:corpus. To verify the generated corpus matches what's checked in: npm run check:corpus.

Build a release binary:

cd app
npm run tauri build  # produces a platform-native installer in src-tauri/target/release

Keyboard shortcuts: press ? inside the reader to see all shortcuts. Press Cmd K (Mac) or Ctrl K (Windows/Linux) to search across the full document set.

This project is strongest today as a design, critique target, and public working draft. It is not scale-ready.

What exists now:

• constitutional text and public explanations
• a threat register and patch log
• adversarial simulations and stress-test documents
• evidence registers and dedicated test packages for unresolved load-bearing claims
• a validation pipeline and reader app

What must still be proven:

• pilot evidence at real scale
• a non-coercive identity and recovery stack
• reliable measurement of essential capacity
• a legitimate founding coalition
• essential-sector refusal survivability for oil, energy, medicine, logistics, and PBM-style intermediaries

The right response is neither blind belief nor dismissal. The useful response is specific critique, hard testing, and evidence.

This project should be understandable to people who never went to college. Legal, policy, and software terms should be avoided unless they are truly needed. When a formal term is needed, explain it in plain English first.

The project-wide writing rule is in Plain-Language Standard. Future edits should follow it, especially in public pages, the reader app, the constitution overview, and threat summaries.

The system separates three things that most societies mix together:

• basic needs
• markets
• public power

It does this with five tools:

The walls between these tools are the system.

Those walls are meant to prevent three collapse states: survival becoming dependent on trade, wealth becoming public power, and temporary advantage becoming permanent dominance. See the Architecture Source Map for the source-backed version of that framing.

Essential Access protects the survival floor. Voice shapes bounded civic priorities. Service Record governs readiness for rotating public roles. Shared Storehouse appears only during verified shortage.

Flow is public money rather than privately created bank money. It is primarily digital, secured with cryptographic methods, and paired with physical cash or equivalent offline instruments for resilience and privacy.

The current main text uses one Founding Order and seven articles.

• Founding Order — Local Choice, Consent & Exit — who joins, how decisions stay local when possible, and how a place can leave.
• Article I — Rights & Rules — the rules that cannot be quietly changed.
• Article II — Personhood, Identity & Continuity — One-person continuity, recovery, guardianship, and dependent protection without surveillance scoring.
• Article III — Real Capacity & Reserves — how the system measures food, water, energy, shelter, care, medicine, and reserves.
• Article IV — Survival — how Essential Access becomes real access to basics.
• Article V — Markets, Commons & Public Finance — Flow, housing, land, business, public banking, and public funding.
• Article VI — Voice, Service Record & Public Decisions — how people help set priorities without creating social credit.
• Article VII — Public Records & Warning Systems — dashboards, audits, and early warnings.

The constitution is built in five layers. Each layer depends on the one above it and feeds signals back up.

Feedback loops: Article VII (Transparency) sends audit visibility back up to Article I (Rights) and public accountability signals back to Article V (Markets). Article VI (Voice) sends priorities and legitimacy inputs back to Article V. Article V sends production and housing flows back down to Article III for physical constraint updates. The system is designed to self-correct — failures surface at the accountability layer and travel back up to the rights and constraints layers rather than accumulating silently.

The annex corpus now lives entirely as standalone documents. Use the Annex Directory as the entry point for constitutional annexes, hardening clauses, and detailed specifications.

The repository includes a corpus validator for the live constitutional document set:

• python3 -m pip install -e .[test] installs the reproducible simulation and test dependencies.
• python3 scripts/validate_corpus.py checks local markdown links, annex-index coverage, FC/T/P identifier integrity, and deprecated live terminology.
• python3 -m pytest -q runs the simulation test suite from the packaged environment.
• npm run check:corpus from app/ regenerates the reader corpus and fails if generated files are not committed.
• GitHub Actions runs the same validator on every push and pull request, alongside frontend build, generated-corpus drift, and reader regression checks.

The project names its biggest failure paths instead of hiding them.

Essential Access depends on knowing what society can actually provide.

If the system measures food, housing, medicine, water, or energy badly, people can be harmed. A captured measurement system could make shortages look fake or make capacity look larger than it is.

The defense is to use several different measurement sources, public methods, direct physical checks, and review when sources start copying the same assumptions.

Remaining risk: the people who define "good measurement" still hold power.

Essential Access is not supposed to become money. But people may try to trade around the rules.

Example: a broker pays someone in Flow to use their Essential Access for someone else. Or a business prices services in "Essential Access equivalents" without touching the official system.

The defense is to make Essential Access personal, limit delegation, watch for broker patterns, and focus enforcement on scalable abuse rather than ordinary help between people.

Remaining risk: small hidden exchanges will still happen. The goal is to stop them from becoming a power structure.

A later government could try to hollow the system out while keeping the words on paper.

It could defund delivery, appoint hostile officials, weaken measurement, or stop publishing records.

The defense is a protected basic floor, transition audits, public triggers when institutions are left empty, and exit rights for places that no longer consent.

Remaining risk: no document can fully stop a determined political movement with enough power. The design can buy time, raise the cost, and make the attack visible.

The design assumes some large firms will not cooperate voluntarily.

Oil, energy, medicine, logistics, PBM-style intermediaries, and other essential-sector actors may leave, litigate, lobby, delay, route control through affiliates, or demand special exemptions.

The defense is not moral persuasion. The defense is a profitable compliant path, refusal drills, reserve drawdown models, public/cooperative fallback capacity, compliant-bidder independence checks, beneficial-owner tracing, and temporary receiver authority when a survival chokepoint is at risk.

Remaining risk: the legal authority to intervene may exist before the physical capacity to replace the refusing actor exists. That gap must be tested before any scale-up claim.

The system has been adversarially stress-tested:

Current status is tracked in the Patch Log inventory. The Threat Register currently has no fully open threat with no mitigation path, but many controls still need pilot evidence, activation, and outside review.

The system acknowledges expected operational imperfections before they occur:

• PCRP false triggers — will happen; detection, termination, and public post-mortem within 7 days are the designed response
• Oracle disputes — will happen; conservative defaults protect access while disputes resolve
• Shared Storehouse scarcity activations — will happen during genuine shortage; managed rationing instead of price-spike exclusion
• Enforcement errors — will happen; partitioned wallets and due process are the correction mechanism
• Measurement uncertainty — is permanent; published confidence bands are the honest response

The system's commitment: every failure in these categories is published publicly, with a timeline and a correction path. Silence is the violation, not the failure.

Scale readiness requires:

• Public readiness guide — see Public Readiness Guide
• Claims and evidence register — see Claims & Evidence Register
• Pilot evidence roadmap — see Pilot Evidence Roadmap
• Formal acceptance of PROPOSED patches (pilot evidence required)
• CFRL one-page publication — see Rights Layer
• Adversarial narrative simulation — see Adversarial Narrative Simulation
• Annual compound simulation — see Annual Compound Simulation
• Essential-sector refusal drills — see Essential-Sector Refusal Test Package
• Legitimate founding coalition

The Formal Acceptance Protocol defines the pathway from design to operation.

If you want the shortest public intro: read the One-Page Overview first.

If you want the human path first: read Life Under The System, then the White Paper.

If you want the public case first: read the White Paper, then the Rights Layer and Public FAQ.

If you want to stress-test the design: read the Threat Register after the White Paper.

If you want the exact rule text: read the Humane Constitution after that.

To critique, challenge, or contribute: open an Issue with your specific objection, the section it applies to, and your proposed alternative. Vague objections will be asked to specify. Specific objections will be taken seriously.

This project is released so people can build from it.

You are welcome to:

• fork the repository
• copy individual sections
• adapt the structure for your own community or project
• translate it into plainer language
• make competing versions
• use the diagrams, threat model, or reading path as inspiration
• share it with people who might pressure-test it

You do not need permission to disagree, revise, or branch away from the main version.

The only request: preserve attribution where reasonable, and make clear what you changed so readers can compare versions honestly.

To cite this work: see CITATION.cff in this repository.

This work is released under Creative Commons Attribution 4.0 International (CC BY 4.0). You may share, adapt, and build on it for any purpose, including commercial, as long as you give appropriate credit.

This is not a claim of perfection. It is a rule design for keeping basic needs, markets, and public power from collapsing into one tool: money.