DOOIT · dooit
D22 ledger ruling, canonical (dual-axis). "RESOLVED: Both definitions coexist. ETYMOLOGY (Noology Dictionary): DOOIT = Discrete Operator Overarching Intelligent Tokens. … RUNTIME (current code): DOOIT = the 4-stage dispatch pipeline Prepare→Method→Execute→Deliver. Every action flows through DOOIT. Both are correct: A is what DOOIT IS, B is what DOOIT DOES." [src: HOS-Webdoc/web/src/data/hos-specification.ts:438]
Content
The DOOIT is the Worker of sapiens3 — "a discrete agent performing empirical, canonical, and cabal work. Optimizes for specific tasks, transports Tokens between PADs and PODs" (Noology Dictionary, via D22). It is level 3 of the 8-level mobilizer-level ladder (BOT < DITTO < DOOIT < ASSISTANT < COMPANION < ADVISOR < HOST < LOOPER, D1) [src: HOS-Webdoc/web/src/lib/sapiens3/types.ts:28] and one of the 6 datan archetypes [src: HOS-Webdoc/web/src/lib/sapiens3/types.ts:57].
Runtime (what it DOES): every action is wrapped in the 4-stage dispatch Prepare → Method → Execute → Deliver [src: HOS-Webdoc/web/src/lib/sapiens3/dooit-dispatch.ts:8]. Run as work, a DOOIT is a 31-second work particle (work-units) [src: HOS-Webdoc/web/src/lib/sapiens3/types.ts:18] [src: wiki/engines/cognitive-loop.md:78]. Petra rule K001 (petra): any action goes through DOOIT. [src: wiki/development/HANDOFF.md:68]
OWNER-2026-07-10 additions (canonical):
- Serves pods: "The meembers are DOOITS (Agentic Execution, webservicing, triggers) for the PODS and DITTOS (API Gateway for the PADs)". [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:550]
- Knowledge role: "Knowledge Engineer - DOOIT". [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:552]
- Functional-declarative usage: "js functions are loops of DOOITs" — in code, plain JS functions are read as loops of DOOITs. [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:559]
Inside a squad, DOOIT delivery is reviewed through the approval chain DOOIT → assistant (leader) → ditto (success-mgr) → MAESTRO role (construct card, D2) → advisor (maintainer). [src: HOS-Webdoc/web/src/data/hos-specification.ts:509] [src: wiki/GLOSSARY.md:205]
Variants
| # | Definition (verbatim) | Source | Ruling | Status |
|---|---|---|---|---|
| A | "DOOIT = Discrete Operator Overarching Intelligent Tokens. 'The Worker. A discrete agent performing empirical, canonical, and cabal work. Optimizes for specific tasks, transports Tokens between PADs and PODs.'" | Noology Dictionary, quoted in [src: HOS-Webdoc/web/src/data/hos-specification.ts:438] | D22 → canonical on the etymology axis (what DOOIT IS) | canonical |
| B | "DOOIT = the 4-stage dispatch pipeline Prepare→Method→Execute→Deliver. Every action flows through DOOIT." | [src: HOS-Webdoc/web/src/data/hos-specification.ts:438] [src: HOS-Webdoc/web/src/lib/sapiens3/dooit-dispatch.ts:8] | D22 → canonical on the runtime axis (what DOOIT DOES) | canonical |
Composition
- uses: Tokens (transport form, D28 content hierarchy), loop (Datan Loop, D18), neuralware (equipped capabilities)
- used-by: pod ("Inside the POD lives the DOOIT", D4 [src: HOS-Webdoc/web/src/data/hos-specification.ts:525]), assistant (schedules DOOITs, D24), squad (member role), cognitive-loop, work-units (31s particle)
See also
- ditto · assistant · companion · advisor · bot · entity-hierarchy · mobilizer-level
- [Cognitive Loop worked example](../../../wiki/engines/cognitive-loop.md)