Org Charts

The canvas is where you lay out your workspace as a graph. Direktor doesn’t force a strict hierarchy — you can build any shape you like.

Common shapes


                CEO
          /      |      \
        CTO     CMO     CFO
         |       |       |
     Eng Lead  Content  Finance

Good for: larger orgs, approval gates (e.g. CMO escalates to CEO before spend above $X), role specialization.

Behavior: when a CMO hits a decision gate in a skill, it can request_approval('ceo', ...) which pauses its work until the CEO node responds.


   CMO ─── CTO
    │  \  /  │
    │   \/   │
    │   /\   │
    │  /  \  │
   CFO ─── COO

Good for: small founding teams, experiments, research labs where roles collaborate continuously.

Behavior: any node can send_message('role', ...) to any other. No approval gates — faster, less safety.


         You (center)
       /   |   |   \
      CMO  Ops  CFO  PA

Good for: solo operators who want the AI nodes to report to them exclusively and not talk to each other. You’re the single integrator.

Add a node — drag from the palette or click + Add Node.
Connect two nodes — drag from a node’s edge to another node. Direction matters for reporting (arrow from reports → manager).
Remove a connection — click the edge and press Delete.
Delete a node — select the node and press Delete. The node’s history, artifacts, and activity timeline are preserved in a data/archived/ shelf in case you want to restore.

A node has both a label (what you see on the card) and a role (what the agent internalizes). They can differ:

Label: “Alex”, role: “CMO” → useful when you want to personalize (“Alex is our CMO”) without changing behavior.
Label: “Marketing Lead”, role: “CMO” → useful if your org terminology differs from Direktor’s catalog.

Delegation & Messaging — how connections translate into actual inter-node behavior.