Civic Blueprint

An open-source blueprint for a more capable, humane society in the age of AI.

Why this exists

We are entering a period of rapid technological change, institutional strain, and growing concentration of power.

At the same time, new tools — especially in artificial intelligence — create the possibility of dramatically improving how society functions.

The question is not whether the future will change.

The question is:

Who designs it, who benefits from it, and who gets left out?

What is Civic Blueprint?

Civic Blueprint is an open, collaborative effort to think more seriously about what kind of society we are building — and what it would take to make that society more capable, more humane, and more difficult to capture.

It focuses on:

increasing institutional capacity without sacrificing democratic accountability
ensuring AI expands agency rather than concentrating power
reducing artificial scarcity in essential systems like housing, healthcare, and education
building practical, implementable frameworks — not just abstract ideas
honestly diagnosing who benefits from dysfunction and what resistance reform will face
being willing to expand who and what counts as the world changes

This is not a manifesto for a perfect world.

It is a working blueprint for building a better one.

How these documents were built

The current project documents were not written by a single author in a single pass. They were developed through iterative drafting by multiple AI models using different prompts and review protocols, then synthesized, edited, and approved by the project steward.

That process has strengths and weaknesses. It produces breadth, rapid iteration, and explicit adversarial challenge more easily than a conventional drafting process. It also carries risks of convergence, shared framing, and false confidence. The project's review protocols exist partly to make those strengths and weaknesses visible rather than hide them.

The documents in this repository should therefore be read as steward-curated working syntheses: real commitments, real hypotheses, and real design directions, but not claims of neutral authorship or finished consensus.

Core documents

The project is built on four interconnected documents:

Principles
Seventeen foundational commitments — from dignity and essential needs to AI governance, ecological limits, justice, legitimate collective power, and expanding moral consideration.
Problem Map
A layered diagnostic of where systems are failing, why they stay broken, and who benefits from the status quo.
Systems Framework
Fourteen domains, each analyzed through diagnostic, design, and strategic questions — including dependencies, leverage hypotheses, failure modes, and candidate reform sequences. The design companion to the Problem Map.
Contributing
How to participate, what quality means here, and how the project practices the transparent governance it advocates.

Extended artifacts

Proposal Catalog
135 concrete reform proposals across all 15 Problem Map domains, generated through a 30-round autonomous agent stress test (Exchange #13). Each proposal is individually listed for steward review, feedback, and further brainstorming. AI-generated hypotheses, not endorsed positions.
Formation Documents Analysis
The project-2028 analysis workspace for comparing Civic Blueprint's principles against constitutions, charters, declarations, and organizational founding texts. Retained source texts now live in external-formation-docs.
Source Digests
Curated reference documents for external media, interviews, and commentary that intersect with the project's analysis. Source digests capture thematic parsing, research context, and project-mapping in a permanent form that multiple exchanges can reference without duplicating context.

Internal project management

These documents support steward coordination and are not published on the website:

Roadmap
Recommended next steps drawn from exchange findings. Tracks what has been completed, what is in progress, and what comes next — including the structured practitioner critique, fast-feedback validation case design, and recursive uplift theory revision.

How to contribute

This project is built in the open, and open means more than read access.

Start with CONTRIBUTING.md for the full guide. The short version:

Read the core documents first
Open an issue describing what you want to contribute
Submit a pull request with your proposed changes
Expect honest feedback

Domain expertise, case studies, reform proposals, analytical critique, and implementation analysis are all needed — especially from outside the US/Western context.

AI-assisted contributors are welcome. See Principles and Contributing for guidance.

How feedback intake works

Public feedback from the website response path is collected as issues labeled website-submission. These submissions are treated as organic feedback by default and reviewed with a steward triage rubric documented in Contributing.

The structured practitioner critique track is separate: invited reviewers, structured prompt, defined collection window, and separate synthesis output (see the internal Roadmap, Recommendation 2).

For day-to-day handling, stewards use the internal Website Submission Triage Checklist.

Status

Early stage. Actively being developed.

The foundational documents are in place. The Problem Map has undergone a major revision incorporating multi-agent review, adding democratic process as a core domain, core bottleneck summaries for scannability, a structural entry points analysis featuring recursive uplift, and an updated dependency map with explicit recursive loops. The Systems Framework has been revised to add dependency mapping, leverage hypotheses, failure-mode analysis, and a sequencing section that synthesizes cross-domain reform chains — evolving from a parallel domain analysis into the project's strategic design layer.

Two parallel tracks are now in focus (see Next Steps):

A public entry point — a website that makes the project's analysis readable and navigable for the domain experts, scholars, and practitioners whose perspectives are most needed.
Computational dependency analysis — formalizing the dependency graph that the Problem Map and Systems Framework describe in prose, and subjecting the project's leverage hypotheses to quantitative analysis.

Progress on Track 1 now lives in the companion website repository (civicblueprint.org):

Website Phase 1 Brief — Phase 1 scope, audience, and launch plan
Homepage Copy Draft — current homepage draft
Proof-of-Usefulness Memo 01 — the first comparative proof-of-usefulness memo (housing permitting + AI governance)

The project is currently in an adversarial review phase — subjecting its foundational documents to structured challenge before building outward. A full navigational index of all exchanges — including dependency links, status, and a visual dependency graph — is available at Exchange Index. Completed exchanges:

Principles — Adversarial Review Exchange: Three rounds of alternating adversarial and constructive review of the project's constitutional layer, identifying structural gaps (justice, legitimate coercion, prioritization), internal contradictions (Principle 13 vs. substantive commitments), and unexamined assumptions (functional-state context, unacknowledged philosophical tradition).
Post-Systems Framework Next Steps — Adversarial Review: Includes adversarial challenge of the two-track strategy, questioning resource feasibility, the risk of false precision in graph analysis, and proposing an alternative sequencing starting with a proof-of-usefulness artifact.
Review Protocol Design Exploration: Two-pass exploration of what review protocols beyond adversarial review the project might need — proposing seven candidate protocols, then subjecting them to adversarial challenge. Concludes that two new protocols (coherence audit, historical parallel test) should be formalized and five others should be folded into the adversarial protocol as standing questions.

The project uses four structured review protocols, each addressing a different failure mode:

Adversarial Review Protocol — Challenges claims. Counteracts convergence bias in multi-agent exchanges. Applied when exchanges generate strategic claims, produce near-total convergence, or will influence the project's direction.
Coherence Audit Protocol — Checks internal consistency across documents. Catches assumption drift, broken cross-references, and unincorporated exchange recommendations. Applied after major document revisions and on a regular schedule.
Historical Parallel Test Protocol — Grounds reform proposals in historical evidence. Tests leverage hypotheses and reform sequences against real-world cases where structurally similar reforms were attempted. Applied when proposals reach "working hypothesis" confidence.
Comparative Alignment Protocol — Compares Civic Blueprint's principles against constitutions, charters, declarations, and organizational founding texts. Applied when the project wants to test overlap, divergence, silence, or possible principle-level gaps across formation documents.

The project continues to need:

Contributors with domain expertise across all fourteen system domains
Global perspectives to challenge and broaden the analytical frame
Case studies from any context that demonstrate what works — especially evidence that tests the project's leverage and uplift hypotheses
Implementation analysis to bridge from framework to action
Adversarial review of the project's strategic claims — especially from human reviewers external to the project

License

MIT