Federated Intent Graph
A unified intent graph assembled from all imported project artefacts in the Architecture Hub, with per-node provenance tracking and cross-project transitive queries.
How the Federated Graph Is Built
The federated graph is a separate graph instance maintained by the hub, independent of any project-level graph. It is assembled incrementally as artefacts are imported.
Node extraction reuses the same parsing logic as project-level graphs - over 30 extraction methods cover all content types. This means the federated graph understands entity relationships, projection dependencies, API endpoints, schema references, and every other typed relationship that exists at the project level.
Re-Import and Graph Updates
When a project re-exports and the hub re-imports, the federated graph handles the update cleanly. All nodes from the previous import of that project are removed first, then the new nodes are inserted. Any cross-project edges that referenced the removed nodes are flagged as broken, surfacing potential integration issues that need attention.
Cross-Project Queries
The federated graph supports the same query operations as project-level graphs, but across project boundaries. This is what makes estate-level impact analysis possible.
Cross-Project Edge Types
The federated graph introduces edge types that only exist at the estate level, representing the governed relationships between projects.
| Edge Type | Meaning |
|---|---|
| consumes-contract | A project consumes a contract produced by another project |
| produces-contract | A project produces a contract that other projects consume |
| governed-by | A construct is governed by a hub-level policy or approval |
Relationship to Other Hub Features
The federated graph is the foundation that other hub features build on. The taxonomy view uses it to discover which entities belong to which taxonomy terms. The mesh view uses it alongside the contract registry to show the data product network. Estate impact analysis traverses it to compute blast radius. Without the federated graph, the hub would only see individual artefacts in isolation - with it, the hub sees the connections between them.