Proposed process

Citizens, analysis, and accountable authority

How a public question would move through NousPolis

The proposal separates public input, research, recommendations, and decisions so each can be examined on its own terms. It is designed to preserve uncertainty, disagreement, and responsibility rather than hide them inside one answer.

This is a proposed process defined by Architecture v0.1. NousPolis is not currently a deployed policy workspace and does not make public decisions.

Proposed process

The detailed public flow

Seven stages keep the path open to inspection.

Each stage would create records for later challenge. The stages organize inquiry; they do not turn analysis into democratic consent or legal authority.

  1. Raise and register the question

    A question could begin with citizen submissions, testimony, an institutional request, new evidence, an implementation failure, an appeal, an emergency, or research. Its source and requested action would be recorded.

  2. Define the problem and affected people

    Participants would document competing framings, the relevant jurisdiction, affected stakeholders, protected rights, local context, and a no-action alternative.

  3. Gather and verify evidence

    A citation begins as a lead, not proof. Reviewers would retrieve sources, connect claims to evidence, assess quality and context, and track evidence lineage.

  4. Compare and challenge options

    Distinct AI systems and human reviewers could independently analyze evidence, construct alternatives, question assumptions, request targeted research, and test failure scenarios. Multiple model instances are not democratic voters.

  5. Publish separate outputs

    An evidence assessment, values-and-trade-offs map, AI-assisted recommendation, dissent, and human-authorized decision would remain separate records.

  6. Human authorization and implementation

    The legally responsible institution could accept, reject, or modify the recommendation. Start proportionately. Where lawful and appropriate, begin with advice, simulation, or a bounded pilot.

  7. Measure, challenge, and revise

    Important forecasts and success criteria would be registered before results are known. Outcomes, complaints, appeals, and new evidence could trigger review without automatically changing policy.

What travels through the system

Different records need different protections.

Citizen testimony, public evidence, analytical records, human authority records, and outcomes carry different duties. Provenance should make later conclusions traceable without exposing protected material.

Information types and main protections
Information typeExamplesMain protections
Citizen inputIssues, testimony, priorities, objections, appealsConsent, privacy, representation limits, anti-capture checks
EvidenceResearch, law, administrative data, forecastsVerification, lineage, uncertainty, freshness
Analytical recordsFramings, options, assumptions, dissent, recommendationsReproducibility, provenance, procedural audit
Authority recordsAuthorization, rejection, modification, rationaleLegal authority and accountability
OutcomesImplementation effects, complaints, new evidencePredeclared metrics, appeal, review, version history

Illustrative example

Urban planning

Should a city allow taller housing around railway stations?

This fictional case uses no real jurisdiction, resident data, measured NousPolis results, precise probabilities, or actual policy recommendation.

Inputs and competing definitions

Residents, businesses, service providers, and underrepresented groups could contribute testimony alongside planning, legal, and infrastructure constraints. Competing framings might emphasize housing supply, displacement, accessibility, land value, regional transport, or neighborhood continuity.

Evidence and alternatives

Reviewers could examine rents, vacancies, construction, transit use, accessibility, infrastructure capacity, emissions, displacement, and transfer limits on evidence from other cities. Alternatives would include no change as well as phased or combined approaches.

Separate outputs and city authority

Evidence, trade-offs, recommendations, minority reports, and the human city decision would remain distinct so disagreement is visible and analytical output is never mistaken for authorization.

Learning without automatic policy

Predeclared measures could cover housing delivery, rent burden, displacement, accessibility, infrastructure load, travel behavior, emissions, and unequal effects. Crossing a condition starts review; it does not automatically change policy.

Illustrative example

Climate policy

How can a region reduce emissions without increasing energy hardship or weakening reliability?

A jurisdiction-neutral case would examine household burdens, worker and industry transition, rural and urban differences, public health, utility constraints, infrastructure, fiscal capacity, and law.

Framings and scenarios

Competing framings could emphasize emissions, affordability, energy security, health, employment, adaptation, rights, or intergenerational responsibility. Analysts would test central, adverse, tail-risk, and implementation-delay scenarios without inventing precise probabilities under deep uncertainty.

Alternatives and authority

Policy portfolios could combine pricing, retrofits, clean generation, grid investment, transit, industrial policy, or resilience spending. Evidence assessment, values and trade-offs, AI-assisted recommendation, and human-authorized decision remain separate.

Proportionate action and learning

Some reversible interventions might support a bounded pilot. Irreversible or population-scale action would need stronger scrutiny and explicit human and legal authorization.

Proposed process comparison

Different governance questions

Futarchy and Liquid Democracy address different parts of governance.

NousPolis is primarily a process for researching, challenging, authorizing, and revising public policy. Prediction markets may inform forecasts but do not govern. Architecture v0.1 does not define proxy delegation or a citizen voting system, and model-role separation is not institutional independence.

AI agents are not citizen representatives or democratic voters. The architecture requires neither blockchain nor token voting because neither technology by itself supplies legitimate participation, independent oversight, or public authority.

Robin Hanson's Futarchy proposal is a primary Futarchy reference. Chiara Valsangiacomo's scholarly definition discusses Liquid Democracy, while The Principles of LiquidFeedback describes one implementation.

Today

Limits and unresolved questions

What NousPolis has not solved yet

There is no deployed public-policy workspace and no public-policy authority. N1 remains blocked until every mandatory safeguard passes. Rules for citizen standing, identity, representation, voting, delegation, and ratification remain constitutionally unresolved. Participation infrastructure still needs anti-bot and anti-capture protections, privacy, moderation, accessibility, and due process. The full process has not proved its cost, speed, scalability, or real-world performance.

Today

Evidence and next steps

Inspect the proposal and its constraints.

Read Architecture v0.1, the N1 enforcement requirements, the dated N1 evidence snapshot, the independence rules, and the adversarial review disposition.