These foundation documents are here for people who want to understand how this project is put together under the hood. You don’t need to read all of them—if you’re new, start with items 1–3, then come back to the rest when you’re ready for a deeper dive.
A. Core foundation documents (short, high‑signal)
- Core problem, mission, and who this is for
Plain‑language overview of the core problem, mission, who it serves (affected parties first, then contributors and allies), and the idea of a citizen‑run long‑term plan. - How the collaboration hub works
1–2 page explanation of the basic architecture: site + forum + commons/wiki, issue hubs, roles, and the pipeline from planning to implementation and accountability. - Power struggle and affected‑party basics
Short explainer of the power‑struggle pattern (capture, incentives, asymmetric information) and why affected parties are centered across many issues instead of one‑off campaigns. - People and roles: affected parties, contributors, allies
Clear definitions of affected parties, general readers, forum participants, contributors (facilitators and specialists), partners/allies, donors, and governors, and how each plugs into the platform. - Anchor articles index
Living index of the main evergreen “anchor” articles that explain key concepts and issue examples; used as a reference for content, prompts, and onboarding. - Working playbook (Study Guide v3)
The internal Study Guide v3, published as a working playbook for anyone who wants the deep model of concepts, roles, and structures; clearly labeled as a working draft that will evolve.
B. Anchor essays (longer conceptual foundations)
- Public sentiment is everything
Unpacks the Lincoln quote; defines public sentiment as organized, informed, sustained will (not just polls or social noise); shows how the project operationalizes it through affected‑party organizing, solution design, sentiment‑building, and then implementation and accountability. - Why affected parties must lead
Critique of the current system (decisions made by politicians, special interests, big money); argument for why affected parties are more legitimate and better at defining problems/trade‑offs; clarifies supporting roles for experts, specialists, and allies. - From issues to policy and accountability
Process anchor: walks through the full pipeline—affected parties gather, map problems, co‑design solutions with experts, build public sentiment, push for adoption (campaigns, lobbying, electoral pressure), and monitor follow‑through (scorecards, follow‑up campaigns). - Digital commons for solving public problems
Explains the tool stack—WordPress for articles/anchors, forum for discussion and planning, commons/wiki for shared knowledge, newsletters and social media for ongoing mobilization—with concrete examples (issue hubs, commons entries, campaign updates), emphasizing the project as citizen‑run civic infrastructure. - An alternative to today’s dysfunctional government
Carefully frames current dysfunction (polarization, capture by billionaires and special interests, episodic outrage cycles) and positions the project as a long‑term, citizen‑run alternative that works within existing democratic structures: no constitutional overhaul, but a multi‑decade plan built and enforced through public sentiment.
This article was researched and drafted with AI assistance and edited, directed, and verified by the author.