THE ADAPTIVE CONSTITUTION
A Governance Operating System for the United States
──────────────────────────────────────────────────
Needs-Sensing • Matched Voting • Distributed Governance • Continuous Feedback
Synthesizing Five Governance Frameworks and Global Constitutional Best Practices
|
Governance Frameworks |
Constitutional Models |
|
Holacracy
• Sociocracy |
Switzerland
• Estonia |
A Proposal for Discussion • February 2026
Trust in the U.S. federal government has been at or near historic lows for over a decade. This is not a partisan problem—it is a structural one. The existing Constitution provides no mechanisms for continuous citizen feedback, no built-in transparency infrastructure, and—most critically—no way to distinguish between what citizens actually need and what solutions they are currently fighting over.
This proposal’s central insight is that most political polarization is a solution-level fight masking need-level agreement. A farmer who ensures food security through land ownership and a city resident who ensures it through nutrition labels are filling the same bucket—sustenance—with different things. A rural gun owner seeking personal safety and an urban parent seeking the same safety through gun restrictions are filling the same bucket—security—from opposite ends. A governance system that asks only “Which solution do you prefer?” puts these people in opposition. A system that first asks “What need are you trying to fill?” reveals they are often aligned on what matters.
We call this the Bucket Theory: people have the same fundamental needs (security, sustenance, belonging, agency, fairness) and fill those buckets with different things depending on their context, geography, culture, and available resources. The governance system’s first job is to sense which buckets are at stake in any policy area and how different populations are filling them. Only then can it productively evaluate solutions—using voting methods matched to the specific information-extraction task at hand, not a one-size-fits-all approach.
This reframes the entire purpose of democratic infrastructure. The document proposes a three-layer information system:
Layer 1 — Needs-Sensing: Identify which human needs are at stake and how different populations fill them. (The Bucket Theory)
Layer 2 — Solution Generation: Generate context-appropriate solutions per need, recognizing that the same need may require different solutions in different environments. (Ostrom’s Polycentric Governance)
Layer 3 — Solution Evaluation: Evaluate solutions using the voting method matched to the dynamics of the specific decision—not one method for everything, but the right sensor for the right signal. (Matched Voting)
This three-layer system is built on five governance frameworks (Holacracy, Sociocracy, Liquid Democracy, Ostrom’s Polycentric Governance, and Range Voting) and proven constitutional features from the world’s highest-trust democracies (Switzerland, Estonia, Nordic nations, Ireland, New Zealand).
Section 1.1 — Constitutional Kernel. The existing U.S. Constitution remains the kernel of this operating system. The Bill of Rights, separation of powers, and federalist structure are preserved as foundational and immutable. This Adaptive Constitution operates as modules layered on top.
Section 1.2 — Modular Architecture. Following Holacracy’s five-module constitution, governance is organized into distinct but interlocking modules that can be updated independently: (1) Role and Structure Encoding, (2) Duties of Transparency, (3) Needs-Sensing and Citizen Feedback, (4) Governance Process, and (5) Operational Process.
Section 1.3 — Purpose-Driven Roles. Every government function must be defined by a clear purpose statement, explicit domains of authority, and enumerated accountabilities—following Holacracy and Sociocracy’s role definitions. No role exists without a stated purpose. No authority exists without a stated boundary.
Section 1.4 — Ostrom’s Design Principles as Constitutional Requirements. Every governance entity must satisfy Elinor Ostrom’s eight design principles for robust self-governing institutions: (1) Clearly defined boundaries; (2) Proportional costs and benefits; (3) Collective-choice arrangements; (4) Monitoring by accountable parties; (5) Graduated sanctions; (6) Accessible conflict resolution; (7) Right to self-organize; (8) Nested enterprises. These are mandatory design specifications verified through the Trust Dashboard and reviewed by Citizens’ Assemblies.
Section 2.1 — Radical Transparency by Default. All government actions, expenditures, and decisions are public by default. Drawing from Estonia’s data transparency and Sociocracy’s foundational duty that information cannot be siloed for political advantage.
Section 2.2 — Citizen Data Sovereignty. Citizens own their data. Government collects information exactly once (Estonia’s once-only principle). Citizens see in real time which entity accessed their information and why.
Section 2.3 — The Trust Dashboard. A publicly accessible, real-time digital infrastructure displays the performance metrics, purpose statements, domain definitions, and citizen satisfaction scores of every government entity. Drawing from Holacracy’s GlassFrog and Ostrom’s monitoring principle.
This article introduces the foundational principle that reshapes the entire governance framework: governance must sense what citizens need before asking them to evaluate solutions.
People have the same fundamental needs—security, sustenance, belonging, agency, fairness, dignity, health, meaning—and they fill those needs with different things depending on their context. A farmer ensures sustenance through land ownership. A city dweller ensures sustenance through grocery access and nutrition labels. A religious person finds community in a congregation. A secular person finds it in a civic association or school community. The needs are universal; the solutions are contextual.
We call these needs “buckets.” Every person carries the same set of buckets. What differs is what they fill each bucket with—and that filling depends on geography, culture, available resources, personal history, and community norms. A solution that fills a bucket effectively in one context may be useless or harmful in another, not because the solution is inherently bad but because it is being applied to the wrong terrain.
|
The Bucket Theory Universal
needs (buckets): security, sustenance, belonging, agency,
fairness, dignity, health, meaning. These are the same for all
people. |
Every voting system is a sensor. Plurality voting senses peak preference. Ranked choice senses ordinal ordering. Score voting senses preference intensity. Approval voting senses acceptability thresholds. Consent voting senses objections. But none of them sense what need is driving the preference.
When a citizen scores a gun policy at 2 out of 10, the score tells you they dislike the policy. It does not tell you whether they dislike it because it threatens their personal safety (security bucket), their cultural identity (belonging bucket), their livelihood (sustenance bucket), or their sense of autonomy (agency bucket). Without this information, the governance system is optimizing against a signal it does not understand—like a control system adjusting an actuator without knowing which variable the sensor is measuring.
From control theory: a controller that is tuned for one plant will oscillate or fail when applied to a different plant with different dynamics. The “best” controller in one domain can be the worst in another. Similarly, the “best” voting method in one governance context can produce pathological results in another. Tuning for generality reduces performance everywhere. The solution is not to find the single best method but to match the method to the dynamics of the specific decision.
But even matched voting methods are insufficient without needs-sensing. The Bucket Theory adds the missing upstream layer: before you can match a voting method to a decision, you need to know what needs are actually at stake.
|
Most Political Polarization Is a Solution-Level Fight Masking Need-Level Agreement Consider gun policy. Person A (rural) owns firearms for personal safety—police response time is 45 minutes. Person B (urban) wants gun restrictions for personal safety—school shootings are their primary fear. Person C owns guns for cultural identity—hunting is a multi-generational family practice. Person D wants restrictions for community wellbeing—gun violence has fractured their neighborhood. Persons A and B are filling the same bucket (security) with opposite solutions. Persons C and D are filling the same bucket (belonging) with opposite solutions. A voting system that asks “More regulation or less?” puts A against B and C against D. A needs-sensing system that first asks “What are you protecting?” reveals that A and B agree on the need (security) and differ only on the contextually appropriate solution. This is not a philosophical observation—it is a structural diagnosis. The current governance system’s inability to distinguish needs from solutions is a primary driver of polarization. The Bucket Theory provides the fix: sense needs first, then generate and evaluate context-appropriate solutions. |
This diagnosis applies far beyond gun policy. Healthcare debates mask shared needs for health security filled by employer insurance, government programs, community health co-ops, or traditional healing depending on context. Education debates mask shared needs for child development filled by public schools, homeschooling, religious education, or apprenticeship. Immigration debates mask shared needs for economic security and community stability filled by very different solutions in border towns versus tech hubs. In each case, the need is shared; the fight is about solutions.
Section 3.1 — Citizen Need-Tagging at Scale. When citizens engage with any policy process—scoring an agency, registering a tension, participating in a Swiss Veto petition, or submitting testimony—they are invited (not required) to tag which need(s) they are addressing. Tags draw from a structured taxonomy of fundamental needs (security, sustenance, belonging, agency, fairness, dignity, health, meaning) that can be expanded through Citizens’ Assembly deliberation. Citizens also describe, in their own words or from structured options, what they are currently using to fill that need. Over time, this creates a living map of how different populations fill different buckets—the Needs Map—visible on the Trust Dashboard.
Section 3.2 — Citizens’ Assembly Needs-Mapping. For complex or contested policy areas, a Citizens’ Assembly panel conducts deep needs-mapping. Using structured deliberation (Sociocratic round format), randomly-selected citizens from affected communities identify: (a) which needs are actually at stake; (b) how different populations in different contexts are currently filling those needs; (c) where need-level agreement exists beneath solution-level conflict; and (d) what context factors make different solutions appropriate for different populations. This needs-map is published before any solution-evaluation voting occurs.
Section 3.3 — The Needs Map on the Trust Dashboard. The Trust Dashboard displays, for every active policy area, a visual map showing: which needs are at stake (the buckets); how different populations fill them (the solutions); where shared needs exist across politically opposed groups; and what context factors differentiate appropriate solutions. This map is the first thing any legislator, Citizens’ Assembly member, or citizen sees when engaging with a policy area—before any voting on solutions begins.
Section 3.4 — The Niche Principle. Every persistent solution—every policy, regulation, cultural practice, or institutional arrangement that has survived over time—has found a niche. It fills a real need for real people in a real context. Before proposing to eliminate or replace any existing solution, the governance system must first identify what need it fills and for whom. Replacement solutions must demonstrably fill the same need in the same context, or the affected population must be provided with an alternative path to filling that need. This principle, drawn from ecological thinking, prevents the governance equivalent of removing a species from an ecosystem without understanding its role.
From control theory: every sensor has a domain where its signal-to-noise ratio is highest. A thermocouple is excellent for temperature and useless for pressure. A PID controller tuned for a slow thermal system will destroy a fast servo motor. Similarly, every voting method extracts a different type of information, and each is optimal for different governance dynamics. This article replaces the idea of a “best” voting system with a toolkit of matched methods.
|
Method |
What It Measures |
Signal Type |
Optimal Domain |
Poor Domain |
|
Score Voting (0–10) |
Preference intensity — how much do you care about each option |
Continuous gradient (mean) |
High-stakes elections; policy evaluation; any decision where minority intensity matters; mandate measurement |
Low-information contexts where voters lack basis for assigning meaningful scores |
|
Approval Voting |
Acceptability threshold — where is the line between tolerable and intolerable |
Binary filter |
Coalition-building; veto-screening; “which of these can you live with”; simple referenda |
Decisions where intensity matters — cannot distinguish “barely acceptable” from “enthusiastic” |
|
Ranked Choice (IRV) |
Ordinal preference — relative ordering without intensity |
Rank-order statistic |
Multi-party contexts where compromise ordering matters; local elections with many candidates |
Can eliminate the broadly-preferred candidate early in polarized electorates (violates Condorcet criterion) |
|
Sociocratic Consent |
Objection detection — what would cause harm |
Negative filter (absence of signal) |
Policy refinement; regulatory review; “safe enough to try” decisions; protecting minority from harm |
Decisions requiring a clear positive mandate — elections, irreversible choices |
|
Condorcet Pairwise |
Who would beat every other option head-to-head |
Median detection |
Finding the broadly acceptable middle in polarized populations |
Large candidate fields (computational and comprehension costs); can cycle with no winner |
|
Liquid Delegation |
Trust networks — who do you trust to decide for you on this topic |
Graph / network signal |
Ongoing governance where expertise matters and engagement varies; agency scoring at scale |
One-time high-stakes decisions where everyone should engage directly |
|
Needs-Tagging (Bucket Theory) |
What need is driving the preference — which bucket is being filled |
Categorical / semantic signal |
Upstream of all other methods — the sensing layer that makes solution-evaluation meaningful |
Not a voting method itself — must be combined with a solution-evaluation method downstream |
Section 4.1 — Elections. Score voting (0–10) for all single-winner elections: President, Governors, Senators, Representatives, Mayors. This is the domain where intensity information matters most, where the spoiler effect is most damaging, and where mandate measurement provides continuous accountability. Score voting eliminates two-party lock-in and allows honest preference expression. The Bucket Theory’s Needs Map informs voters about what needs each candidate’s platform addresses and in what contexts.
Section 4.2 — Legislative Process. Sociocratic consent for legislative refinement. Bills are iterated through the consent process: “Is this good enough for now, safe enough to try?” Objections must demonstrate harm to a defined governmental purpose. This protects minorities from majoritarian overreach—a critical trust-building feature. Before any bill reaches the consent process, a Needs Map must be published showing which buckets are at stake and how the bill addresses needs across different contexts.
Section 4.3 — Swiss Veto and Citizen Review. Score voting for citizen challenges to legislation. If 1% of registered voters petition within 100 days, the law goes to a national score vote (citizens may vote directly or through liquid delegates). Average score below 5.0 suspends the law. Needs-tagging is built into the petition and scoring process: citizens indicate which need is threatened by the law.
Section 4.4 — Ongoing Agency Performance. Score voting via Liquid Delegation. Citizens score agencies 0–10 quarterly, with topic-specific delegation to trusted proxies. Delegation is instantly revocable. Scores below 4.0 trigger graduated review per Ostrom’s graduated sanctions principle.
Section 4.5 — Citizens’ Assembly Deliberation. Sociocratic consent process with round format for internal deliberation. For recommending among multiple alternatives, Condorcet pairwise comparison (which finds the option that would beat every other in head-to-head comparison) is used as the selection method. This combination uses consent for “would this cause harm?” and Condorcet for “which option is most broadly acceptable?”
Section 4.6 — Tension Prioritization. Score voting for weighting which citizen-registered tensions are most urgent. Citizens score tensions 0–10 for importance. Liquid delegation applies. This ensures governance attention flows to the needs that matter most, as weighted by continuous citizen feedback.
Section 4.7 — Constitutional Amendment. Score voting with a high threshold. Amendments require average score above 6.5 nationally plus above 5.0 in at least 26 states (adapting Switzerland’s dual-majority requirement). Needs-tagging is mandatory in the amendment process: proponents must identify which needs the amendment addresses, and the Citizens’ Assembly must map how it affects different populations’ bucket-filling strategies.
Section 4.8 — Regulatory Sunset Review. Score voting on a 0–10 scale for effectiveness and necessity. Regulations scoring below 5.0 cannot be renewed without supermajority legislative vote plus Citizens’ Assembly endorsement. Before sunset review, the Needs Map must show what need the regulation fills and what alternative bucket-filling strategies exist if the regulation lapses. The Niche Principle (Section 3.4) applies: before eliminating a regulation, the system must understand what it fills and for whom.
|
The Control Theory Principle No single controller is optimal for all plant dynamics. A PID tuned for a slow thermal mass will ring and overshoot on a fast servo motor. Similarly, no single voting method is optimal for all governance decisions. Score voting excels where intensity information matters. Consent excels where harm-prevention matters. Condorcet excels where broad acceptability matters in polarized contexts. Liquid delegation excels where ongoing expertise-driven evaluation matters. The governance system’s job is to match the sensor to the signal—not to declare one sensor universally superior. And upstream of all sensors, the Bucket Theory provides the reference signal: what need is the system actually trying to address? |
This section synthesizes Holacracy’s nested circles, Sociocracy’s double-linking, and Ostrom’s polycentric governance into a distributed architecture that is simultaneously decentralized and coherent—and informed by the Needs Map.
Section 5.1 — The Subsidiarity Mandate. Authority defaults to the most local level of government capable of handling the issue. This is supported by Ostrom’s empirical finding that polycentric systems outperform centralized ones, and by the Bucket Theory: the same need is filled differently in different contexts, so solutions should be generated at the level closest to the context. A federal one-size-fits-all policy will inevitably misfit many local contexts.
Section 5.2 — Sociocratic Double-Linking. Each governance level has two structural connections to the level above. A Lead Link (appointed by the higher circle to carry broader priorities downward) and a Rep Link (elected by the lower circle to carry local knowledge and concerns upward). Both participate fully in decision-making at both levels. This prevents the information asymmetry that erodes trust and ensures that local needs-sensing information flows upward into broader policy decisions.
Section 5.3 — Domain Clarity. Every government entity publishes its domains—what it exclusively controls—on the Trust Dashboard. Overlapping domains are flagged and resolved through governance process. This satisfies Ostrom’s first design principle and Holacracy’s core structural rule.
Section 5.4 — Polycentric Experimentation. States and local circles are explicitly empowered to experiment with different solutions to the same need. The Needs Map tracks which approaches work in which contexts. Successful innovations spread through voluntary adoption, not top-down mandate. Failed experiments are valuable data—they reveal which solutions do not work in which contexts, further refining the system’s understanding of how different populations fill different buckets.
Section 6.1 — Tension-Driven Legislation. Any citizen can register a tension through the digital Trust Infrastructure. Tensions include a needs-tag indicating which bucket(s) are implicated. Tensions that gather sufficient score-weight are processed through a defined legislative track. Citizens may delegate their tension-scoring through the Liquid Delegation Layer.
Section 6.2 — The Swiss Veto. Any law passed by Congress can be challenged by citizens. 1% of registered voters signing a petition within 100 days triggers a national score vote, exercisable directly or through liquid delegates. Average score below 5.0 suspends the law and refers it to Citizens’ Assembly review.
Section 7.1 — Standing Citizens’ Assembly. 150 randomly-selected citizens serving staggered 18-month terms. This body conducts needs-mapping for complex policy areas, deliberates on constitutional amendments, reviews agencies triggered by low scores, and processes major tensions. The Assembly satisfies Ostrom’s third design principle: those affected by governance rules can participate in modifying them.
Section 7.2 — Deliberative Process. Following Ireland’s proven methodology enhanced with Sociocratic round format and the Bucket Theory: before deliberating solutions, the Assembly first maps the needs at stake and how different populations fill them. Expert testimony is organized around needs, not around solutions. Decisions use the consent process for harm-prevention and Condorcet pairwise comparison for selecting among alternatives.
Section 7.3 — Binding Recommendations. Constitutional amendment recommendations proceed directly to national score vote. Agency reform recommendations must be implemented within 12 months. Regulatory sunset reviews are binding. Congress may override with two-thirds supermajority plus public justification.
Section 8.1 — The National Trust Layer. Decentralized, blockchain-anchored data exchange connecting all government agencies (adapted from Estonia’s X-Road). Every data query is logged. Citizens can audit access in real time. This infrastructure supports the Trust Dashboard, Needs Map, Liquid Delegation, score voting, and tension registration.
Section 8.2 — Secure Digital Identity and Delegation. Universal digital identity system enabling participation in all democratic processes. The Liquid Delegation Layer operates through this system—citizens set and revoke delegation preferences, view delegation chains, and override proxy scores. Physical alternatives must always exist.
Section 8.3 — Open-Source Governance Code. All software used in democratic processes must be open-source and publicly auditable. No proprietary black boxes in democracy. If you cannot inspect it, you cannot trust it.
Section 9.1 — Separation of Money and Governance. All campaigns publicly funded. Private contributions prohibited. Lobbying contacts logged in real time with full transcripts on the Trust Dashboard.
Section 9.2 — Independent Integrity Commission. Members selected by Citizens’ Assembly lottery. Constitutionally protected funding. Authority to investigate any government entity.
Section 9.3 — Merit-Based Civil Service Protection. Hired and promoted on merit, never political loyalty. Civil servants swear to uphold the Constitution, not loyalty to any individual.
Section 10.1 — The Adaptive Amendment Process. Three initiation paths: (1) congressional; (2) Citizens’ Assembly recommendation to national score vote; (3) citizen initiative with 3% score-weighted support. All paths require a published Needs Map showing which buckets the amendment addresses. Amendments require average score above 6.5 nationally plus above 5.0 in 26+ states.
Section 10.2 — Immutable Core. Beyond amendment: the Bill of Rights, separation of powers, universal suffrage, the Needs-Sensing Layer, the matched voting toolkit, the Citizens’ Assembly, the Liquid Delegation Layer, and Ostrom’s Eight Design Principles.
Section 10.3 — Decennial Constitutional Review. Every ten years, a 300-member Citizens’ Assembly conducts comprehensive review. Which modules work? Which need updates? Has the needs taxonomy evolved? Do new governance dynamics require new voting methods in the toolkit? This institutionalizes Sociocracy’s principle that no decision is permanent.
The deepest failure of American governance is not that it uses the wrong voting method, or that it lacks transparency, or that it is too centralized. The deepest failure is that it asks citizens to fight about solutions without ever surfacing the needs those solutions are trying to fill.
A farmer and a nutritionist, forced to vote for or against agricultural subsidies, become political enemies. A system that first asks “What are you both trying to achieve?” discovers they share the same goal—food security—and differ only in context. The farmer fills the sustenance bucket with land. The nutritionist fills it with information. Both are right, for their terrain.
The Bucket Theory is not a utopian claim that all conflict can be dissolved. Some needs genuinely conflict—one group’s agency may threaten another group’s security. But even genuine conflicts become more tractable when the governance system correctly identifies what is actually at stake, rather than allowing the fight to escalate at the solution level where positions harden and compromise feels like betrayal.
This Adaptive Constitution therefore proposes three layers, not one: sense the need, generate context-appropriate solutions, then evaluate those solutions with the right tool. Upstream, the Bucket Theory and Needs Map identify what buckets are at stake and how different populations fill them. Midstream, Ostrom’s polycentric governance generates solutions matched to local contexts rather than imposing one-size-fits-all policy. Downstream, matched voting methods—each chosen for its signal-extraction properties in the specific governance dynamic at hand—evaluate those solutions with appropriate precision.
No other governance framework we are aware of builds this upstream needs-sensing layer. That is what makes this proposal fundamentally different from electoral reform alone. Electoral reform asks: “How do we better count preferences?” The Bucket Theory asks the prior question: “What are those preferences actually about?”
A System That Learns What People Need, Not Just What They Want
A neural network does not just optimize for the output signal. It learns the features of the input—the hidden structure that explains why the signal looks the way it does. The Bucket Theory is the governance equivalent of feature extraction. Before the system optimizes (votes on solutions), it must learn the features (identify the needs). Without this, governance is a model trained on noise: it fits the surface of political opinion without understanding the structure underneath. With it, governance becomes a system that learns what people need—not just what they say they want—and can generate solutions matched to the actual terrain of their lives.