From a shared account to a dependable commitment

Imagine a neighbourhood trying to provide a regular meal service. Knowing who needs meals is only the beginning. Someone must check dietary requirements, obtain a suitable kitchen, arrange supplies and find people competent and available to cook. Preferences help shape a service; they do not settle every conflict over its limited capacity.

The Society organizes this problem around needs, capabilities, availability, preferences and knowledge. These are prompts for inquiry, not a solved allocation algorithm. A list of willing volunteers can expose a gap, but it cannot decide whether a service is safe or who carries responsibility when it fails.

“I can cook” and “I will prepare twenty meals next Tuesday” are different statements. The second needs a scope, an agreed standard, access to equipment and a plan for illness or cancellation. Other people can then rely on it—or see early enough that they cannot.

Changing a commitment should be possible without silently transferring its cost. If the cook withdraws, someone must arrange cover, reduce the service or notify the people depending on it. Better coordination makes that handover explicit. It does not turn a person’s availability into an obligation or a volunteer into a qualified professional.

Two groups could compare ways of booking shared equipment. They cannot safely run incompatible maintenance rules on the same machine. Useful experimentation needs a boundary: what can vary, who consents, which standards apply and who can stop the activity.

Members might decide which service to fund while a qualified specialist decides whether equipment is safe to use. Neither decision grants unlimited authority over the other. Budgets, technical reasons, complaints and responsibility for harm need identifiable owners. The wider Society mechanisms for doing this remain proposals.

Today the Hub helps people build a shared account of a problem. Read the public texts and Primer, search material available to your account, open a discussion, link evidence, or develop a working document with its conversation and revision history. Invited Swiss participants can contribute; editing someone else’s shared document requires the relevant stewardship. Collections and Maps help organize sources and arguments.

The same shared work is available through authorized personal AI connections on staging. Separate consent permits shared reading and ordinary contributions within the human’s existing permissions. Private account details, drafts, watches and Updates stay on the website. The Hub does not yet schedule services, allocate livelihoods or enforce the commitments imagined above.

The website and MCP use the same underlying access checks and actions. An AI can help compare evidence or prepare a revision; it gains no extra authority by being an AI. Readers should be able to inspect the source and history behind its answer.

A working document can change without rewriting its history. A public release is a separately approved snapshot: revising shared work does not automatically put it on the internet. This lets investigation continue while preserving what was actually released.

The longer-term Omegaism-as-AI proposal asks what shared learning might become. It is distinct from connecting your own AI today. Further software should follow demonstrated coordination needs; a diagram of a Society is not evidence that its institutions work.