Gardens

A place for coordination to happen.

Garden A shared coordination environment built around something people are actually trying to do.

A Garden gives a project, place, group, initiative, or other bounded purpose enough shared context for people to see what needs attention and organize action around it.

Shared context

A Garden holds what coordination needs.

Not everything has to become a task. The Garden makes relevant context easier to see, relate, and carry forward.

  • NeedsWhat requires attention
  • OffersWhat can be contributed
  • QuestionsWhat remains unclear
  • OpportunitiesWhat could become possible
  • PeopleWho can participate
  • ResourcesWhat is available
  • Coordinated workWhat is taking shape
  • DecisionsWhat direction was chosen
  • OutputsWhat remains visible

The basic cycle

The Garden contains the work.

Within the Garden, attention can become bounded effort—and bounded effort can leave an observable result.

  1. 01

    Signal

    Something requires attention.

    A need, offer, question, observation, opportunity, or proposal enters the shared environment.

  2. 02

    Run

    A bounded effort forms around it.

    Relevant people, information, resources, timing, and decisions organize around a defined piece of work.

  3. 03

    Proof

    Something observable remains.

    A decision, plan, completed action, build, record, or other visible output carries the work forward.

Why this is different

Most online spaces preserve conversation.
A Garden is intended to preserve coordination.

Conversation may happen, but it is not the final structure. The important thing is that needs, decisions, efforts, and outputs become visible—and retain continuity beyond the moment they were discussed.

Conversation
can move quickly and disappear into a stream.
Coordination
keeps the relevant context connected to action and result.

Use patterns

A Garden can exist wherever coordinated effort needs a boundary.

These are examples of how the architecture can be applied—not claims of completed deployments.

  • 01ProjectA defined objective and the work around it.
  • 02PlaceActivity connected to a physical environment.
  • 03Working groupShared context for a temporary group.
  • 04Community effortNeeds, offers, action, and visible results.
  • 05Temporary initiativeCoordination that has a clear beginning and purpose.

The public model

Architecture, environment, surface.

  1. 01Shared Light

    The human-centered coordination architecture.

  2. 02Gardens

    The bounded environments where coordination happens.

  3. 03FieldPlay

    The software surface being developed to support and navigate the model.

    View FieldPlay status →

Interactive example

Enter a Demonstration Garden.

Watch a neutral example move from an unresolved Signal to a bounded Run and a retained result. It is an interactive simulation—no live people or community activity are represented.

Enter Demonstration Garden