SC-002 — Neural Engine Run Loop (Swimlane) · sc-002-neural-engine-run

Owner directive (2026-07-10), canonical. "use the neural engine to organize the Runs of the squad and the knowledge base of the construct. … 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:451]

Content

The run loop the neural-engine executes — "the kernel-level workflow engine (N8N+ComfyUI+LLM) that Sapiens3 uses to execute" per D12/D21 [src: HOS-Webdoc/web/src/data/hos-specification.ts:430]. Lanes: Owner → Companion / Neural Engine → Squads (6 roles) → Library + dispatch.json → commits. Every dispatched loop must clear the cognitive-loop (Cognis → Kernels → Neuralwares [src: wiki/engines/cognitive-loop.md:3]) and close with a commit.

The six squad roles (owner-fixed, 2026-07-10)

All verbatim from the owner prompt [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:552] — "This is the same for any Loop, Run, Node, Cycle, Looper (Humans with Neural Engine), Agent (Datans with Neural Ware)." [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:569]

Swimlane

sequenceDiagram
  participant OW as Owner (Looper)
  participant NE as Companion / Neural Engine
  participant SQ as Squads (6 roles)
  participant LIB as Library + dispatch.json
  participant GIT as Commits / PRs

  OW->>NE: dated prompt → archived as authority (OWNER-YYYY-MM-DD)
  NE->>LIB: read ONLY library cards (playbooks, cookbooks, schemas, rails)
  NE->>LIB: write run state → dispatch.json (schema-dispatch-json)
  loop every tick (intervalSeconds: 600)
    NE->>LIB: wake · tick++ · heartbeat
    NE->>SQ: allocate capability (gear-sets, neuralwares)
    SQ->>LIB: pull playbook step at cursor (work particle)
    SQ->>SQ: Cognitive Loop: Cognis → Kernels → Neuralwares
    alt gate passes (method → execute)
      SQ->>GIT: one commit per loop (PR branch, never main)
      SQ->>LIB: advance step cursor · spark successor loops
    else gate fails
      SQ->>SQ: bounce back / swap neuralware (academy) and retry
    end
    SQ-->>NE: squad states + blockers
    NE->>LIB: write-back cursors, heartbeats[], owner_gated
    NE-->>OW: surface owner-gated items (never enter secrets)
  end
  GIT-->>OW: reviewable trail — "PR following the interactions of the systems"

Grounding: the tick/interval/cursor/heartbeat state machine is modelled on the RUN-015 autoloop ("intervalSeconds": 600, "tick": 22, playbook queues PB-A…PB-F, owner_gated, rails) [src: runs/RUN-015-autoloop.json:8]. The retry-by-new-neuralware rule is owner-fixed: "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" [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:612]. Squad instances for this run: squad-eggtech (tech optimal), squad-schematic (kernel/cogni/genome flow), squad-instance (Royal Orbit) [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:526].

Composition

• uses: neural-engine · cognitive-loop · schema-dispatch-json · pb-003-run-dispatch · gear-sets · squad-roles · bpmn-neural-engine-run (BPMN rendering of this flow)
• used-by: bp-001-spatial-site (workstation page renders these lanes) · kernel-neural-engine · cogni-neural-engine · sop-003-run-dispatch

See also

• sc-001-kernel-cogni-genome — what each dispatched loop builds against
• looper · datan · squad · mobilizer-level