Concept dreambook · not a live service · no membership or governance actions
New doors / field edition 001

Four unbuilt thresholds · 12 November 2026

Four new doors.
Two worlds.
One open invitation.

A concept dreambook for a more legible public circle, a more human assembly table, and a village guide that feels like a front porch.

3 OSO names · one family1 village window0 live services implied
Four illustrated doors opening onto a circle and a mountain village An open book holds an orchestra circle on one page and abstract mountain contours on the other. Four doors above it represent the four conceptual domains. 01 / PUBLIC02 / ALIAS03 / TABLE04 / VILLAGE AN ATLAS OF POSSIBILITIES
Drawing 00 · doors before wallsOriginal vector · CC0
osodao.org / circleosodao.com / aliasosodao.app / tablezuchiangmai.app / porch

Overview · the domain-role map

A small constellation,
not four websites.

The three OSO names should speak with one voice. The village name belongs to a different landscape. Each door earns its place by doing one clear thing.

Family A · Open Source Orchestraone identity / three distinct jobs
02 / THE SHORT WAY IN

osodao.com

A simple alias to osodao.org. No second brand, no competing home, no separate story.

Redirect only, if built
01 / THE PUBLIC CIRCLE

osodao.org

The flagship front door: principles, people-centered participation, public notes, and an invitation to listen.

Canonical home
03 / THE SHARED TABLE

osodao.app

A future hands-on assembly where listening becomes a draft and a draft becomes a shared, legible decision.

Later, not first

zuchiangmai.app

A village field guide and front porch: places, books, builds, gatherings, people—and gentle ways to take part.

Family B · a local window

One invitation, not one mold. The OSO family is about shared stewardship. The Chiang Mai guide is about finding your place in a living local landscape.

Mockup 01 · osodao.org · the public circleConcept — not live

OSODAO.ORG: No throne. Just a circle.

osodao.org / concept studynot a live service

Open Source Orchestra · a public circle

No throne.
Just a circle.

An orchestra score meets a round table. Every contribution has a place. Every consenting human has one voice. The center is not a ruler—it is the work we share.

Read the ground rules ↘Why no wallet? ↓
An equal circular seating scoreTen equal seats labeled music, code, care, translation, stewardship, documentation, access, welcome, craft, and learning surround an open musical score. There is no head seat. MUSICCODECARETRANSLATIONSTEWARDSHIPDOCUMENTATIONACCESSWELCOMECRAFTLEARNING THE OPEN SCORENO HEAD OF THE TABLE

01 / VOICE

One consenting human.
One voice.

Participation is chosen, not presumed. Code and care, music and translation: each contribution matters.

02 / RECORD

A community ledger.
Currently not on-chain.

Public notes can be accountable without pretending that a blockchain or token has already been chosen.

03 / COMMONS

Shared equally
by default.

Funding asks are for the whole circle. There is no token weight, rank, or special seat at the table.

04 / CONSENT

No wallet ask.
No hidden enrollment.

The first invitation is to read and listen. Any future step needs clear consent and a human explanation.

osodao.com → osodao.org

One front door. The .com is an alias, never a separate brand.

Why the score?

A score holds difference without flattening it. A circle makes the same promise spatially: every seat can see every other seat, and the center belongs to the shared work.

A separate room stays separate.

The existing osodaomeet hall remains its own immersive room. This public-circle concept does not overwrite it, absorb it, or turn it into a membership funnel.

Mockup 02 · osodao.app · a future assembly tableConcept — not live

OSODAO.APP: The Assembly

osodao.app / tabletop studyno functioning governance
Design fiction · no real voting · a working surface for many hands

The Assembly.

Proposals become shared decisions only after people have room to listen, shape, and understand one another.

1

Listen

A question enters the room. Context, lived experience, and uncertainty are welcome before a solution.

Public notes
begin with attention
2

Shape

People annotate the same draft. Trade-offs become visible. A blue pencil is as useful as a big idea.

Shared draft
revise in the open
3

Decide together

A consent-based outcome is written in plain language, with its reasons and its next small step.

Shared record
people, not balances
01 / ReadablePublic notes
02 / AccountablePublic decisions
03 / LegiblePublic spending

This is a paper interface, not a promise of software. No real proposals, member identities, ballots, balances, or governance actions appear here. The future tool would begin with consent and comprehension—not a transaction.

Mockup 03 · zuchiangmai.app · the front porchConcept — not live

ZUCHIANGMAI.APP: A city you can come home to.

zuchiangmai.app / field-note studynot an official community service
Abstract lantern-lit mountain village at duskOriginal geometric mountain contours, simple village roofs, a notebook-like path, and warm lanterns. The landscape is an abstract illustration, not a claim of authentic cultural motifs.

A village field guide · a community notebook

A city you can
come home to.

Not a directory of everything. A generous first page: where to begin, what to read, how to join in, and how to leave a place better.

Abstract contours · not a cultural motif
PlacesBooksBuildsGatheringsPeople

Begin with an intention.

Four gentle prompts. No feed, no status performance.

Make something

Bring a half-formed idea. Find a table, a tool, or another curious pair of hands.

Read together

Leave a margin note. Share a book. Let a good question travel further than a hot take.

Share a meal

Make room for one more bowl. Hospitality is a way of drawing the map.

Offer a hand

Small help is a kind of infrastructure. Start with what you can genuinely offer.

Scope & evidence · what is actually known

The names are real.
The rooms are not.

These are observations from the owned infrastructure inventory, not claims about adoption, deployment, or community approval.

DomainConcept roleZone activated
zuchiangmai.app Village field guide / front porch
16:59:44 UTC
osodao.org Flagship public circle
17:25:19 UTC
osodao.com Simple alias to osodao.org
17:25:20 UTC
osodao.app Future hands-on assembly table
17:25:19 UTC

Cloudflare

All 4 zones were created and activated on 12 November 2026. Owned metadata lists Cloudflare nameservers darwin and jocelyn.

DNS & web

The owned DNS inventory showed no A, AAAA, CNAME, MX, or TXT records. Apex and www names did not resolve when checked.

Source

No source repositories for these names appeared in the owned GitHub inventory. This page introduces concepts, not recovered product plans.

Concept study only. Do not type these domains into a browser expecting a service.

Nothing here says a site is deployed, a community has approved a direction, or a domain is ready to visit. The mockups and controls are explanations, not enrollment.

Suggested build order · slow is smooth

Draw the circle
before the table.

The smallest trustworthy sequence starts with meaning, not machinery. Each stage can stop without leaving a hollow product behind.

  1. Bless the boundaries.

    Confirm the circle’s principles, the alias-only role of osodao.com, and the separate identity of the existing meet hall.

  2. Make the public circle legible.

    Start with osodao.org: plain-language principles, accessible notes, consent, and truthful status. No membership theater.

  3. Add the alias; prototype the table later.

    Point osodao.com to the canonical home only after it exists. Test osodao.app as a consent-first design prototype before any real decisions.

  4. Localize the porch with local stewards.

    Shape zuchiangmai.app with the people and tools already present. Link out more than it rebuilds; keep the live agenda and PIT work separate.

Keep the immersive room immersive. osodaomeet remains a distinct hall with its own artistic language. The public circle may eventually link to it, but must not replace it.