conceptcanonicalD1D262 variants

Entity Hierarchy (Mobilizer Levels) · entity-hierarchy

Owner directive (D1/D26, resolved 2026-04-12), canonical. "RESOLVED: Use the cogloop.md/Lucas 8-level hierarchy from D1 as canonical: BOT < DITTO < DOOIT < ASSISTANT < COMPANION < ADVISOR < HOST < LOOPER." [src: HOS-Webdoc/web/src/data/hos-specification.ts:466]

Content

The Entity Hierarchy is the 8-level capacity ladder every mobilizer in sapiens3 sits on, ordered low → high, where each level holds the capacity of all levels below it [src: HOS-Webdoc/web/src/lib/sapiens3/types.ts:25]:

BOT < DITTO < DOOIT < ASSISTANT < COMPANION < ADVISOR < HOST < LOOPER

LevelRole (canonical doc comment)
bot"Lowest level, basic automated response"
ditto"Fetch/translation gateway (Verify→Validate→Augment→Disponibilize)"
dooit"Action executor (Prepare→Method→Execute→Deliver, 31s particle)"
assistant"Squad leader, oversees DOOIT execution"
companion"Learns Looper preferences, develops creative solutions"
advisor"Scientific golden standard with BIAS, Game Design consensus"
host"Digital twin of the human, holds the most data"
looper"Construct of a Host, holds capacity to run a founding CodeLoop"

[src: HOS-Webdoc/web/src/lib/sapiens3/types.ts:12-33]

The ladder is fixed in code as MobilizerLevel + MOBILIZER_ORDER [src: HOS-Webdoc/web/src/lib/sapiens3/types.ts:25] [src: HOS-Webdoc/web/src/lib/sapiens3/types.ts:35] — see mobilizer-level. The HANDOFF canonical-decisions table repeats it verbatim [src: wiki/development/HANDOFF.md:142].

Two clarifications keep this ladder clean:

  • MAESTRO is not a level. Per D2, "MAESTRO is a functional ROLE (squad manager), not a mobilizer LEVEL" [src: HOS-Webdoc/web/src/data/hos-specification.ts:509]; canon later renamed the archetype MAESTRO → construct (RUN-013 #6) [src: HOS-Webdoc/web/src/lib/sapiens3/types.ts:53].
  • The archetype enum is a different axis. NeuralNetworkType (6 datan archetypes: DOOIT · DITTO · CONSTRUCT · ASSISTANT · COMPANION · ADVISOR) classifies what kind of Datan; MobilizerLevel classifies how much it can mobilize [src: HOS-Webdoc/web/src/lib/sapiens3/types.ts:57].

Variants

#Definition (verbatim)SourceRulingStatus
A"BOT < DITTO < DOOIT < ASSISTANT < COMPANION < ADVISOR < HOST < LOOPER (8 levels). Source of truth: Lucas Session 2 prompt."[src: HOS-Webdoc/web/src/data/hos-specification.ts:501]D1 → chosen; D26 confirms it "subsumes" the Master Doc listcanonical
B"The Master Doc 6-level (HOST > ADVISOR > COMPANION > ASSISTANT > CONSTRUCT > DOOIT) is a SUBSET — active mobilizers in a typical ProLab session, replacing BOT/DITTO with CONSTRUCT (a generative wrapper, see D17)."[src: HOS-Webdoc/web/src/data/hos-specification.ts:466]D26 → "Both views are valid, but the 8-level is the union of all roles" — B is a valid projection, not a rival laddervariant

Composition

See also

  • matter-hierarchy — the matter ladder (what is acted on), distinct from this mobilizer ladder (who acts)
  • squad-roles
  • [Upstream wiki page](../../../wiki/architecture/entity-hierarchy.md)

Linked from — 18 cards