Skip to main content

Communities

Nobody has to do this work alone. A community is a named workspace many citizens share — the top of the hierarchy the whole product is organised around.

COMMUNITY   a shared workspace, with an access model
  AREA      a named subdivision holding a set of decisions
    DECISION  one question, one position, one chain

That same path is how scope works everywhere else: facts, metaphysics and law all assemble along it, from Earth down to a single decision.

The access model​

Every community carries one: owners, writers, readers, plus a world-read flag.

So a community can be a small private working group, an open project anybody can read and a few can edit, or a fully public record. The model is explicit rather than implied by a setting somewhere.

The cursor​

You are always "in" one community, and switching is a dropdown at the top of the areas list rather than a navigation event. It is per-user state — your cursor, not a property of anything shared.

Small detail, large effect: it means moving between communities does not feel like leaving one application and entering another.

Areas​

An area is a named subdivision holding a set of decisions. It is the scope at which people are actually working on the same thing, and therefore the scope at which positions aggregate.

Seed communities​

A fresh install boots with a couple of seeded communities so the product is not an empty room on first launch, and so the hierarchy is legible before you have built anything.

Pages in this area​

Where to go next​

Last updated on