AEOS
--:--:--

Knowledge Graph

The relationship engine. 515 entities and 1114 relationships, projected from every module in the enterprise — nothing here is authored twice. Rename a department and its node renames, because the node is that department.

Open ExplorerGraph search
515
Total nodes
1114
Relationships
14
Entity types
15
Relationship types
3
Companies
203
AI agents
51
Projects
4.3
Density
edges / node

Graph health

99Graph health
Graph health: 99 out of 100

Measures connectedness and integrity, not size. Adding a company does not raise it — a graph that scored higher for being bigger would be a vanity metric.

  • Orphan nodes7
  • Dangling edges0
  • Mean degree4.33
Orphans by type
  • Memory Record7

Dangling edges name an entity no projector emitted — a stale key, or a module referencing something this app does not model. They are counted and excluded rather than drawn, so the map never shows a line to nothing. Grouping them by the missing end names the gap instead of just sizing it.

Most connected8

Degree centrality — how many relationships touch the entity. A proxy for importance, not a synonym for it: the node everything hangs off is the one a change ripples through.

Recently updated nodes6

Recently updated relationships8

Entities by type14

  • Company3
  • Department13
  • Executive12
  • Manager8
  • AI Agent203
  • Project51
  • Workflow10
  • Task116
  • Memory Record44
  • Knowledge Article6
  • Document11
  • Report9
  • Channel23
  • Client6

Relationships by type15

  • Works with229
  • Owns206
  • Assigned to191
  • Depends on104
  • References82
  • Member of76
  • Manages74
  • Uses33
  • Approved by24
  • Belongs to21
  • Reports to19
  • Created by19
  • Communicates with15
  • Stored in11
  • Related to10

Departments by connectedness6

How much of the enterprise hangs off each department. The one at the top is where a reorganisation would be felt hardest.

Tags in use18

agent83write78done65high55working54normal51read-only49backlog45gsd33active31rev27department21operations21claude-opus-520del19finance19research19sales19

Entity types14

  • Companycompany

    A portfolio company. Owns departments, projects and agents.

  • Departmentdepartment

    A functional unit. Staffed by AI employees, led by a manager.

  • Executiveexecutive

    An executive seat. Owns departments and approves gates.

  • Managermanager

    A department manager. Reports to an executive seat.

  • AI Agentagent

    An installed fleet agent with a tool grant.

  • Projectproject

    A unit of delivery inside a department.

  • Workflowworkflow

    A routed chain of stages with approval gates.

  • Tasktask

    One unit of work inside a workflow stage.

  • Memory Recordmemory

    A durable fact the enterprise has learned.

  • Knowledge Articleknowledge_articleno module yet

    Written guidance. Curated, versioned, cited by workflows.

  • Documentdocumentno module yet

    A file held in a company knowledge base.

  • Reportreportno module yet

    A generated read over a period.

  • Channelchannel

    A communication surface where entities talk.

  • Clientclientno module yet

    An external party a company delivers to.

Adding a fifteenth type is a row in ENTITY_TYPES plus a projector. No component reads a literal type key — they all iterate this table.

Relationship types15

  • Ownsowns↔ belongs_to

    Containment. A company owns its departments and projects.

  • Belongs tobelongs_to↔ owns

    The inbound reading of ownership.

  • Managesmanages↔ managed_by

    Line authority over a department or a person.

  • Reports toreports_to↔ has_report

    The org chart edge. A manager reports to an executive seat.

  • Member ofmember_of↔ has_member

    Staffing. An agent is a member of a department.

  • Assigned toassigned_to↔ has_assignment

    Work allocation. A task is assigned to an agent or department.

  • Works withworks_with↔ works_withassociative

    Symmetric collaboration, inferred from shared work.

  • Depends ondepends_on↔ blocks

    A blocking dependency between tasks or workflows.

  • Created bycreated_by↔ createdassociative

    Provenance. Who recorded or authored this.

  • Approved byapproved_by↔ approves

    An approval gate's authority.

  • Usesuses↔ used_byassociative

    An agent uses a tool; a workflow uses a template.

  • Referencesreferences↔ referenced_byassociative

    A citation. The weakest link the graph stores.

  • Communicates withcommunicates_with↔ communicates_withassociative

    Participation in a shared channel or thread.

  • Related torelated_to↔ related_toassociative

    Symmetric association with no stronger reading available.

  • Stored instored_in↔ storesassociative

    An artefact's location — a document in a knowledge base.

Edges are stored once and directed. The inverse is a display concern, which is why it lives in the registry rather than as a second stored edge that could drift.