Loop · loop
Owner directive (2026-07-10), canonical. "Hub, to update and talk with one another, every loop should have a commit, until the atom and the nodes, and etc with PR following the interactions of the systems." [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:586]
Content
A Loop is the atomic unit of action in HOS. "Every action in Mainland is a Loop. A Loop is valid only once it has run the fixed sequence Cognis → Kernels → Neuralwares" — that sequence is the cognitive-loop, the one rule of the system [src: wiki/engines/cognitive-loop.md:3]. A Loop is started by a looper or a datan, traverses every cogni on its own kernel, must clear the Cognitive Loop gate (method → execute), and on closing sparks the next Loops [src: wiki/engines/cognitive-loop.md:17].
In the dwork work hierarchy, the Loop sits between WorkParticle and Spark: Cycle → Node → Run → WorkParticle → Loop → Spark [src: wiki/engines/dwork.md:17]. Payment (LPz, D13) settles per completed loop on approval.
The hub rule (OWNER-2026-07-10): every Loop has a commit; interactions between systems follow as PRs. A Loop without a traceable commit is not a closed Loop. This binds Loops to version control the way particles are bound to the 31s timebox.
Seven loop types (D18): "7 distinct loop types per cogloop.md. (1) Environment Loop — planning, tools, agents, MCPs, memory, setup. (2) Pipeline Loop — stages with atomic verification + commit. (3) Workflow Loop — documentation concatenation, PAD/POD creation. (4) Datan Loop — DOOIT/DITTO/Assistant + DSync escalation to Companion → Advisor. (5) Work Loop — cost calculation, Aura/Warden/Essentia points, leveling. (6) Neural Loop — engine configuration. (7) Companion Loop — preference learning." [src: HOS-Webdoc/web/src/data/hos-specification.ts:409] Encoded as LoopType [src: HOS-Webdoc/web/src/lib/sapiens3/types.ts:113].
Variants
| # | Definition (verbatim) | Source | Ruling | Status |
|---|---|---|---|---|
| A | "LoopType — the 7 loop types from cogloop.md (D18). Each serves a different purpose in the cognitive cycle." (environment · pipeline · workflow · datan · work · neural · companion) | [src: HOS-Webdoc/web/src/lib/sapiens3/types.ts:110] | D18 → canonical typology | canonical |
| B | "Code currently has 1 generic Loop in loop-store.ts — will be expanded to typed loop categories in P2." | [src: HOS-Webdoc/web/src/data/hos-specification.ts:409] | D18 → acknowledged implementation gap, not a competing definition | variant (shipped subset) |
Composition
- uses: cognitive-loop (validity rule), cogni + kernel (traversal stages), neuralware (equipped capabilities)
- used-by: dwork (work hierarchy), datan / looper (initiators), squad (execution), holon (write-back target), slice (behavior loops), sop-001-loop-execution
See also
- cognitive-loop — the rule every Loop must satisfy
- work-units — Cycle/Node/Run/Particle/Spark context
- [Upstream wiki page](../../../wiki/engines/cognitive-loop.md)