Mental model·Worlds

Mental model

Worlds

A world in Blue is the set of blocks you participate in. Not one giant application — many separate interactions, each with its own participants, rules, and state, taken together forming your world.

Participation, not ownership

Traditional software often assumes one app, one database, one owner, one interface. That makes "your world" equal to "everything you own." Blue is different.

Your world is not everything you own. It is the set of Blue documents you participate in.

You may participate in:

  • a shop you run
  • an order someone else opened with you
  • a payment governed by a guarantor you do not control
  • a delivery flow that includes a courier you have never met
  • a service contract with another business
  • a partnership proposal you are still negotiating
  • an internal workflow at the company you work for

Each of those is its own block. Taken together, they form your world.

Example: Alice's world

Alice runs a flower shop. Her world may include:

  • her shop block
  • a shop automation block with her OpenClaw agent
  • an incoming order block — Alice + customer
  • a payment block — Alice + customer + bank
  • a delivery block — Alice + courier + customer
  • a partnership block — with a local hotel

Bob's view of the same world

Bob, the customer, also has a world. From his side it includes the order block (Alice + Bob), the payment block (Bob + Alice + bank), the delivery block (courier + Bob), and his mandate block (Bob + Bob's agent). Bob does not see Alice's shop automation block, because he does not participate in it.

Worlds overlap. Alice's order block is part of Alice's world and Bob's world at the same time.

The bank's view

The bank sees the payment block (and PayNote rules attached to that transaction). It does not see the order details, the shop, or the delivery confirmation, except where those are explicitly composed into the payment.

Why this matters

Scope

You only need to understand the interactions you are part of.

Privacy

Not every participant sees everything. Each block has its own participants and visibility model.

Composition

Blocks can reference or trigger each other, but they remain separate.

Identity

A participant may appear in many blocks, often through the same timeline identity.

How participation can change

Participation is per-block. A participant can be removed from one block (revoked from a mandate, removed from an order channel) but remain in others. Their world changes shape — the protocol does not. A world is not a single membership list; it is a per-block set of memberships.

Worlds can grow organically

Start with one shop. Then add an order, a payment, a service, a partnership, a refund flow, a recurring subscription. This is how "building reality" works in Blue — you do not build one monolith, you add new blocks to the world.

Worlds are not necessarily tied to MyOS

MyOS is one environment where worlds can be created and observed. But the world itself is not MyOS-specific. Blue blocks can, in principle, be processed elsewhere, hosted elsewhere, connected to other timeline providers, and moved across runtimes. That openness matters.

If blocks are interactions, a world is: the set of interactions you are part of. That is much closer to real life than "one application owns everything."