conceptcanonicalD27

Dyson · dyson

Owner ruling (D27, 2026-04-12), canonical. "(EXECUTION, separate) Holon → Dyson — Holons wrap Forms for execution, Dysons are the infrastructure environments where Holons run." [src: HOS-Webdoc/web/src/data/hos-specification.ts:473]

Content

A Dyson is the civilization-scale entity at the top of the matter-hierarchy (particle → atom → cell → node → holon → dyson): "Infrastructure instances where holons execute. Containers, environments, deployments." [src: HOS-Webdoc/web/src/lib/atomic-holon/matter-hierarchy.ts:123-126] A Dyson aggregates holonIds [src: HOS-Webdoc/web/src/lib/atomic-holon/matter-hierarchy.ts:128-130].

The name evokes the Dyson sphere: where a holon is a self-contained whole/part, a Dyson is the environment that harvests and hosts a population of Holons — droplets, container tiers, deployed OS instances. The knowledge refinement flow terminates here: VoidWeb → AtomicWeb → Holons → Dysons — "holons are aggregated into infrastructure-scale Dysons" [src: wiki/knowledge/holons.md:22].

Per D27, keep the two hierarchies distinct: the 9-level FORMS ladder (Unit → Block → Sphere → Particle → Atom → Cell → Node → Component → Entity) describes capability of matter; the EXECUTION pair Holon → Dyson describes where wrapped forms run. Do not interleave them.

Operationally, this project's Dysons are the droplet-hosted instances (see src-droplet-index): the Mainland production droplet, the planned Neural-Engine droplet and Neural-Ware droplet ("create another droplet, focused on Neural engine, and another at Neural Ware" — OWNER-2026-07-10 [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:614]).

Composition

See also

  • holon — the unit Dysons execute
  • entity-hierarchy — OS-level nesting above
  • [Upstream wiki page](../../../wiki/knowledge/holons.md)

Linked from — 7 cards