Skip to main content

Node and system workspaces

A workspace is not only where people work. The platform provisions a parallel infrastructure workspace tree for itself, and understanding it is what makes "ask the node how it is doing" a coherent idea rather than a slogan.

The tree​

Alongside the home workspace every entity gets, the platform bootstraps a hierarchy of system workspaces, idempotently, keyed on the infrastructure object rather than on an entity id.

Figure: the infrastructure workspace tree. Each level is a real workspace with a scope kind naming what it represents, and parentage is explicit, so the node workspace is the roll-up parent of its cells' workspaces.

Table equivalent

LevelScope kindKeyed onWhat it is
OrganizationorgThe organization's base idThe organization's own face
NodenodeThe node idThe node's face: node-wide, cross-cell resources, and the roll-up parent of its cells
CellcellThe cell idOne cell's own face
ServiceserviceThe serviceA service's face within a cell

These are provisioned as workspaces of type system, and like every other home they are idempotent: bootstrapping the tree twice returns the same workspaces rather than duplicating them.

Why the node workspace matters​

This is the one worth understanding, and it does two jobs at once.

The node service maps its resources to it. Anything that belongs to the node rather than to any single cell has a home: resources that must be reachable regardless of which cell is currently serving, and state that has to survive a cell being replaced. A node is a logical identity over a set of cells, and this is where that identity keeps its things.

It is the roll-up parent of the node's cell workspaces. Parentage is set explicitly, so the hierarchy is a real edge rather than an inference from naming. That edge is what the roll-up walks.

The consequence is the property the architecture is built around: a cell can die and be replaced without the node losing an identity, a history, or a place to keep node-wide state. The node workspace persists through cell churn because it was never keyed on a cell.

Cross-cell resources​

Because the node workspace sits above the cells, it is the natural scope for anything that is not owned by one cell:

  • Node-wide state the node service holds on behalf of all its cells.
  • The roll-up view that answers estate-level questions.
  • The node's own inbox and feed, since a node is an entity with a home like any other.

Compare that with a workspace bound to a service group: a customer workspace is placed on cells and can be pinned to them, up to dedicating a whole group. A node workspace is above cells and is not placed on any of them in particular.

How the Mind reads this tree​

The tree is what makes the fractal roll-up work, and the shape is worth stating precisely because it is easy to describe as a simple average and be wrong.

The Node Mind is both things at once:

  • Its own. The Workspace Mind of the node's own default workspace: its semantic coherence, its governed load, and the standing of its owning entity.
  • Computed over its children. A fractal roll-up of the cells' and Edge Agents' Workspace Minds, so the node reflects the whole network while persisting through cell and device churn.

A persisted snapshot means the node can answer "how is my whole network doing" instantly, and while children are unreachable, which is the condition that actually obtains in the field.

Roll-up is opt-in where it should be​

Contributing to the node's shared semantic pool is not automatic. A workspace opts a vector space into or out of the node-wide pool deliberately, and the write enforces the isolation boundary on both legs: the caller must be a member of that workspace, and the space must actually belong to it, so a holder of the permission cannot flip a co-located workspace's sharing by path manipulation.

That is the right default for a platform where two workspaces on one node may belong to parties who do not share anything. Aggregate health rolls up; meaning is contributed on purpose.

The invariants survive the roll-up​

Three properties make the composition trustworthy rather than a dashboard average:

  • Coherence and net potential are rolled up as distinct axes and never collapsed. Strong internal agreement paired with low net gain surfaces as extractive, not as aligned.
  • The most-concerning child mode surfaces rather than being averaged away, on a severity ordering where long-horizon operation is best and short-horizon, survival-mode operation is worst.
  • Absent signals stay absent. A missing reading is reported as unknown, never fabricated as a zero.

Above the node, aggregation to the organization is optional, so a multi-node roll-up is something an organization turns on rather than something that happens to it.