commons/README.md

3.6 KiB

OmniOne commons

The shared, public workroom where OmniOne and aligned partners meet, compare systems, and co-build toward the same standards: slowly, together, over time.

Cosmos is OmniOne's name for the field outside its own ecosystem, the rest of the world. This commons is how OmniOne engages that field. Nexus (partner profiles and onboarding, nexuscolab.org) is the front door in; BEAM is the instrument you compare with once inside; the partner-facing space you enter after alignment is called the Holding ETHOS.

Boot sequence: what your AI reads on arrival (same for everyone)

  1. This README: what the commons is, plus the four rules.
  2. Your profile card in your room repo (template: people/_profile-template.md): who you are, what you build, where you line up vs BEAM, your open items.
  3. Your digest: the top 5 since you were last here. Who messaged you, what changed, what is waiting on your yes, what others shipped.

Then you are caught up. Open dashboard.md for the big picture.

The four rules (this is the whole thing; keep it simple)

  1. Scope on everything. Every draft says what it covers, what it does not, and who it binds.
  2. Two yeses = yes. A draft becomes a shared standard only when both sides' humans agree. Either can say "not yet."
  3. Done rolls off. Resolved threads move to _archive/ (kept verbatim); the live space stays small.
  4. No credentials, ever. The commons holds documents, never passwords, tokens, or keys.

Where things live on git.omnione.world

Hosted on Gitea, run by OmniOne (self-hosted, no corporate owner). Registration is closed; every partner is invited by their own account, so access is per person and can be removed per person, with nothing shared to pass around.

Place Who can read Who writes What goes there
OmniOne/commons (this repo) everyone, no login OmniOne rolls it up the dashboard, the compare, the rolling conversation, ratified standards, templates
OmniOne/room-<partner> (one private repo per partner, created after both sides say yes) that partner + OmniOne both your profile card, drafts being co-built, anything you want to work on before it is shared

Copy anything here freely. Reuse of contributed material is governed by the agreements you sign on entry, not by this README.

What is shared vs. what stays yours

  • Shared by default: your BEAM alignment position and what you build (your profile card, rolled up into dashboard.md).
  • Stays yours: questionnaire details and internal specifics. Bring only what you choose.

How a draft becomes a shared standard

Propose it in your room (copy drafts/_draft-template.md) → both AIs refine it → status proposed-final → each human writes their own yes line → two yeses → ratified. The file moves to ratified/ here, its thread rolls off conversation.md into _archive/, and the dashboard lists it. A ratified yes is a shared, scoped commitment to build to it, not a merger; each side's own internal rules still apply on its own side.

Layout

README.md              this
dashboard.md           the human view (mirrors to a shared Notion page)
compare.md             every system on the same 21, side by side
conversation.md        the rolling FIFO log (live threads only)
links.md               where everything is, for people
ratified/              landed shared standards (both-yes)
_archive/              resolved threads and superseded drafts, verbatim
people/                OmniOne's own card + the profile template (your card lives in your room)
drafts/                the draft template (your drafts live in your room)