Commons v0.2: scaffold content moved from the local Gitea (Cosmos, 2026-09-08)

This commit is contained in:
Josh Pasmore 2026-09-08 00:21:10 -05:00
parent 6b5d5cec43
commit d6b33b0f67
10 changed files with 186 additions and 1 deletions

View File

@ -1,2 +1,48 @@
# commons # 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)
```

3
_archive/README.md Normal file
View File

@ -0,0 +1,3 @@
# Archive
Resolved threads and superseded drafts, kept verbatim. Nothing here is deleted.

34
compare.md Normal file
View File

@ -0,0 +1,34 @@
# The compare: options on the table, side by side
> The shared view of **how each system answers the same questions**. Two layers sit here:
> 1. **Prompt self-maps (the primary compare).** Each entity's Step-1 output, how they build each piece, placed side by side and **attributed per entity** (colour-coded in the Notion dashboard and the app view; in the repo each entity's answers carry its name). It shows, across the line, the **different options people are using** and where we need to work to align.
> 2. **BEAM readings**: the structural score on the same 21. **The BEAM side-by-side lives in the app** (`/compare` in BEAM), so it is not duplicated here.
> ⚠️ **The Step-1 prompt is being rebuilt.** The self-map format below is a placeholder until the new prompt lands; that output is what fills the "options on the table" per entity.
## Prompt self-maps: options on the table
*One block per entity, attributed. Populated from each entity's Step-1 self-map once the redone prompt ships.*
| Entity | Their approach: the building blocks | Where it lines up / differs |
|---|---|---|
| **OmniOne** | *(self-map from the new prompt, pending)* | the baseline others compare against |
| _(partner)_ | _(their self-map, pasted in on entry, attributed)_ | _(across the line: align / borrow / gap)_ |
## BEAM readings
Two things sit side by side in the app, on purpose:
- **BEAM position**: how strongly the requirement is *evidenced* today (band + evidence tier). A = genuine source document · B = partial / authenticity uncertain.
- **Architecture maturity**: whether the *tool that actually backs* the requirement is built: **Live · Live (partial) · Designed · Candidate · Gap** (OmniOne's Architecture Register).
**Numbers are never restated here.** OmniOne's live reading, and every partner's, is in the BEAM app at `/compare`; a number copied into a file goes stale the day the instrument moves.
## OmniOne / N.E.O.S.: the honest read
**The agreements are strong; the architecture that enforces them is mostly still to build.** That gap is what this commons is for.
- **Where OmniOne would bring stronger evidence** (the requirements held at evidence tier B): **Pluralism (#14) · Interoperability (#16) · Commons stewardship (#17) · Onboarding and education (#18) · Structural review (#20).**
- **Where the build itself is thinnest** (architecture Gap or Candidate): Adaptive feedback (#9) · Security (#15) · Scoped, revocable authority (#3) · Roles and succession (#10) · Drift detection (#19). These are where co-building has the most to add.
## How your options land here
1. You run the **Step-1 prompt** → it produces your **self-map** (how you build each piece). That is a direct comparison we can look at.
2. If you enter the Holding ETHOS, your self-map is **pasted in, attributed to you**: one of the options on the table next to everyone else's.
3. Your **BEAM score** sits side by side **in the app** (`/compare`), not duplicated here.
4. Across the line, we see what to align on. Where you are stronger we borrow from you; where we are, you borrow from us. Both directions.

7
conversation.md Normal file
View File

@ -0,0 +1,7 @@
# Conversation: the rolling log
> **FIFO: live threads only.** Newest at top; one line per update where you can. When a thread resolves, move it to `_archive/` verbatim so this stays small. This is what keeps the commons from getting complicated.
---
*(No live threads yet. First entry lands when the first partner arrives.)*

31
dashboard.md Normal file
View File

@ -0,0 +1,31 @@
# Commons Dashboard: the human view
> The one page a human checks to see what is going on. Mirrors to a shared **Notion** page. **Written by OmniOne**, rolled up from everyone's own profile card. Keep every section short; add a chart only where a count actually helps.
> **Human links:** `links.md` (everywhere worth going) · `compare.md` (all systems on the same 21) · mirrors to Notion.
## Who's here
*One line each. OmniOne's card is `people/omnione.md`; partners' cards live in their rooms.*
| Who | What they build | Vs BEAM |
|---|---|---|
| **OmniOne** (`people/omnione.md`) | new-paradigm operating system | live reading in the BEAM app · the host and the worked example |
## Open decisions: waiting on a yes
*A draft lands here the moment it is `proposed-final`. Clear it when both yeses are in.*
| Draft | Scope | OmniOne yes | Partner yes |
|---|---|---|---|
| _(none yet)_ | | | |
## Ratified: landed shared standards
*Both-yes artifacts. Full files in `ratified/`.*
| Standard | Scope | Date |
|---|---|---|
| _(none yet)_ | | |
## Best practices: harvested
*What the sweep turned up that is worth everyone adopting.*
- _(none yet)_

13
drafts/_draft-template.md Normal file
View File

@ -0,0 +1,13 @@
# <Draft title>
**Scope:** <what it covers> · **NOT:** <what it excludes> · **Binds:** OmniOne | partner | both | app X
**Status:** proposed | in-discussion | rescope | proposed-final | ratified
**OmniOne yes:** <name + date | none yet> **Partner yes:** <name + date | none yet>
---
<the proposal, co-authored; sharpen the scope as you go>
---
> Copy this into your room repo's `drafts/`. **Two yeses → ratified.** The file then moves to `ratified/` in the commons, and its thread rolls off `conversation.md` into `_archive/`.
> A ratified yes is a **shared, scoped commitment to build to this**, not a merger. Anything touching OmniOne canon still goes through OmniOne's internal canon gate separately; the same for the partner's own rules.

24
links.md Normal file
View File

@ -0,0 +1,24 @@
# Links: where everything is (start here if you are a human)
> Files are for the AIs; this page is for people. Every place worth going, in one list.
## The live things
- **This commons** (public, no login) · https://git.omnione.world/OmniOne/commons
- **BEAM app** (take the comparison) · https://beam-readiness-gev.netlify.app
- **Walkthrough preview** (see the whole partner flow, no login) · https://beam-readiness-gev.netlify.app/preview
- **Notion dashboard** (the human roll-up of this commons) · https://app.notion.com/p/Cosmos-Commons-Dashboard-3b8d14367d5f81ed915ff2fa8528dbfb
## Inside this repo
- **README**: what the commons is, the four rules, and where things live (start there).
- **`dashboard.md`**: the at-a-glance human view (who is here · open decisions · what has landed).
- **`compare.md`**: every system on the same 21, side by side.
- **`conversation.md`**: the rolling log of what is being worked.
- **`ratified/`**: the shared standards both sides have said yes to.
- **`people/`**: OmniOne's card and the profile template. Your card lives in your own room repo.
- **`drafts/`**: the draft template. Your drafts live in your own room repo.
## The map behind the compare
- **The 21 requirements and why each matters**: the BEAM instrument (structural readiness).
- **The architecture behind each requirement**: OmniOne's Architecture Register (what is Live / Designed / Gap). *(Published as a shared dashboard; link added when it is up.)*
*(Anything not linkable yet is marked; those are the pieces still being stood up.)*

View File

@ -0,0 +1,11 @@
# <Name / Org>: profile card
> Your one-page card. Copy this file into your room repo as `people/<your-name>.md`. **You edit your card; OmniOne rolls the one-line summary up into the commons dashboard.**
- **What we build:**
- **Where we line up vs BEAM:** *(your alignment position, the one thing shared by default)*
- **Open items, waiting on us:**
- **Open items, waiting on someone else:**
- **Contact / our AI's entry point:**
*(Questionnaire details and internal specifics stay yours. Share only what you choose.)*

13
people/omnione.md Normal file
View File

@ -0,0 +1,13 @@
# OmniOne: profile card
> OmniOne's own page. The host of this commons; also the first worked example of how a profile + BEAM position reads here.
- **What we build:** a new-paradigm community operating system: how organizations govern, decide, and share value so no single interest can own or capture it. A family of apps built to one standard (Module Standard) sharing one identity layer, one decision method (ACT), one rules layer (canon/agreements), one look. A project of the nonprofit Green Earth Vision.
- **Where we line up vs BEAM:** the *New Earth Operating System (N.E.O.S.)* self-assessment, run from OmniOne's own governance documents (not an outside audit). **The live reading is in the BEAM app**, never copied here. Per-criterion read → `compare.md`.
- **Where we'd bring stronger evidence (held at evidence tier B):** Pluralism (#14) · Interoperability (#16) · Commons stewardship (#17) · Onboarding (#18) · Structural review (#20).
- **Open items, waiting on us:** publish the architecture register as a shared dashboard · run the Step-1 self-map (below).
- **Open items, waiting on someone else:** none.
- **Step-1 self-map:** *(the prompt output, to be dropped in once run; slot held so the profile reads the same as a partner's will.)*
- **Contact / our AI's entry point:** the BEAM app, https://beam-readiness-gev.netlify.app · walkthrough preview `/preview`.
*(Questionnaire details and internal specifics stay ours, shared only by choice. What is shared by default: this BEAM position and what we build.)*

3
ratified/README.md Normal file
View File

@ -0,0 +1,3 @@
# Ratified
Landed shared standards: one file each, both yes lines filled. Empty until the first one lands.