A practical guide to contributing
Use your own AI
Read Omegaism, think something through with your own AI, and contribute when you have something to share. There is no official central AI you must use or agree with. Availability on this deployment is shown separately below.
Omegaism
The text you are reading
A passage you want to understand or question.
Your reading stays here.
Your AI sidebar
Explore the question privately. Choose what to share afterwards.
What you can do here
Use a compatible connected AI to search and read approved public sources, compare arguments and draft a question or correction. The availability box shows whether this deployment offers the connection. A shared or trained Omegaism AI is a separate long-term proposal.
Shared reading and ordinary collaboration through MCP are enabled on staging for explicitly authorized clients. Your connection can read the shared material your human account can currently read and perform ordinary contributions within your current permissions. Existing public-only grants remain public-only until you explicitly authorize the additional scopes.
Keep reading, with your AI beside you
On a supported desktop browser, your AI provider's side panel can sit beside the page you are reading. Your document stays open while you ask questions, check an argument or prepare a contribution.
The browser panel and the Omegaism connection do different jobs. The panel keeps your conversation nearby. An authorized MCP connection lets a compatible client search and read Omegaism’s released public material. Additional shared-content consent lets it read the shared material your account can currently read. Installing a browser extension does not automatically connect it to Omegaism: check that your chosen panel can use your authorized MCP connection.
From a question to a contribution
1. Start with something you care about
Read the Reality Primer, follow the guide to current work, or sign in on the website to explore discussions. Notice a claim, question or missing perspective worth investigating. You do not need to read everything first.
What is this passage claiming, and what would count as evidence against it?
2. Bring the passage into your conversation
Open your provider's browser panel using its toolbar or supported selection menu. For globally public material, select the relevant text when supported or use Explore with your AI to review and copy a Resource reference. With explicit shared-content consent, authorized clients may retrieve shared contributions within your current audience permissions. Private Updates, watches, drafts, account details, reports and legal declarations remain outside MCP. Check that your AI has the intended context. Omegaism stays open beside it.
Help me investigate this passage. Keep our discussion private for now; do not post anything.
3. Find where the question already belongs
Ask your connected AI to search approved public Omegaism sources and inspect likely matches. With explicit shared-content consent, it can also search the registered-account discussions you can read and, while you are admitted, the participant Commons. No separate approval from each Post’s author is required.
For a long document, ask it to inspect the outline and any Resource Map, plan which parts of the argument need evidence, and search within the source. Read the exact sections, including qualifications and objections. A map is a shared interpretation that you can challenge; its omissions never make source passages unsearchable.
What do the released texts say about childcare staffing or liability? Show me the relevant passages, including qualifications and objections.
4. Review a contribution, then deliberately share it
On a Primer chapter, Discuss this chapter shows linked conversations. Suggest a change opens a new native discussion with the chapter selected; supply the wording you propose and your reason. It does not edit the source text or apply a patch. Working documents also link to their discussions. No external editor or forum account is needed.
Draft privately first using only material you may share with your AI. Review the wording and audience before replying or creating a distinct linked discussion on the website. A client with shared-read and write consent can perform the same ordinary actions you are authorized to perform. Contributions require current accepted Swiss-pilot admission and appear under your Omegaism identity; signup alone does not allow posting.
Draft a short objection to this public passage. I will review it and decide whether to submit it on the website.
5. Develop the work and return to it
A discussion can lead to a working document without losing its existing conversation. Authorized MCP clients can create documents, revise your own Posts, apply permitted document edits, and read revision history and exact source passages. Watching discussions and checking private Updates stay on the website. New work defaults to the participant Commons; it is not automatically public. Creating a personal document records a scoped, revocable editing grant for that document. Shared manuscripts require explicit stewardship. Authorized people can also create and revise Resource Maps with exact source evidence; a source change marks an older map as needing review. Passage-linked discussions and document revision comparison are implemented; an in-reader suggestion-and-acceptance workflow remains planned.
Help me organize this public-source analysis into a draft. Do not submit it; I will choose its audience and create the working document on the website.
Set up your own AI
Sign in to Omegaism first, then authorize the same account in your AI client using the endpoint shown in the availability box above. Use an existing working connection. After a staging login-service migration, an old connection may need fresh authorization.
- ChatGPT: in Plugins, choose Add custom MCP server, enter the endpoint and select OAuth, then Create as a plugin. Install it from your personal plugins and enable it in a Work conversation. Follow the official quickstart for the controls available to your account. Use its published OAuth identity when offered; no website client credentials are needed.
- Claude: open Customize → Connectors → Add → Add custom connector, enter the endpoint, and review the detected authentication settings. Choose sign-in and Use Claude’s published identity; leave manual client credentials empty. Each person signs in with their own Omegaism account and approves access. Follow Claude’s connector guide; organization settings may require an administrator.
- Other compatible clients: add the remote MCP endpoint and complete the client’s OAuth flow. Codex’s MCP guide describes its supported setup.
First ask for a public Resource read and open the returned browser link. For shared reads and contributions, reconnect and approve all three scopes: resources:read, resources:read:shared and collaboration:write. Staging requests them at sign-in because some clients do not complete incremental consent. Your website notice acceptance and client OAuth consent are separate; neither grants admission or stewardship. A connection guide is not evidence that a particular client’s consent or renewal flow has been verified. Browser side panels remain optional; no extension or plugin packaging project is needed just to read and discuss here.
If an old ChatGPT tab reports “Missing OAuth callback data,” return to the connection’s current Connect action and start a fresh authorization attempt. Do not reuse an old callback URL. This is a recovery step, not a fix for repeated disconnections; report the time and client so the operator can compare provider logs without collecting tokens or private conversation text.
What your connection permits
resources:read continues to permit only explicitly released public material. Existing grants are not expanded. resources:read:shared, in addition to resources:read, permits the registered and participant shared Resources your human account is currently allowed to read. A registered account without pilot admission can read registered material, but cannot read the participant Commons or contribute. Your private account information, Updates, watches, drafts, reports and legal declarations are never exposed through this connection.
collaboration:write separately permits ordinary shared changes alongside both read scopes. Contributions through either interface require a current accepted Swiss-pilot invitation and the human’s adult/residence declarations. An account or an OAuth grant alone is insufficient. Formal membership and ideological agreement are not required. Shared-document revision additionally requires current document.revise authority; Resource Map creation and revision require the corresponding grant. These responsibilities can be revoked and do not confer administration, moderation, membership management or publication authority.
To request shared-read consent, ask your client to call a read tool with includeShared: true. A missing grant returns an authorization challenge before looking up any Resource. Native resource operations can request the same upgrade with _meta["omegaism/includeShared"]: true. A write attempt without all three scopes requests the missing authorization before processing its arguments. Declining extra consent leaves public reads available. Staging also requests shared-read and write consent in the initial connection flow for clients that cannot complete incremental consent. A displayed tool is never proof of current admission, stewardship or release approval.
Private exploration, deliberate sharing
Connecting an AI does not upload your chat history. Omegaism receives explicit queries, reads and submitted tool arguments. Your AI provider's own privacy controls govern what its browser panel can see.
Contributions stay within their selected audience and remain working material. Public website release and institutional adoption require separate decisions. The shared-access disclosure explains that registered users or admitted participants may use external AI services to process contributions they are authorized to read. This does not make Commons material accessible to everyone on the internet. Provider privacy and retention practices apply, and Omegaism cannot recall independent copies. Do not contribute sensitive information you do not want the selected audience or their chosen AI services to receive. Shared AI access is enabled on staging under the accepted shared-ai-2026-11-07 notices. Production activation is a separate decision.