Architectural Intent Graph
The Architectural Intent Graph is the semantic backbone of NeoArc Studio. 33 node types and 19 edge types form a complete traceability network connecting every artefact in the workspace: pages, diagrams, schemas, APIs (REST, GraphQL, gRPC, AsyncAPI, Webhooks, MCP), model entities, views, and governance blocks. This graph powers impact analysis, data lineage, governance measurement, and deprecation tracking.
When you add a schema field, you are creating a node. When you embed a diagram in a page, you are creating an edge. When you map a schema field to a model property, you are creating a lineage relationship. When a risk block references a model entity, you are creating a governance edge. Everything you do in NeoArc Studio contributes to a semantic graph that captures the intent behind your architecture.
Most users never interact with the Intent Graph directly. They work with pages, diagrams, schemas, and APIs. But beneath every action lies this graph structure, enabling capabilities that traditional documentation tools cannot provide: impact analysis that traces a field rename across every API type, data lineage from API surface to database column, governance measurement that counts which entities have risk documentation, and deprecation tracking that identifies every active reference to a retired component.
Node Types (33)
The Intent Graph tracks every artefact in the workspace as a typed node. Nodes range from high-level documents to individual fields and properties.
Edge Types (19)
Relationships between nodes are captured as typed edges, each with specific semantic meaning. Together, they form the traceability network.
How the Graph Powers the System
The Intent Graph is not a feature you use directly. It is the infrastructure that makes every other feature work.
Graph Data Structure
The Intent Graph uses adjacency maps for O(1) edge lookups in both directions.
Query Capabilities
The Intent Graph service provides a rich query API for traversing relationships.