Skip to content
UOAUniversal Operating Agreement
DEVELOPMENT ROADMAP

Begin privately. Open carefully. Earn legitimacy through the work.

The timeline is intentionally staged. The UOA should not perform certainty or scale before its safeguards and participation model are ready.

NOWPrivate foundation

Define the constitutional minimum.

Genesis statement, working principles, refusal clauses, architecture, threat model, participation rights, privacy posture, and initial stewardship design.

FALL 2026Closed review

Invite structured challenge.

Small cross-disciplinary review groups examine assumptions, language, governance, accessibility, cultural bias, technical feasibility, and capture risks.

JAN 1, 2027Public opening

Release the first participation environment.

Publish the proposal, open the contribution process, expose the version history, and begin structured public deliberation.

2027+Evidence and federation

Test the agreement in real systems.

Launch compatible nodes, document case studies, evaluate consequences, develop open interoperability, and move stewardship toward legitimate multi-stakeholder governance.

What must be proven before scale

  • A participant can understand how their contribution will be used.
  • Consent, withdrawal, privacy, and pseudonymity work in practice.
  • Different models can interpret the same versioned agreement consistently.
  • Translation preserves meaning and makes cultural disagreement visible.
  • Powerful institutions cannot overwhelm affected communities.
  • Minority reports remain attached to decisions rather than disappearing.
  • Security failures, manipulation attempts, and governance conflicts have credible response paths.
  • Outcomes can change the agreement, rather than the agreement merely justifying the system.