Reference Architectures

This section groups platform-specific reference architectures separately from constitutional theory.

Reference architectures should be read as constitutional implementations: examples of how constitutional responsibilities may be interpreted in particular technology environments. They do not define the theory and should not be treated as the source of constitutional principles.

Platform reference groups

Microsoft Fabric

Reference materials for interpreting constitutional responsibilities in Microsoft Fabric environments.

AWS

Reference materials for interpreting constitutional responsibilities in AWS environments.

Databricks

Reference materials for interpreting constitutional responsibilities in Databricks environments.

Google Cloud

Reference materials for interpreting constitutional responsibilities in Google Cloud environments.

Neo4j

Reference materials for graph-based implementation contexts, including governed meaning, relationship structure, provenance, and lineage.

Related entry point:

• Neo4j GraphTalk Melbourne — Semantic Intelligence in Motion

Editorial interpretation

Reference architectures appear after applied architectures because they are more specific. They demonstrate how constitutional understanding may be expressed in platform contexts without converting platform guidance into constitutional theory.