Logo
NeoArc Studio

Architecture Hub Mode

A dedicated workspace mode for lead and estate architects to govern federated organisations - importing artefacts from project teams, managing contracts, visualising the estate mesh, and tracking cross-project impacts.

What Is Hub Mode?

Hub mode is a workspace mode that transforms a NeoArc Studio workspace into an architecture governance centre. Any workspace can be switched to hub mode from the project settings. When enabled, the sidebar changes to show hub-specific navigation sections - dashboard, imports, contracts, taxonomy view, and mesh view - while retaining full access to the underlying workspace features.

The hub workspace is where estate architects work. Project teams continue using standard studio-mode workspaces for their day-to-day architecture work. The hub imports their exports, governs the contracts between them, and distributes approved content back downstream.

Hub Capabilities

The hub brings together several interconnected features that work as a unified governance system.

Federated Intent Graph
A unified graph assembled from all imported project artefacts. Every node is tagged with its source project and import provenance, enabling cross-project queries and transitive impact analysis.
Contract Registry
A schema-registry-inspired system for tracking versioned contracts. Full content snapshots at every version, consumer bindings, backward compatibility classification, and approval workflows.
Taxonomy View
Visualise the estate organised by any shared taxonomy - business domains, data classification, compliance tiers. Switch dimensions without changing the underlying entity data.
Mesh View
A data product network showing projects as nodes and contracts as directed edges. Health indicators show version drift, and every connection traces back to a governed contract.
Estate Impact Analysis
When a breaking change arrives via re-import, the hub traces the blast radius across all consuming projects. Migration tasks are auto-generated and tracked on the task board.
Distribution
Package approved contract versions into signed artefacts targeted at specific consumer projects. The hub controls what each consumer receives.

Switching Between Modes

Any workspace can switch between studio mode and hub mode from the project settings. The toggle is immediate - enabling hub mode navigates to the hub shell with its governance-focused sidebar, while switching back returns to the standard studio workspace. The underlying project files remain unchanged; hub mode simply adds a governance layer on top.

The Import-Govern-Distribute Cycle

The hub operates on a clear cycle. Project teams export artefacts containing their projections, schemas, APIs, and other architectural content. The estate architect imports these into the hub, where they are registered, versioned, and reviewed. Approved contracts are then distributed to consuming projects as curated artefact packages.

This cycle means that every cross-project dependency passes through the hub. There are no informal handoffs or undocumented integrations. The mesh view reflects exactly what has been governed, not what someone guesses might exist.

Hub Dashboard

The dashboard provides an at-a-glance estate health overview with summary cards showing total projects, contracts, pending imports, and migration status. Recent import activity and pending approvals are surfaced so the estate architect can quickly see what needs attention.

Who Is Hub Mode For?

Lead Architects
Responsible for cross-cutting concerns, technology standards, and ensuring project teams align with the estate architecture.
Enterprise Architects
Need visibility across the full portfolio of projects, with contract governance and taxonomy-driven views of the estate.
Architecture Governance Boards
Require approval workflows, impact reports, and audit trails for architectural changes that cross project boundaries.