sopcanonicalOWNER-2026-07-10D18

SOP-001 — Loop Execution · sop-001-loop-execution

Owner directive (2026-07-10), canonical. "dont let the Neural Engine Execution or the Neural Ware Agenticly gettings things done stray a single word from the Kernels and the knowledge in general at the Library." [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:610]

Content

This SOP defines how any datan (or looper) executes one loop inside a run. It applies to all seven loop types (D18: Environment, Pipeline, Workflow, Datan, Work, Neural, Companion [src: HOS-Webdoc/web/src/data/hos-specification.ts:409]). The governing rule is the cognitive-loop: "Every action in Mainland is a Loop. A Loop is valid only once it has run the fixed sequence Cognis → Kernels → Neuralwares." [src: wiki/engines/cognitive-loop.md:3]

Procedure

  1. Take the row. Read the assigned playbook row (pb-001-spatial-site-loop, pb-002-library-authoring or pb-003-run-dispatch). A loop with no playbook row does not start.
  2. Equip the gear-set. Load exactly the gear-set the row names (gear-sets): its cookbooks, benchmark gates, schemas and registry neuralwares. No improvised tooling — the loadout is what makes the Datan "a deterministic agent to complete the task" [src: …/knowledge-management-and-concept-modeling.md:453].
  3. Read only library cards. All definitions and instructions come from the Knowledge Library; sources outside it are reached only through cards that cite them (sop-004-library-authoring).
  4. Traverse the Cognitive Loop. Execute through the Cognis in order, each on its own kernel, with equipped neuralwares injected at their stage [src: wiki/engines/cognitive-loop.md:17, 64].
  5. Clear the gate. Pass the Cognitive Loop gate (method → execute check against the approved playbook + frontier standard [src: wiki/engines/cognitive-loop.md:57]). A failed gate bounces the loop back, not forward [src: wiki/engines/cognitive-loop.md:94].
  6. Deliver the particle. Produce "the exact particle requested in the format requested" [src: …/knowledge-management-and-concept-modeling.md:612]. Delivery below the quality bar is a failed delivery (Dynamic Work approval threshold 0.6 [src: wiki/engines/cognitive-loop.md:95]).
  7. Commit. "every loop should have a commit, until the atom and the nodes, and etc with PR following the interactions of the systems." [src: …/knowledge-management-and-concept-modeling.md:586]
  8. Spark. Record the spark(s) the closed loop emits — the output artifact that initiates the next loops [src: wiki/GLOSSARY.md:2829].

Gear-swap rule (the academy rule)

"If the datan could not delivery what is expected, it should go to the academy and bring a new neuralware (N8N, ComfyUI,VisualStudio,Gitea,Servers,APIS,TOOLS, WHATEVER) to try again and bring the exact particle requested in the format requested." [src: …/knowledge-management-and-concept-modeling.md:612]

Constraints on the swap:

  1. A swap happens only after a failed delivery (gate bounce exhausted or particle rejected) — never pre-emptively mid-loop.
  2. The replacement neuralware must come from the same gear-set family as the failed one (gear-sets defines families); crossing families is a re-dispatch decision for the RUN Leadership seat (squad-roles), not the Datan.
  3. Every swap is logged in the run heartbeat (sop-003-run-dispatch): failed loop id, neuralware out, neuralware in, retry result.
  4. After the swap the Datan retries the same playbook row — the row, format and acceptance criteria do not change.

Composition

See also

Linked from — 20 cards