Holons

How a holon works

A holon is data. It lives on its entity, it is called into existence when it is needed, and it answers inside a structure that already exists.

Fixed structure, intelligence inside. Everything a holon can do follows from where it sits. It never improvises a route, a value or a role.

Six things

How a holon behaves

  • It lives on its entity

    Every entity has its own holon: an id that lives on the entity, so it always knows what it is for.

  • Called into existence in one step

    A single request brings it to life with everything it needs: what a holon is, where it sits, its function, its purpose and the context it was called from.

  • It answers in selections

    It chooses from typed values: a range, a category, a period, a place, with one sentence of reasoning. Every answer can be compared and checked.

  • It can be assigned work

    A holon is one of the things a task can be assigned to. A task answers one question.

  • It routes along a fixed structure

    The Org holon sees across every function and routes each question to the function, process or specialist that owns it.

  • Information comes to you

    You don’t visit every holon. What matters rises to the top and arrives in your feed as tasks and exceptions.

Cells

What every answer becomes

A cell is the record a task leaves behind. On its own it is abstract: an attribute, a value, a moment.

Put together, cells can be brought back to life as the entity they describe, seen as they stood in any past period, and given goals for the future. That is why holons answer in selections: a selection becomes a clean cell.

Suggestions

A suggestion box, on two schedules

Each holon proposes improvements from its own point of view.

It does so on a schedule rather than all the time: once every period, and after an event, especially one that missed.

Holon suggestions: Coming soon