Model-Derived Views
Data Views are lightweight projections of the central model. They store only layout positions and style overrides. Entity data, properties, types, and relationships come from the model at render time, so views can never drift from the source of truth.
A common failure mode in architecture documentation is the diagram that was correct when it was drawn but has since drifted from reality. An entity was renamed in the database, but the ERD still shows the old name. A property was added, but the diagram was not updated. The diagram becomes worse than useless - it actively misleads anyone who reads it.
NeoArc eliminates this problem by making views projections of the model rather than independent artefacts. A view does not store entity data. It stores a reference to the model entity, plus layout coordinates and optional style overrides. When the view renders, it reads entity data - properties, types, key roles, relationships - directly from the model. If a property is renamed in the model, every view that includes that entity shows the new name immediately. There is no sync step. There is no manual update. The view cannot disagree with the model because it reads from the model.
The Data View
A Data View is a force-directed graph canvas where model entities appear as interactive nodes. Each view has a single purpose defined by its view mode and profile.
Entity Overlay
The Entity Overlay is the standard way to inspect any node's properties. Click a node (or press Alt+Enter) to open a floating panel showing the full property table with incoming and outgoing relationship pills on either side. The overlay works identically in both the editor and the published viewer.
What Views Store vs. What They Read
Understanding the separation between stored and derived data is key to understanding why views cannot drift.
Persistence Mode
Persistence mode Data Views are for database architects and developers. The Entity Overlay displays ERD-style columns with types resolved through the selected database profile.
Search Mode
Search mode Data Views are for search engineers configuring index mappings. The Entity Overlay shows search-specific columns resolved through the selected search profile.
Each search field can also be expanded within the overlay for deep configuration detail: text analysis settings, vector search parameters, storage and performance options, query capabilities, sub-fields, and governance metadata. All values are read from the model property's search projection and resolved through the active search profile.
Multiple Views, Same Entities
A single model entity can appear in multiple Data Views simultaneously. A Customer entity might appear in a high-level persistence view with a SQL Server profile for the DBA, another persistence view with a PostgreSQL profile for the migration team, and a search view with an Elasticsearch profile for the search team. All views show the same entity data because they all read from the model. Each view applies its own profile for type and naming resolution.
Graph Canvas Features
All Data Views share the same interactive graph canvas with these capabilities.