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: 17 September 2026

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

Canonical architecture: Enterprise Intelligence Architecture

Enterprise vocabulary: Enterprise Intelligence Architecture — Canonical Definitions

Graph participation reference: Enterprise Knowledge Graph Pattern

Cross-cutting control reference: The Enterprise Control Plane

Source baseline: Reference Architecture Version 1.0; original Last Updated July 2026, retained as source-baseline history.

Web clarification: 17 September 2026 — Specification and result evidence, source and projection-producer accountability, bounded Graph Qualification, interchange and practical reversibility, synchronisation evidence and runtime/control boundaries clarified. An at-a-glance explanation is added. The lifecycle illustration is retained with an explicit scope paragraph; the separate architecture diagram is replaced with a labelled projection responsibility view. Existing principle identifiers, source classification and specification/preservation lists are retained.

Source scope: This is Arqua's implementation pattern for controlled projection of selected enterprise-product representations into graph targets. It describes preservation and assessment responsibilities; it does not confer source authority, publication standing, runtime reliance or permission to mutate a source. The Projection Specification is a governed specification artefact, distinct from a projected graph and evidence of a projection run.

Executive summary

Within this pattern, the Enterprise Knowledge Graph is a governed projection of enterprise products rather than a replacement owner of their operational state. Projections should be maintained against declared sources and update requirements; the pattern does not prescribe a universal refresh interval.

The projection is required to preserve, within its declared scope:

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

Synchronisation is an operating objective requiring evidence of source versions, projection updates and target state. It is not a property established by this pattern or a claim that a graph contains complete, current 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 carry representations under the authority and accountability of their recognised enterprise sources for a declared scope. They do not create the underlying authority or confer accepted standing on every downstream interpretation.

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.

Source owners remain accountable for their own published representations within scope. Projection producers remain accountable for their mapping rules and transformations. New derived claims must retain their inputs, derivation, producer, evidence and standing rather than silently inherit source endorsement; institutional acceptance remains with the appropriate enterprise governance process.

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.

Reversibility is bounded by the declared mappings and retained evidence. It does not promise a lossless round trip, reconstruction of missing information or permission to apply graph changes back to an operational source. Historical reconstruction and a consequence-bearing write-back are different operations with separate authority and controls.

Enterprise Projection Lifecycle

This is a responsibility and dependency illustration, not a prescribed service deployment or an automatic successful admission sequence. Projection Specification is an artefact used by the projection activity. Preparing or staging a representation does not grant publication standing; Enterprise Intelligence consumption remains subject to applicable participation, access and current-use qualification.

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 assesses whether the projected representation meets the applicable identity, semantic, provenance, quality and publication-rule requirements for a declared projection and target. Its result must identify the assessed versions, criteria, scope, evidence and limitations; missing evidence is not a successful check by default.

This assessment neither grants Publication Standing nor qualifies every future use. Publication Authority retains the participation decision. Runtime Context Assembly separately forms and qualifies purpose-specific understanding, and consequence-bearing actions remain subject to applicable execution controls.

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

Eligible published graph representations may contribute to RCA under an active Intent Scope. RCA forms Candidate Operational Understanding and records an Assembly Manifest, then performs Context Qualification and records its outcome in a Qualified Context Manifest. Qualified Operational Understanding results only where reliance is supported for that use.

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.

The specification describes the intended projection; the produced representation and its assessment evidence are separate records. A particular result must remain traceable to the inputs and versions actually used, the applicable specification version, target, accountable producer and assessment scope. Approving a specification does not prove that a run followed it. The nine concerns above are not a complete normative contract schema or evidence that a reusable implementation has been supplied.

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.

Technical identity mappings must preserve the relevant source scope and namespace. A matching identifier string does not by itself establish that two representations denote the same enterprise subject; merges, splits and equivalence claims require an explicit governed basis rather than being inferred from a successful conversion.

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.

Mappings must make their direction, applicable versions, preserved distinctions and known limitations explicit. Unsupported distinctions, ambiguity or information loss must not be silently presented as equivalent meaning. These requirements do not claim that every graph target can express every source meaning without loss.

Provenance

Every projected node and relationship should preserve:

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

A projection lacking the provenance required for its declared participation or reliance cannot be treated as satisfying that requirement merely because it is accessible. Provenance supports assessment; its presence alone does not establish truth, completeness, current suitability or safety.

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

Source change and projection currency

Source updates, projection runs, target availability and consumer uptake are different events. The relevant source version, projection specification, result and assessment evidence must remain distinguishable. A changed source or withdrawal notice does not prove that every projection or consumer has applied the change.

Current participation and reliance must be assessed against applicable versions, temporal scope, conditions and observed update evidence. An earlier assessment does not automatically cover a changed source, mapping or target. Missing propagation evidence or incomplete coverage must remain visible; historical records retain their previous meaning and standing rather than being silently rewritten as current truth.

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.

Interchange between targets must retain the relevant source and specification references, semantic mappings, provenance and conditions of use, with transformation losses visible. Successful serialisation or import does not prove equivalent meaning or inference behaviour. A target-to-target copy does not acquire new publication standing, inherited source endorsement or unrestricted rights by changing format.

Runtime Context Assembly

Graph projections may supply candidate relationships through eligible Published Enterprise Products for a declared Operational Intent and active Intent Scope. Projection determines the representation supplied; it does not determine the consumer's purpose or establish sufficiency for reliance.

RCA forms Candidate Operational Understanding and an Assembly Manifest, then performs Context Qualification and records the result in a Qualified Context Manifest. Graph Qualification provides evidence about the projection, not a substitute for this current-use assessment. Qualified Operational Understanding is produced only where reliance is supported; neither qualification result authorises execution.

Graph technologies may support traversal and assembly functions without taking over RCA's architectural responsibility. Graph-backed input is optional and can be combined with other eligible Published Enterprise Products; this pattern does not require every context to use a graph.

Enterprise Control Plane

Projection produces representations under accountable specifications. The Enterprise Control Plane supports cross-cutting identity, authority, semantic, policy, lineage and evidence controls through projection, publication and consumption without taking over the producer's responsibility or the publication decision.

Enterprise Participation and Publication Authority retain governed-entry responsibilities. RCA retains formation and Context Qualification; EAA retains the separate consequence-boundary evaluation. The control plane coordinates these relationships rather than becoming an admission authority, mandatory central orchestrator or operational executor.

Where projection, publication, source write-back or another operation itself binds consequence, applicable controls belong at that operation's boundary. A specification, reference architecture or control record does not prove that the required control operated.

Projection responsibility view

Accountable sources: Governed enterprise products provide scoped representations with their source authority, ownership and applicable participation conditions.

Specification and production: The governed Projection Specification directs identity, relationship and semantic mappings. Projection producers create identifiable results with traceable inputs, versions and transformation evidence; the specification is not the runtime result.

Assessment and participation: Graph Qualification assesses the specified projection and target. Publication standing, interface access and resulting graph-oriented offerings retain their separate governance. A successful assessment is not an automatic permission for every consumer.

Purpose-specific use and change: Eligible published graph representations may contribute to RCA formation and conditional qualification under an active Intent Scope. Cross-cutting controls and change evidence preserve the relevant boundaries; proposed consequence-bearing action remains separately governed. These are responsibility relationships, not one compulsory platform or guaranteed successful pipeline.

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.

SMF non-collapse constraint

This pattern inherits the accepted System Model Foundation Non-Collapse and Typed Relationship Constraints (NC-01 through NC-06). Projection, mapping, target interchange or graph connectivity does not by itself establish semantic equivalence, common boundary membership, transferred source authority, accepted standing or suitability for a runtime Intent Scope. Any such stronger effect requires the applicable governed relationship/mapping type, scope, time, authority/standing, evidence and rules. Projection implementations may use equivalence closure or DSU-style techniques only where those semantics are explicitly declared and valid; arbitrary projected graph edges must not be unioned as though connection meant membership.

Representation foundation: System Model Foundation.

Cross references

This pattern should be read with:

• Enterprise Knowledge Graph Pattern
• Semantic Projection Pattern
• Runtime Context Assembly
• 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

This is a reading path, not a mandatory implementation order or runtime pipeline. The Future specialisations section retains the source's stated plans; this increment does not verify or promote unreviewed future papers as published specifications.

Validation

Before publishing, verify:

• Projection is consistently described as deriving from authoritative enterprise products.
• Governed graph projections are not treated as replacement owners or sources of institutional authority for the projected operational state.
• 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.
• Intended specification, actual production, projection assessment and current-use qualification remain distinguishable and traceable.
• Source responsibility, projection-producer accountability and derived-claim standing remain explicit; projection does not confer publication or execution authority.
• Synchronisation, withdrawal propagation and preservation claims distinguish requirements from observed operating evidence and its limitations.
• Interchange and practical reversibility disclose mapping scope and information loss without claiming universal equivalence, lossless round trips or write-back permission.

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 describes Arqua's implementation pattern for producing and maintaining governed graph representations from enterprise products.

It sets requirements for keeping projections aligned with declared source representations; actual synchronisation, semantic preservation and current suitability require scoped implementation and operating evidence.

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.