Knowledge / Architecture
How is Enterprise Reality structured and bounded?
Architecture translates governing meaning into bounded responsibility. It explains how Enterprise Reality can be represented, understood and acted upon without allowing any one system, graph, database or AI component to stand in for the reality it serves.
Sequence
Architecture follows governing meaning
Canon answers what governs Enterprise Reality. Architecture answers how that governing meaning is carried into responsibilities and boundaries. It remains subordinate to applicable constitutional authority and cannot redefine it.
- Canon
- Architecture
- Engineering
Bounded responsibilities
A progression, not interchangeable products
Each responsibility exists for a reason. A later capability may consume what an earlier one makes available, but must not silently absorb its responsibility or authority.
01
Repository
Holds governed source material without becoming the enterprise it describes.
02
Metadata
Interprets publication identity, governance and relationships consistently.
03
Corpus
Provides a coherent governed runtime representation of knowledge.
04
Graph
Projects governed relationships so context can be navigated.
05
Enterprise Reality Graph
Represents those relationships without becoming Enterprise Reality itself.
06
Reasoning
Evaluates governed evidence and relationships to justify conclusions.
07
Automation
Coordinates only actions that are permitted within established authority.
08
AI Runtime
Advises, explains and assists downstream of governed understanding.
Reality and representation
A representation can describe reality without becoming it
Systems, repositories, metadata, graphs and generated artefacts are representations or observations of Enterprise Reality. They make aspects of it available for governed understanding; they do not replace the enterprise reality they represent.
Enterprise Reality is not reducible to any one technical representation.
Identity
Identity must survive representation change
Stable identity precedes system representation. Applications may be replaced, records may be reorganised and representations may evolve, but the enterprise identity they concern must remain intelligible across those changes. No application owns that identity merely by holding one representation of it.
Governed knowledge
Source, interpretation and runtime representation stay distinct
Governed knowledge moves through related responsibilities without confusing their ownership. The Corpus is not the source repository, and the Metadata Engine is not a generic catalogue.
Repository
Responsibility: Governed source material
Boundary: Not Enterprise Reality
Metadata interpretation
Responsibility: Publication identity, governance and relationships
Boundary: Not a generic metadata catalogue
Enterprise Corpus
Responsibility: Governed runtime representation of knowledge
Boundary: Not the source repository or a data lake
Relationships
The graph represents relationships
The Knowledge Graph Engine projects governed relationships. The Enterprise Reality Graph makes those relationships navigable as a representation; it does not itself reason, and it is not Enterprise Reality itself.
Relationships before reasoning.
Reasoning
Justification remains answerable to evidence
Reasoning consumes governed representations and evidence to produce justified conclusions where authority permits. It must remain traceable and explainable: insufficient evidence is a legitimate outcome, conflicting evidence may remain visible, and reasoning does not invent evidence.
Action boundary
A conclusion is not permission
Automation consumes governed knowledge and reasoning within authority boundaries. It coordinates permitted action; it does not acquire enterprise authority simply because a conclusion has been justified.
- Reasoning
- Justified conclusion
- Authority
- Permitted action
AI boundary
AI is advisory and downstream
AI belongs after governed relationships, reasoning and automation. It can support explanation, recommendation and assistance, but it does not own canonical knowledge, reasoning authority, decisions, approvals or operational execution.
Enterprise Reality is authoritative. AI is advisory.
Human experience
Platform and Explorer have different responsibilities
The Platform makes Enterprise Reality executable. Explorer makes it understandable to people. Explorer consumes Platform capability for human investigation; it does not define Enterprise Reality.
Platform → governed Enterprise Reality → Explorer → human investigation
Architecture and maturity
Structure does not imply release standing
Architecture can define a responsibility without asserting that its implementation is planned, in development, implemented or released. Release standing follows a distinct path through engineering, programme governance and release certification.
Implemented is not the same as Released.
Public architectural principles
What this architecture protects
- Truth before techniqueTechnical choices must serve the reality and governing meaning they represent; they do not define either.
- Architecture before implementationResponsibilities and separations are made clear before particular implementation choices are considered.
Continue through Knowledge
Return to the public record
Architecture explains bounded structure. Releases is the separate verification domain for lifecycle standing; structure alone does not establish maturity or certification.