Help make the next version harder to fool

Explore the public summaries and Primer without an account. Sign in to search Hub work and read discussions available to registered accounts. Be specific about the claim, evidence or explanation you want to improve.

Contributing requires an invitation, acceptance of the current Swiss pilot information, and your own adult and Swiss-residence declarations. Admitted participants can reply, start linked discussions and create working documents. If you participated before but access has paused, review your participation status for updated notices. Neither Primer completion nor formal Verein membership is required.

On a chapter, choose Discuss this chapter to find related conversations, or Suggest a change to describe a proposed improvement in a new linked discussion. It does not directly edit the chapter or apply a patch. Working documents keep their discussions and revision history in the same Hub.

Read what others have already contributed, reply where your point belongs, or start a discussion with a clear question and the relevant source. A promising exchange can become a working document without losing its conversation. Your private website Updates help you return to replies and watched activity.

Optional chat can help people coordinate, but shared arguments and working documents belong here. Use the contact route for help or abuse reports. Agreement, enthusiasm or participation frequency should not stand in for the quality of an argument.

A connected personal AI can search sources, compare an argument with its evidence and help you prepare a contribution. On staging, shared reading and ordinary contributions through MCP are active. Use the same Hub account and explicitly authorize the additional access when connecting or reconnecting your client.

Shared reading reaches only material you can currently read. Write consent lets your client carry out ordinary actions you are permitted to perform, such as posting a reply or revising your own contribution. An older public-only connection stays public-only until you authorize more access. Review what your AI proposes before asking it to submit.

Consent does not grant pilot admission, stewardship or public publication. Editing another person’s shared document requires the relevant permission on both interfaces. Private account details, drafts, Updates, watches, reports and legal declarations stay outside MCP.

Your private AI conversation is not imported automatically. When you deliberately submit a contribution, it joins shared work with its attribution and history. Your AI’s private explanation does not alter the common source.

Pilot admission permits ordinary contributions. Revising a shared document or curating a collection requires the relevant explicit grant. Public release requires exact-revision approval; institutional adoption requires its own real decision. None of these follows from signing up, and pilot admission is not formal Verein membership.

The intention is to preserve revisions and reasoning rather than silently edit the record of a disagreement. A contribution can improve the project by overturning a central conclusion. Neither the founder’s view nor a religious interpretation should determine who is allowed to raise a valid objection.

If you find a software problem, describe what you tried, what happened and what you expected. A small reproducible example is especially useful. Do not include passwords, tokens or someone else’s private material in a shared report; use Contact for sensitive issues.

The source code is not yet publicly released. Its separate audit and release are still needed before an open contribution route can be offered. Meanwhile, testing the actual website and AI workflows can identify the changes that matter.