Graph Projection and Interchange Pattern

A Reference Architecture for Projecting Authoritative Enterprise Products into Governed Graph Representations

Category: Enterprise Implementation Patterns

Status: Reference Architecture Version 1.0

Author: Arqua

Classification: Public

Last Updated: July 2026

Architectural question: How do authoritative enterprise products continuously become governed graph representations without making graphs primary enterprise systems?

Executive summary

Enterprise Knowledge Graphs should not become enterprise systems of record.

They should be continuously projected from authoritative enterprise products.

Projection preserves:

• enterprise ownership
• semantic integrity
• provenance
• authority
• temporal consistency
• platform independence

The graph remains synchronised with enterprise reality without becoming enterprise truth.

This pattern explains controlled enterprise projection. It does not describe graph modelling. It defines how authoritative enterprise products become governed graph representations while preserving constitutional responsibilities, enterprise ownership and platform independence.

Purpose

The Graph Projection and Interchange Pattern defines:

• how enterprise products become graph representations
• how projections evolve
• how identity is preserved
• how semantic consistency is maintained
• how provenance is retained
• how revisions occur
• how multiple graph technologies remain aligned

The pattern establishes Projection Specification as the governed enterprise artefact that controls how source-aligned enterprise products participate in graph representations.

Architectural principles

GPI-1 — Enterprise products remain authoritative

Enterprise products remain the source of authority for enterprise state, identity, meaning, provenance and stewardship.

Graph projection does not transfer authority from source products into a graph platform.

GPI-2 — Graphs are projections

Graphs are governed projections of enterprise products.

They expose relationships, identities, meaning and evidence for graph participation without becoming primary enterprise systems.

GPI-3 — Projection never changes enterprise ownership

Projection never changes enterprise ownership.

The originating product, domain or governance structure remains accountable for the authoritative representation.

GPI-4 — Identity remains stable across projections

Identity remains stable across projections.

Projected graph representations must preserve enterprise identifiers, relationship identity and revision history so that graph participation remains traceable to enterprise reality.

GPI-5 — Semantic meaning is preserved during projection

Semantic meaning is preserved during projection.

Projection maps enterprise meaning into graph representations without allowing graph implementation choices to redefine enterprise semantics.

GPI-6 — Provenance accompanies every projected representation

Provenance accompanies every projected representation.

Every node, relationship, claim or graph artefact should remain traceable to its originating product, projection version, authority and revision history.

GPI-7 — Multiple graph technologies may coexist

Multiple graph technologies may coexist.

RDF graphs, Property Graphs, analytical graph projections and operational context graphs may implement different graph targets while remaining aligned through governed Projection Specifications.

GPI-8 — Projection remains reversible wherever practical

Projection remains reversible wherever practical.

Projected graph representations should retain sufficient identity, provenance, semantic mapping and transformation history to support reconciliation, audit, replay and controlled revision.

Enterprise Projection Lifecycle

Authoritative Enterprise Product
↓
Projection Specification
↓
Identity Mapping
↓
Relationship Mapping
↓
Semantic Mapping
↓
Graph Projection
↓
Graph Qualification
↓
Enterprise Knowledge Graph
↓
Runtime Context Assembly

Authoritative Enterprise Product

The lifecycle begins with a governed enterprise product that preserves authoritative enterprise representation, ownership, meaning, provenance and quality.

Projection Specification

The Projection Specification defines how selected entities, relationships, identities and semantic meanings are projected into graph representations.

Identity Mapping

Identity Mapping preserves enterprise identifiers, relationship identity, authority, temporal validity and revision history across projection boundaries.

Relationship Mapping

Relationship Mapping defines how enterprise relationships are represented in the graph while remaining traceable to authoritative products.

Semantic Mapping

Semantic Mapping preserves enterprise meaning, concept definitions, glossary terms, ontology alignment and relationship meaning during projection.

Graph Projection

Graph Projection materialises the controlled representation into one or more graph targets without changing enterprise ownership or authority.

Graph Qualification

Graph Qualification verifies that projected representations preserve identity, semantics, provenance, quality and publication rules before participation in the Enterprise Knowledge Graph.

Enterprise Knowledge Graph

The Enterprise Knowledge Graph exposes governed relationships derived from authoritative enterprise products. It remains a projection, not enterprise truth.

Runtime Context Assembly

Runtime Context Assembly consumes governed graph projections and determines operational relevance for a defined purpose, policy frame and execution context.

Projection Specification

A Projection Specification defines:

• source products
• participating entities
• relationship mappings
• semantic mappings
• identity mappings
• provenance rules
• transformation rules
• quality rules
• publication rules

Projection Specifications become governed enterprise artefacts.

They define how enterprise products participate in graph representations. They should be versioned, reviewed, owned, tested and governed in the same way as other enterprise architectural artefacts that influence operational understanding.

Identity Preservation

Projection must preserve:

• enterprise identifiers
• relationship identity
• authority
• temporal validity
• revision history

Graphs must not invent new enterprise identities.

Where graph-specific identifiers are required, they should remain technical identifiers that resolve back to enterprise identity. They should not become substitutes for enterprise identity, ownership or authority.

Relationship Projection

Projection may represent relationships including:

• ownership
• dependency
• authority
• composition
• participation
• evidence
• policy
• semantic relationships

Relationships remain traceable to authoritative products.

Relationship Projection should preserve the source product, source identity, relationship meaning, authority, temporal validity, evidence basis and revision history. A relationship represented in the graph remains a projected enterprise relationship rather than a new graph-owned fact.

Semantic Preservation

Semantic projection maps enterprise meaning into graph representations.

Semantic authority remains independent of graph implementation.

Projection must preserve:

• enterprise ontology
• business glossary
• concept definitions
• relationship meaning

Graph technologies may represent meaning differently. The Projection Specification defines how enterprise meaning is carried into each target representation without allowing the target technology to redefine the enterprise concept.

Provenance

Every projected node and relationship should preserve:

• originating product
• projection version
• source identity
• authority
• timestamp
• projection method
• revision history

Without provenance the graph cannot participate safely in Enterprise Intelligence.

Provenance allows projected graph representations to be traced, explained, challenged, revised and withdrawn when source products change or projection rules are updated.

Multiple Graph Targets

Projection may target:

• RDF graphs
• Property graphs
• analytical graph projections
• operational context graphs

The Projection Specification remains independent of graph technology.

Different graph targets may support different access patterns, reasoning styles, performance characteristics or operational uses. The architectural requirement is that each target remains traceable to the same governed projection rules and authoritative enterprise products.

Runtime Context Assembly

Runtime Context Assembly consumes graph projections.

Projection determines representation.

Runtime Context determines operational relevance.

Graphs do not perform Runtime Context Assembly. They provide governed graph representations that Runtime Context Assembly may consume, qualify and combine with other accepted enterprise representations for a defined operational purpose.

Enterprise Control Plane

Projection contributes representations.

The Enterprise Control Plane coordinates runtime participation.

Projection remains independent of runtime orchestration.

The Graph Projection and Interchange Pattern ensures that graph representations are governed, traceable and semantically consistent before they participate in runtime services. The Enterprise Control Plane determines how those representations participate in runtime coordination, authority resolution, context qualification and enterprise operation.

Architecture diagram

The diagram shows projection as a controlled enterprise process.

Authoritative Enterprise Products remain the source of enterprise state. Projection Specifications govern how identity, semantics and relationships become graph representations. Graph Qualification verifies that the projection is fit to participate in the Enterprise Knowledge Graph. Runtime Context Assembly consumes the resulting graph representations only where they are relevant to a defined operational context.

Future specialisations

Future implementation patterns may specialise this pattern into:

• RDF Semantic Graph Pattern — Coming Soon
• Property Graph Operational Context Pattern — Coming Soon
• Graph Federation Pattern — Coming Soon
• Graph Synchronisation Pattern — Coming Soon

These specialisations should extend the projection pattern without changing the constitutional architecture or making any graph technology the source of enterprise truth.

Non-goals

This pattern does not:

• replace enterprise products
• define graph technology
• require RDF
• require Property Graphs
• replace semantic governance
• replace Runtime Context Assembly
• centralise enterprise ownership

It defines controlled enterprise projection, not graph modelling, graph platform selection or graph database implementation.

Cross references

This pattern should be read with:

• Enterprise Knowledge Graph Pattern
• Semantic Projection Pattern
• No access
• Source-Aligned Product Pattern
• Enterprise Registry
• Enterprise Representation Intelligence
• The Enterprise Control Plane
• Qualified Operational Understanding

These references define the constitutional and implementation context for governed graph projection.

Pattern navigation

Enterprise Knowledge Graph Pattern
↓
Graph Projection and Interchange Pattern
↓
RDF Semantic Graph Pattern
↓
Property Graph Operational Context Pattern

Validation

Before publishing, verify:

• Projection is consistently described as deriving from authoritative enterprise products.
• Graphs are never described as enterprise systems of record.
• Projection Specifications become governed enterprise artefacts.
• Identity, semantics and provenance remain preserved.
• Runtime Context Assembly consumes graph representations but is not replaced by them.
• Future RDF and Property Graph papers naturally specialise this pattern.

Boundary statement

This page is an Enterprise Implementation Pattern. It is not a Constitutional Architecture paper.

It does not define graph modelling, RDF, Property Graphs, graph databases or any graph platform as the architecture.

It does not modify the authority of Source-Aligned Enterprise Products, Enterprise Representation Intelligence, Institutional Memory, Runtime Context Assembly, Enterprise Coordination or the Enterprise Control Plane.

It does not assert that graph projection provides legal compliance, regulatory assurance, operational assurance or automated decision authority.

Human and organisational accountability remains with the institution applying the pattern.

Conclusion

The Graph Projection and Interchange Pattern establishes the canonical implementation pattern for how enterprise products continuously become governed graph representations.

It keeps Enterprise Knowledge Graphs synchronised with enterprise reality without making them enterprise truth.

By preserving ownership, identity, semantic integrity, provenance and platform independence, the pattern allows RDF, Property Graph and other graph implementations to specialise graph participation without changing the constitutional architecture.