Squad Roles (Knowledge & RUN role mapping) · squad-roles
Owner directive (2026-07-10), canonical. "Knowledge Engineer - DOOIT / Knowledge Analyst - DITTO / Knowledge Management - Assitant / Knowledge Architect - companion / Knowledge Executive - Advisor / Knowledge Deisgner - Construct" (verbatim, owner spelling preserved). [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:552-557]
Content
Every dynamic squad in the HOS-Instance build seats the same six knowledge roles, each bound to one mobilizer of the canonical 8-level hierarchy (D26: BOT < DITTO < DOOIT < ASSISTANT < COMPANION < ADVISOR < HOST < LOOPER [src: HOS-Webdoc/web/src/data/hos-specification.ts:466]). construct is a generative wrapper at Assistant level per D17 [src: HOS-Webdoc/web/src/data/hos-specification.ts:402]; MAESTRO is a functional role, not a level, per D2 [src: HOS-Webdoc/web/src/data/hos-specification.ts:509].
The six knowledge roles (OWNER-2026-07-10)
| Knowledge role | Mobilizer | Duty (owner's words) |
|---|---|---|
| Knowledge Engineer | dooit | "Agentic Execution, webservicing, triggers" for the pods [src: …/knowledge-management-and-concept-modeling.md:550]; "js functions are loops of DOOITs" [src: :559] |
| Knowledge Analyst | ditto | "API Gateway for the PADs" [src: :550]; "RAG, GatewayAPI, Cache - DITTO" [src: :561] |
| Knowledge Management | assistant | "The Assitant is the leader, dealing with merging, testing, and orchestrating, allocating the ncessary." [src: :548] — canonical datan name "Jules" (D24) [src: HOS-Webdoc/web/src/data/hos-specification.ts:452] |
| Knowledge Architect | companion | "bringing the creative self of the Holon Print of the brain of the Human Looper" [src: :547] — canonical datan name "Modo" (D25) [src: HOS-Webdoc/web/src/data/hos-specification.ts:459] |
| Knowledge Executive | advisor | "The advisor mirrors reception of the world and their stakeholders and makerts and flutuations." [src: :546] |
| Knowledge Designer | construct | Generative/design output; a Construct is "data that uses generative Loops" (D17) [src: HOS-Webdoc/web/src/data/hos-specification.ts:402] |
The three RUN roles (OWNER-2026-07-10)
| RUN role | Mobilizer | Verbatim |
|---|---|---|
| RUN Leadership | assistant | "RUN Leadership - ASSITANT" [src: …/knowledge-management-and-concept-modeling.md:563] |
| RUN Management | companion | "RUN MANAGEMENT - COMPANION" [src: :565] |
| RUN Maintainer | advisor | "RUN MAINTAINER - ADVISOR/Executive" [src: :567] |
The owner generalizes the mapping: "This is the same for any Loop, Run, Node, Cycle, Looper (Humans with Neural Engine), Agent (Datans with Neural Ware)." [src: …/knowledge-management-and-concept-modeling.md:569]
Claude's seat
The owner instances Claude as the Companion of this build: "you are a Companion, with Neural Engine at Claude" [src: …/knowledge-management-and-concept-modeling.md:614]. Claude therefore holds the Knowledge Architect / RUN Management seat and runs the neural-engine; Advisors are to be created "with the best open models" [src: :614] under the Knowledge Executive seat.
Variants
| # | Definition (verbatim) | Source | Ruling | Status |
|---|---|---|---|---|
| A | "The Companion is the maintainer, bringing the creative self of the Holon Print of the brain of the Human Looper) and the Prosperity definer for the Consumer." | [src: …/knowledge-management-and-concept-modeling.md:547] | OWNER-2026-07-10 → the later, explicit RUN-role enumeration (B) is the operative seat assignment; A's "maintainer" describes the Companion's custodial relation to the Looper's creative self, not the RUN Maintainer seat | variant |
| B | "RUN MAINTAINER - ADVISOR/Executive" | [src: …/knowledge-management-and-concept-modeling.md:567] | OWNER-2026-07-10 → chosen: the enumerated RUN-role list is the specific, exhaustive mapping; Maintainer = Advisor | canonical |
Composition
- uses: dooit · ditto · assistant · companion · advisor · construct (the mobilizers seated) · entity-hierarchy / mobilizer-level (the hierarchy the seats respect) · gear-sets (each seat's deterministic loadout)
- used-by: squad-eggtech · squad-schematic · squad-instance (all three seat tables) · sop-001-loop-execution / sop-003-run-dispatch (procedures that address seats by role)
See also
- squad — the squad concept itself
- datan · looper — who fills the seats ("Looper (Humans with Neural Engine), Agent (Datans with Neural Ware)")
- neural-engine — what the Companion (Claude) runs