Holon · holon

Owner directive (2026-07-10), canonical. "Any knowledge particle can become a Holon, this is recursive to infinity both ways." [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:600]

Content

A Holon is the fundamental knowledge unit of HOS, borrowed from Arthur Koestler's holonic theory: "an entity that is simultaneously a whole and a part: complete in itself, yet a participant in larger structures" [src: wiki/knowledge/holons.md:3]. Operationally, "every processed source file becomes one Atomic Holon — a self-contained knowledge unit that carries content, semantic metadata, and a set of physics properties" [src: wiki/knowledge/holons.md:5].

In the matter-hierarchy (particle → atom → cell → node → holon → dyson), the Holon is the fifth rung: "self-contained whole that is also part of a larger system. 'Whole on itself' — interacts with anything. Deterministically identical if proper process followed" [src: HOS-Webdoc/web/src/lib/atomic-holon/matter-hierarchy.ts:104-107]. Per D27, Forms and Execution were conflated: the 9-level FORMS ladder (Unit→…→Entity) is one hierarchy; "(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].

The refinement flow is VoidWeb → AtomicWeb → Holons → Dysons [src: wiki/knowledge/holons.md:22]; the dikwc line assembles Datum → Information → Knowledge Particle → Concept Atom → Holon with physics constants (K_SPRING=0.1, G=0.5; super-cluster at ≥3 shared tags) [src: wiki/voidweb/DIKWC.md:3-21].

The recursion also organizes space: every District is a Holon District — composed of Holon Districts with six invariant organs (ProLab · Workstation · Library · Academy · Fortress · Lighthouse) [src: wiki/architecture/holon-districts.md:7,24]. And per OWNER-2026-07-10, a Holon's rendering is abstracted by its holonprint, with Runs attachable per Holon [src: ...knowledge-management-and-concept-modeling.md:496].

Composition

• uses: matter-hierarchy (its rung), dikwc (its production line), holonprint (its render abstraction)
• used-by: dyson (execution environment), districts (Holon Districts), loop (write-back target), spatial-site (rendered Holons), slice (Holons composed into sceneries), genome (generated through the AtomicHolon engine)

See also

• holonprint — how a Holon is rendered
• entity-hierarchy — OS → engines → Districts → Holons nesting
• [Upstream wiki page](../../../wiki/knowledge/holons.md)