Congressus · Collaboration

Congressus belongs to everyone it serves.

This paper is a pre-draft working document explicitly seeking collaboration across nine research domains. The architecture is complete enough to build on. What it needs is rigorous stress testing, formal specification, empirical grounding, and engagement with traditions that the current drafters cannot fully represent.

Get in touch

Read the white paper

Collaboration sought

Computational Social Choice

Formal specification of preference aggregation and negotiation protocols. Game-theoretic analysis of the three-representative consensus mechanism. Empirical response to Arrow’s Impossibility Theorem.

Constitutional & Political Theory

Legitimacy, representation, and democratic theory. Formalization of the Private Sphere Doctrine. Engagement with Rawlsian public reason and the Precision Principle’s relationship to constitutional interpretation.

AI Safety & Alignment

Review of the capture resistance architecture. Agent behavior specification. Validation of the capture detection agent design and the conditions under which the three-representative model is manipulation-resistant.

Digital Democracy Practice

Empirical grounding from vTaiwan, Decidim, and related projects. What has actually worked at scale? What failed? Where does the Congressus architecture diverge from field experience?

Moral Philosophy

Private sphere doctrine and harm theory. Kohlberg’s moral development extensions. The philosophical foundations account — does it hold? What does it miss? Track 1 upward revision proposals.

Non-Western Political Philosophy

Critical engagement with the Floor’s cultural assumptions. The framework claims to draw from the overlapping consensus of human moral traditions — that claim requires challenge from scholars who can identify what it misrepresents or excludes.

International Relations

Sovereignty, enforcement, and international law. Does the small nation coalition logic hold empirically? What are the actual incentive structures for early adoption versus holdout?

Software Engineering & AI Infrastructure

Prototype development and federated architecture implementation. The Phase 1 hardware spec is documented in Section 13. Build contributors are welcome at any level from the single-state demo upward.

How this collaboration works

1No contributor owns the framework. Congressus belongs to everyone it serves. Contributions are offered to the public record, not to any individual or institution.

2Engage with the actual text. The white paper is specific. Responses should be equally specific — cite the section, the claim, the mechanism you are engaging with.

3The merit-conditional dissent principle applies here too. If you identify a flaw, propose a remedy. Critique without construction is not a valid output.

4All collaboration is published. The public record includes critiques, revisions, and responses. The system is designed against its own institutionalisation — that starts here.

To contribute: Post to the Discussion, email collaborate@congressus.org, or submit a formal collaboration proposal with your institutional affiliation and the specific contribution you are proposing.