Mesh View
A data product network visualisation showing projects as nodes, contracts as directed edges, health indicators for version drift, and protocol annotations - all auto-derived from the governed contract registry.
What You See
The mesh view presents the estate as a network diagram. Projects are nodes, and contracts between them are directed edges flowing from producer to consumer. Each edge carries metadata - the contract name, version, protocol type, and a health indicator showing whether the consumer is on the current version.
Key Features
Health Status Logic
Health status is computed per contract based on the relationship between the current version and what consumers are actually using.
| Status | Colour | Meaning |
|---|---|---|
| Healthy | Green | All consumers are on the current version, or the contract has no consumers yet |
| Version Drift | Amber | Some consumers are behind the current version and need migration |
| Ungoverned | Red | The contract has no approved versions - it exists but has not been through the approval workflow |
Manual Flows
Not every cross-project connection has been formally governed yet. The mesh view supports manual flows - edges that the estate architect adds to represent known but undocumented connections. Manual flows appear with distinct styling (dashed lines) and serve as a reminder that these relationships should eventually be formalised through the contract registry.
How Edges Are Derived
Display Settings
The mesh view provides display toggles to control what information is shown - version indicators, protocol labels, and health status badges can each be toggled independently. Layout options include force-directed, circular, and hierarchical arrangements. View layouts are persisted to .neoarc-studio/mesh-views/ so your preferred configuration is preserved.