Entity 360 assembles a resource-centered view from the typed graph. It is the best starting point after search because it keeps identity, facts, and relationships in one tenant-scoped context.
Review the entity type, fully qualified name, display fields, aliases, organization, workspace, and selected context. An alias supports discovery but does not replace the entity’s canonical identity.
Aspects contain reusable facts validated by their aspect type. Version history lets readers distinguish the latest fact set from earlier evidence. A missing aspect can mean the entity type does not bind it, it was not ingested, or the current identity cannot view it.
Field references represent addressable nested fields such as columns. Hierarchy children and path operations describe structural containment. They are distinct from typed edges: hierarchy answers “where is this resource,” while an edge answers “how are these resources related.”
Related edges are constrained by relationship types. Use direction and type to understand whether the entity reads from, writes to, depends on, owns, runs on, or has another declared relationship with its neighbor.
The search document controls discoverability of indexed identity and metadata. Traversal expands through permitted edges with direction, depth, and relationship filters. Specialized 360 projections for tables, services, repositories, KPIs, or environments may add resource-specific views backed by the same graph.Continue with Lineage for dependency-focused traversal.
