About // 03

HOW TO
EVALUATE THIS

What the project claims — and what it does not

A project proposing to redesign economic coordination deserves skeptical, rigorous scrutiny. This page exists to support that scrutiny — to be clear about what Integral claims, what it does not claim, where its known gaps are, and how serious engagement with the project works.

What Integral Claims
CLAIMS Market economies structurally produce ecological destruction, inequality, and the erosion of genuine democracy — as predictable outputs of their coordination logic, not as aberrations.

This is a structural systems argument, not a moral one. The evidence for it is the empirical record of market economies operating across different political contexts, regulatory environments, and cultural conditions — consistently producing the same classes of outcome.

CLAIMS Non-market economic coordination is institutionally feasible — demonstrated empirically by commons governance research and cooperative economic practice.

Ostrom's Nobel-winning research documents this for resource commons. The cooperative economic tradition documents it for production and distribution. Integral draws on both bodies of evidence.

CLAIMS The five-system architecture described in the white paper is internally coherent and architecturally capable of supporting the coordination functions it claims to support.

This is a claim about design logic, not empirical performance. It is subject to critique on architectural grounds — and the white paper's GitHub repository invites exactly that critique.

CLAIMS The minimal first-node implementation described in the development guide is buildable by a volunteer contributor community with the skills and resources required.

This will be validated or refuted by Phase 1 development. The development guide exists to make this claim testable — by specifying exactly what needs to be built and to what standard.

What Integral Does Not Claim
DOES NOT CLAIM That Integral will work at scale before it has been demonstrated to work at small scale.

The project is at Phase 1. The proof of concept has not yet been built. Claims about large-scale performance are architectural projections, not empirical findings. They should be evaluated as such.

DOES NOT CLAIM That the transition to Integral is inevitable, imminent, or guaranteed to succeed.

Integral is one serious attempt at a hard problem. It may fail. The project's integrity requires acknowledging this honestly rather than projecting false confidence.

DOES NOT CLAIM That all problems of human coordination are solved by this architecture.

The system addresses economic coordination — production, distribution, contribution accounting, ecological feedback, and governance of shared resources. It does not address every dimension of human social organization.

DOES NOT CLAIM That participation in Integral requires ideological commitment or political alignment.

The system is designed to work for communities with diverse values, as long as they commit to the foundational principles of transparency, democratic governance, and ecological accountability. It meets people where they are.

Known Gaps and Open Problems

The white paper's postscript enumerates the project's own known weaknesses. This is not a sign of incompleteness — it is a sign of intellectual honesty. The following are the most significant open problems as of the current version.

OPEN PROBLEM // 01
THE ECOLOGICAL DATA CHALLENGE
Comprehensive, standardized, interoperable lifecycle assessment data does not yet exist at the granularity required for full ecological accounting. OAD's ecological assessment begins with simple human-completed checklists — a deliberate acknowledgment of this limitation. Building the data infrastructure for genuine ecological accounting is likely the largest single long-term challenge the project faces.
OPEN PROBLEM // 02
SCARCITY ARBITRATION AT FEDERATION SCALE
When multiple nodes in a federation need more of a scarce resource than is available, the CDS deliberation process is the answer — but coordination complexity at federation scale is underspecified in the current white paper. This requires more worked examples and more engagement with the computational and institutional literature on multi-party resource allocation.
OPEN PROBLEM // 03
IDENTITY AND AUTHENTICATION
Multiple systems depend on authenticated identity — CDS participation, ITC labor attestation, COS worker tracking — but the specification for how identity is managed across a federation in a way that is simultaneously Sybil-resistant, privacy-preserving, and non-coercive remains underspecified. This is a foundational infrastructure problem with no obvious off-the-shelf solution.
OPEN PROBLEM // 04
COLLECTIVE ACTION AT SCALE
The ITC's decay mechanism and access requirements address free-rider problems structurally, but behavioral economics suggests collective action problems in voluntary systems are harder than the current specification acknowledges. More engagement with the empirical literature on what actually sustains voluntary cooperative institutions over time is needed.
OPEN PROBLEM // 05
LEGAL AND REGULATORY INTERFACE
Early nodes will operate within existing legal frameworks — tax law, employment law, property law — that were not designed for this type of organization. ITC-compensated labor may be treated as employment by tax authorities. The transition framework assumes more operational freedom than early nodes are likely to have. This requires careful legal design that the current specification does not yet provide.
What Validation Looks Like
Phase 1 validates
PROOF OF CONCEPT

A real community using all five systems in a working feedback loop — producing real goods, recognizing real contributions, making real governance decisions, and generating real feedback. This is the minimum claim that Phase 1 either proves or refutes.

Phase 2 validates
SCALABILITY WITHIN A NODE

Whether the architecture can handle growing complexity — more participants, more production diversity, more governance load — without requiring redesign. Phase 2 expansion either confirms the architectural choices or reveals their limits.

Phase 3 validates
FEDERATION WITHOUT CENTRALIZATION

Whether independent nodes can share resources, designs, and intelligence without requiring a central authority. This is the most architecturally ambitious claim and the one most dependent on Phase 1 and 2 being genuinely solid.

Long term validates
ECOLOGICAL PERFORMANCE

Whether the system actually produces lower ecological impact over time as the feedback loop matures and ecological accounting deepens. This is the claim that matters most and the one that takes the longest to test against reality.

How to Engage Critically
CRITIQUE THE ARCHITECTURE
The white paper's GitHub repository has a structured critique issue template. A well-argued critique identifying a logical flaw, an underspecified edge case, or a contradiction between stated principles and proposed mechanisms is one of the most valuable contributions the project can receive. Critique issues are reviewed and responded to by the relevant working group.
Open a critique issue on GitHub
BRING DOMAIN EXPERTISE
If you have serious expertise in cooperative economics, ecological assessment, commons governance, distributed systems, participatory governance, or any other relevant field — the project needs you to apply that expertise critically. Not to validate the architecture but to stress-test it against what you know actually works and fails in practice.
See how domain experts contribute
WATCH THE BUILD
The most rigorous evaluation of Integral's claims will come from watching Phase 1 development unfold in public. The GitHub repository is the record of every decision made, every problem encountered, and every assumption tested against reality. Following that record as it develops is the most direct way to evaluate whether the project is doing what it says it is doing.
Follow development on GitHub
integrity.check // project.status
$ project.status --honest
phase: 1 // foundations
proof_of_concept: NOT YET BUILT
architecture: SPECIFIED // open to critique
known_gaps: 5 DOCUMENTED // more likely exist
intellectual_foundations: DOCUMENTED // see foundations page
critique_process: OPEN // github issue templates

// Confidence comes from transparency, not from claims.
Open a critique issue Read the white paper Questions & answers