Squad · squad

Owner directive (2026-07-10), canonical. "Any knowledge particle can become a Holon, this is recursive to infinity both ways, a datan may have 10 dynamic squads below him working on holons it needs to finalize its atoms. Humans work together, not above, not supervising, not in the loop, same thing." [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:600]

Content

A Squad is the execution unit of dwork: a group of datans (anchored to a human looper) that runs loops over work particles. Baseline configuration: "20 squads, 5 datans each, max 2 concurrent executions. Can open sub-squads." [src: HOS-Webdoc/web/src/data/hos-specification.ts:152]

Roles (D2): SquadRoleType = 'leader' | 'success-manager' | 'manager' | 'maintainer' | 'maestro' | 'member' — "MAESTRO is a functional ROLE (squad manager), not a mobilizer LEVEL" [src: HOS-Webdoc/web/src/lib/sapiens3/types.ts:69] [src: HOS-Webdoc/web/src/data/hos-specification.ts:509].

Approval chain (D7): "APPROVAL CHAIN (success path, fires on every delivery): DOOIT→ASSISTANT(leader)→DITTO(success-mgr)→MAESTRO(mgr)→ADVISOR(maintainer). DSync (failure path, fires when stuck): ASSISTANT detects stuck → flags DSync → COMPANION develops creative solution → asks ADVISOR(s) → Game Design consensus." [src: HOS-Webdoc/web/src/data/hos-specification.ts:549] Note: whether MAESTRO is always present or optional in the chain is open as C-08 [src: wiki/development/HANDOFF.md:145]. Run-role mapping (OWNER-2026-07-10): "RUN Leadership - ASSITANT · RUN MANAGEMENT - COMPANION · RUN MAINTAINER - ADVISOR/Executive" [src: ...knowledge-management-and-concept-modeling.md:565-567].

Dynamic Squads (OWNER-2026-07-10): "dynamic events on dynamic Ventures by Dynamic SQUADS (Datans using Plabooks, tools, models, context, skills) to compose, craft, produce, prepare, render, delivery and execute" [src: ...:469]. Squads are recursive: a datan may spawn dynamic squads below itself to finalize its atoms — the same whole/part recursion as holons. The neural-engine sets each squad's gear (gear-sets) and dispatches its Runs.

The three founding squads of this instance are squad-eggtech, squad-schematic, squad-instance [src: ...:526].

Composition

• uses: datan (members), squad-roles (role definitions), pb-003-run-dispatch + sop-003-run-dispatch (dispatch), gear-sets (equipment)
• used-by: dwork (scheduler kernel), loop (execution), genome-strand (datanAllocation.squadIds), spatial-site (built by squads)

See also

• squad-roles — the role catalog
• okrs-2026-h2 — what squads are measured on
• [Upstream wiki page](../../../wiki/engines/sapiens3.md)