Ivory & Co.
AEA by Ivory & Co.StandardsKnowledge & ResearchImplementationCertificationIvory & Co.
Ivory & Co./Standards/Publication 01

AEA by Ivory & Co. · AEA DesignThe architecture of the discipline itself.

AEA Design is the result of applying Adaptive Enterprise Architecture to itself. It records the design properties and relationships the discipline needs in order to work as a coherent system.

Adaptive Enterprise Architecture grew from a difficult question: how do we describe an entire business without reducing it to its organisational structure, operating model, processes or technology?

Businesses are complex systems of interconnected decisions, capabilities, relationships, activities and conditions. They change continually, often in ways that cross the boundaries of any one function or organisation. AEA provides an architectural basis for understanding that complexity.

A discipline intended to describe enterprises must also be able to describe itself. AEA Design examines the discipline as an architectural subject. It adds no architecture above the Architecture Standards and originates no doctrine of its own. Its authority is derived from the standards, and it describes the design that emerges when AEA is examined through its own foundations.

Why this publication matters

The integrity of a discipline cannot rest on the knowledge of its creator or the interpretation of its practitioners. Its foundations have to stay coherent as they are applied, examined, challenged and developed.

AEA Design sets out how the discipline maintains coherence across its architectural concerns, how those concerns relate, and why the architecture must stay applicable as enterprises grow and change. It also recognises that a modern enterprise may be more complex than any individual can understand unaided. A useful discipline makes that complexity legible without asking the enterprise to become simple.

Publication record

Title
Adaptive Enterprise Architecture — AEA Design
Version
1.0.0
Date
11 September 2026
Status
Published — governance-released baseline
Derivation
Application of the eleven AEA Architecture Standards to AEA itself
Steward
Ivory & Co.
Integrity
SHA-256 169079f74e7ff452eb25eb8c8b6560794b2a628c9071049fc017bcbdb2907a9c
Related
Architecture Set Standard · eleven Architecture Standards · Governance Standards
Download PDF© 2026 Ivory & Co. · Licence terms to be confirmed
·Full publication

AEA Design v1.0.0

The complete text, in its original section structure and governed wording.

Adaptive Enterprise Architecture

AEA Design

Version: 1.0.0 — Published
Status: Published — governance-released baseline
Date: 11 September 2026
Derivation: Application of the eleven AEA Architecture Standards to AEA itself


1. Purpose

AEA Design defines the design of Adaptive Enterprise Architecture itself.

It is established by applying the eleven AEA Architecture Standards to AEA as the subject being architected.

The AEA Standards remain the architectural authority. AEA Design does not create an additional architecture above the Standards, nor does it independently originate AEA doctrine. It records the design that results when AEA is subjected to its own architectural requirements.

AEA is designed through the application of AEA to itself.

AEA Design is intentionally bounded. It defines the properties, relationships and requirements necessary for AEA to operate as a coherent architecture. It does not create a mirror estate of eleven additional Standards about the Standards.

Where self-application exposes a deficiency, ambiguity or missing proposition in an existing Standard or in the Architecture Set, that finding does not become doctrine merely by appearing within AEA Design. It identifies something that must be resolved through the appropriate development and governance of AEA.


1.1 Provenance and Point of View

AEA did not originate as a new Enterprise Architecture method designed to help technology teams understand the business.

It emerged from a strategist's need to understand business as a connected whole: how value, direction, capability, relationships, work, participation, enablement, expression, actuality, possibility, understanding and reliance connect to form the business and shape the way it operates.

Enterprise Architecture and Business Architecture are established disciplines with substantial bodies of prior work. AEA does not depend upon claiming that those disciplines are new, nor upon claiming that the individual subjects contained within AEA have never been considered before.

AEA activates a connected, whole-of-business way of thinking about what a business is, how its architectural dimensions interlock, and how that architecture can remain legible as the business changes and grows.

AEA is a strategist's architecture of business. Its use is not confined to an architecture function or technology organisation. It is intended to be usable across Boards, executives, strategists, operators, finance, people, technology, transformation, specialist disciplines, human participants and machine participants wherever a coherent understanding of the business is required.


2. Design Basis

AEA comprises eleven Architecture Standards:

Directional — Intent
Domain — Scope
Ecosystem — Interconnectedness
Environment — Enablement
Execution — Instructions
Expression — Individuality
Intelligence — Understanding
Possibility — Optionality
Reality — Actuality
Trust — Reliance
Workforce — Participation

The eleven Standards constitute a flat Architecture Set. No Standard is inherently subordinate to another.

Each Standard owns a distinct architectural concern while operating as part of the architecture as a whole.

AEA Design must therefore preserve both the integrity of each individual Standard and the integrity of their collective composition.


3. Whole-of-AEA Design Properties

3.1 Standard Integrity

Each AEA Standard must remain internally coherent within its architectural ownership, definitions, boundaries and rules.

A Standard must be capable of standing as a coherent articulation of the architecture it owns.

Internal coherence, however, is not sufficient on its own.

3.2 Set Integrity

The AEA Standards must remain collectively coherent as a single Architecture Set.

A proposition or change may be valid within one Standard while creating collision, contradiction or unintended consequence elsewhere in AEA.

AEA must therefore be designed, developed and governed as a system of Standards, not as eleven independently maintained documents.

A material change to one Standard must be capable of being understood in relation to the Architecture Set as a whole.

3.3 Legibility of Complexity

AEA must enable the architecture of a business to remain legible as its complexity increases.

AEA does not exist to eliminate complexity.

It provides sufficient architectural separation and structure for complexity to be understood without requiring the business itself to remain simple.

3.4 Cognitive Independence

The legibility of a business through AEA must not depend upon its architecture fitting within the cognitive capacity of any individual.

AEA must remain structurally applicable from an idea held by one person through to a business whose architecture exceeds what any individual can comprehend unaided.

Growth may increase the amount, depth and interconnectedness of architecture required.

It must not require an entirely different architecture of business simply because the business has become larger.

3.5 Architectural Sufficiency

AEA must provide sufficient architectural coverage for the architecture of business.

Every architectural proposition necessary to describe the business must be capable of having an appropriate architectural home.

Where a necessary proposition cannot coherently reside within the existing Architecture Set, this is evidence of a potential deficiency in AEA.

It is not permission to force the proposition into an inappropriate architecture.

The sufficiency of AEA therefore remains continuously testable.

3.6 Singular Architectural Ownership

Every architectural proposition must have an unambiguous architectural home.

An architecture may consume, measure, interpret, render or rely upon a proposition owned elsewhere without acquiring ownership of that proposition.

Cross-architecture use must not create duplication, semantic collision or competing ownership.

3.7 Separation Without Fragmentation

AEA must preserve precision of architectural separation without fragmenting the business being architected.

Architectural distinctions exist to protect meaning.

Intent is not Actuality.
Actor is not Role.
Capability is not Instruction.
Understanding is not Reliance.
Authority is not Trust.

These distinctions must make the business more legible without turning it into eleven disconnected representations.

3.8 Structural Interoperability

AEA architectures must remain independently precise while being structurally interoperable with the other architectures with which they interact.

Architectural boundaries protect meaning.

They must not prevent coherent composition.

3.9 Concurrent Architecture

AEA architectures must remain capable of concurrent operation.

Sequence may be introduced when AEA is traversed, analysed, applied, communicated or implemented.

Such sequence does not establish architectural hierarchy or precedence unless that relationship is itself established by AEA.

3.10 Controlled Extensibility

AEA must remain capable of extension and continued development without allowing change to create uncontrolled duplication, semantic collision, conceptual accumulation or architectural fragmentation.

Adaptation does not mean unrestricted addition.

AEA must be capable of refinement, extension, correction, replacement and retirement while preserving the integrity of the architecture.

3.11 Adaptive Authority

AEA must remain capable of adapting where evidence establishes that an existing architectural proposition is no longer sufficient.

Current AEA may be authoritative without being immutable.

Authority does not require infallibility.

Expression: AEA is right until it isn't.

3.12 Legible Certainty and Uncertainty

AEA must make the state of its architectural propositions sufficiently explicit to distinguish what is established from what is uncertain, proposed, questioned, superseded or unknown.

AEA must not manufacture certainty merely to create the appearance of completeness.

3.13 Implementation Independence

AEA must remain independent of the particular humans, organisations, agents, models, runtimes and technologies through which it is maintained, applied or consumed.

A change in fulfilment does not inherently require a change in the underlying architecture.

3.14 Canonical Integrity

Application, implementation, extension, interpretation or commercial use of AEA must not independently alter canonical AEA.

Canonical AEA changes through the mechanisms authorised to change canonical AEA.

The continued development of AEA itself is therefore distinct from the creation of things from AEA.


4. Directional Architecture — Intent

Directional Architecture establishes why AEA exists, what it is intended to become, the strategic scope within which it will develop, the choices that shape that development, the trade-offs those choices create, and the guardrails that must constrain movement.

This is the head of AEA Design.

4.1 Purpose

AEA exists to make the architecture of business legible.

Its purpose is not to make business simple. It is to enable the complexity of business to remain intelligible as scale, interconnection, participation, technology and operating conditions increase.

AEA exists to preserve the legibility of business complexity.

This is what allows AEA to remain useful from an idea held by one person through to a business whose architecture no longer fits inside any one person's head.

4.2 Vision

AEA is intended to become the defining architecture through which business is understood and designed across scale.

Its envisioned future is one in which the architecture of business can remain coherent and legible regardless of:

  • business size;
  • industry;
  • geography;
  • operating model;
  • organisational form;
  • technology;
  • human or non-human participation;
  • or the degree of complexity through which the business operates.

AEA is not intended to become a framework only for large enterprises, mature organisations, technology functions or traditional enterprise architects.

It is intended to remain applicable from the earliest formation of a business through to the largest and most complex businesses in the world.

4.3 Ultimate Outcome

AEA is the world's number one trusted authority on the architecture of business.

Trusted authority is not defined by citation, academic acceptance or institutional recognition alone.

AEA is intended to become the reference point against which serious thinking, design and operation of business is tested.

4.4 Commercial Outcome

AEA is also intended to be exceptionally commercially successful.

Its intellectual authority is not pursued as an end that sits apart from economic consequence.

The business built around AEA is intended to capture substantial commercial value from the application of AEA.

AEA is intended to combine category authority with category-leading commercial success.

The Standards themselves do not need to become commercial products in order to create commercial value.

Commercial value is realised through their application.

4.5 Directional Intent

AEA intends to:

  • establish AEA as the leading standard for a connected, whole-of-business architectural view;
  • set the standards through which that category is understood;
  • become the most trusted authority within that category;
  • remain structurally valid across the full scale of business development;
  • remain applicable as forms of participation and intelligence evolve;
  • demonstrate its value through actual application rather than assertion alone;
  • create consequential adoption among people and organisations able to produce meaningful business outcomes;
  • and support a commercial ecosystem capable of creating and capturing substantial economic value from the application of AEA.

4.6 Strategic Scope

AEA's strategic scope is the architecture of business.

AEA is concerned with the architecture required to make business legible as a whole.

Its scope is deliberately broader than a technology architecture, organisational design method, process methodology, business architecture technique or operating-model framework.

AEA does not seek to become every specialist discipline that may contribute to business design.

Instead, it provides the architectural structure within which specialist disciplines, bodies of knowledge and applied methods can be located, related and composed without AEA needing to absorb them.

AEA's scope therefore includes the architecture necessary to describe business from its earliest viable conception through increasing levels of scale and complexity.

4.7 Strategic Choices

AEA makes the following current strategic choices.

Choice 1 — Business, not enterprise, is the subject

AEA claims authority over the architecture of business.

It does not rely on the term enterprise as a size category or inherit the assumptions attached to traditional Enterprise Architecture.

Choice 2 — Legibility over simplification

AEA will not reduce business complexity by collapsing unlike propositions into simpler but less truthful models.

It will preserve necessary distinctions so complexity remains legible.

Choice 3 — One architecture across scale

AEA will not create separate core architectures for small business, mid-market, enterprise, agentic business or future operating forms merely because scale or fulfilment changes.

Application depth may vary.

The underlying architecture should not need to be reinvented for each scale.

Choice 4 — Canonical architecture before commercial wrapper

Canonical AEA remains distinct from the products, services, methods, technologies and commercial wrappers built from it.

Commercialisation occurs through application and extension, not through audience-specific mutation of canonical AEA.

Choice 5 — Application as proof

AEA will not rely on theoretical elegance alone as the basis of authority.

AEA in Action will provide a proving ground through which AEA is applied, tested and evidenced against actual business.

Choice 6 — Adaptive, not immutable

AEA will remain open to the possibility that a current proposition is no longer sufficient.

Its authority is grounded in governed adaptability rather than claims of permanent correctness.

Choice 7 — Consequential adoption over adoption for prestige

AEA does not optimise for institutional adoption, academic recognition or ubiquity as ends in themselves.

It prioritises adoption that produces meaningful business consequence and strengthens both authority and economic value.

Choice 8 — Human and machine usability without semantic mutation

AEA must remain capable of being reliably used by humans and non-human systems without creating alternative meanings of canonical AEA.

Choice 9 — Standards as the source; application as the value engine

The Standards remain the authoritative architectural source.

The business model around AEA is built from applying the Standards, not from redefining them in order to create products.

4.8 Strategic Trade-offs

The choices above create deliberate trade-offs.

AEA accepts:

  • additional architectural precision in exchange for reduced conceptual ambiguity;
  • disciplined change control in exchange for unrestricted modification;
  • explicit separation of concepts in exchange for the superficial simplicity of collapsing them together;
  • slower promotion of untested ideas into canon in exchange for greater reliability of canonical AEA;
  • protection of canonical integrity in exchange for allowing every interpreter to redefine AEA freely;
  • and the need to prove commercial and business consequence in exchange for relying solely on intellectual prestige.

AEA does not treat these trade-offs as defects.

They are consequences of the position it intends to hold.

4.9 Values Guardrails

The following guardrails constrain how AEA may develop.

Guardrail 1 — Coherence before accumulation

AEA must not add concepts merely because they are useful or interesting.

New concepts must have an architectural home and must not destroy existing coherence.

Guardrail 2 — Truth before neatness

AEA must not manufacture certainty, completeness or alignment when uncertainty, contradiction or insufficiency actually exists.

Guardrail 3 — Evidence before assertion

Claims of effectiveness, authority or value should increasingly be supported by demonstrated application and consequence.

Guardrail 4 — Meaning before audience convenience

Canonical architectural meaning must not be changed merely to make AEA easier to sell, explain or package for a particular audience.

Guardrail 5 — Architecture before implementation

AEA must not allow current tooling, participants, organisational structures or operating models to become the definition of the underlying architecture.

Guardrail 6 — Adaptation without drift

AEA may evolve, but evolution must not become uncontrolled conceptual drift.

Guardrail 7 — Commercial success without canonical corruption

Commercial value may be created aggressively from AEA, but commercial pressure must not independently redefine canonical AEA.

Guardrail 8 — Consequence over prestige

Academic acceptance, industry recognition and institutional endorsement may strengthen AEA, but none substitutes for actual application and demonstrated consequence.

4.10 Coherence Boundaries

A proposed movement is directionally incoherent with AEA where it would:

  • make AEA specific to one size or class of business;
  • make the architecture dependent on one operating model;
  • make canonical AEA audience-specific;
  • allow commercial products to redefine canonical AEA;
  • make a current technology category foundational to the architecture where the underlying proposition is technology-independent;
  • substitute authority by assertion for evidence;
  • remove AEA's ability to adapt when evidence demonstrates insufficiency;
  • collapse distinct architectural propositions for convenience;
  • or compromise the ability to identify what constitutes current authoritative AEA.

Such a movement requires reconsideration of Directional Architecture before it can legitimately become part of AEA.

4.11 Course-Correction Principle

AEA's strategic direction is intended to remain durable while the path used to realise it can change.

Commercial mechanisms, technologies, publishing models, implementation methods, ecosystems, participants and enabling environments may all evolve.

They do not require Directional change unless the movement alters the fundamental category, ambition, scope, strategic choices or guardrails established here.


5. Domain Architecture — Scope

Domain Architecture establishes the business being architected, its value logic, the stable domain knowledge through which it performs its core function, and the conditions under which that domain structure remains sufficient.

5.1 Business Model

AEA itself is the canonical intellectual architecture. The business around AEA creates economic value by applying that architecture.

The Standards alone do not generate economic value. Economic value is realised through their application.

Application may generate value through consulting, implementation, software, licensing, certification, education, commercial interpretation and other models built from AEA.

The commercial mechanism may change without changing AEA's underlying domain knowledge.

5.2 Value Logic

AEA creates value by making the architecture of business legible and usable.

Architectural knowledge → application to business → increased legibility and design capability → business consequence → realised value.

Commercial value capture occurs downstream from application.

5.3 Domain Knowledge

The eleven AEA architectures constitute AEA's complete current domain knowledge structure.

Directional, Domain, Ecosystem, Environment, Execution, Expression, Intelligence, Possibility, Reality, Trust and Workforce are not merely document categories. Together they constitute the stable bodies of architectural knowledge through which AEA describes the architecture of business.

The eleven Standards are a flat set. Their collective completeness is a substantive architectural claim and must remain testable.

5.4 Domain Completeness and Evolution

AEA is currently designed on the position that the eleven architectures are sufficient to architect business as a whole.

AEA does not require structural expansion merely because its knowledge grows.

The knowledge, propositions, models and internal anatomy of each architecture may continue to develop while its architectural domain remains stable. Such development demonstrates the extensibility of the model rather than a change to its Domain structure.

For example, Execution Architecture may evolve the anatomy of an AEA Standard, its process models, evidence requirements, variants or other instructional knowledge. That evolution expands what AEA knows about Instructions; it does not create a different architectural domain.

A new useful idea is not a new architecture.
A new technology is not a new architecture.
A new business model is not a new architecture.
A cross-architecture proposition is not a new architecture.
A new application is not a new architecture.

A new architecture is warranted only where a necessary architectural phenomenon of business is established for which none of the existing eleven architectures provides a coherent home.

Accordingly:

Change within an architecture is evidence of adaptation. Change to the Architecture Set is evidence of potential architectural insufficiency.

The eleven are therefore expected to become richer over time without structural proliferation.

5.5 Architecture Set Relationship — Value Nucleus and Operating Ring

The eleven Standards remain a flat Architecture Set.

Within that flat set, AEA recognises two functional groupings.

Value Nucleus

The Value Nucleus comprises Directional, Domain, Ecosystem, Execution, Expression, Possibility and Reality.

Together these architectures describe the business's value proposition as a connected whole: where it is going; what business it is; the ecosystem through which value exists; how work is performed; how value and identity are expressed; what could become possible; and what is actually true.

Operating Ring

The Operating Ring comprises Intelligence, Workforce, Environment and Trust.

These architectures operate across the Value Nucleus through Understanding, Participation, Enablement and Reliance.

Value Nucleus and Operating Ring describe relationship and function within the Architecture Set. They do not create hierarchy, sequence or architectural precedence.

The eleven Standards remain peers. The grouping makes their interconnection more legible and is consistent with Domain Architecture's distinction between value and the capabilities that enable value.

5.6 Differentiation — The Interlocking Business Schematic

The individual subjects within AEA are not claimed as newly invented disciplines.

Strategy, capability, process, ecosystems, workforce, technology enablement, information and intelligence, current state, future possibility, expression and trust have all been considered in business practice and scholarship in different forms for many years.

AEA's differentiation is the precision with which those subjects are bounded and the way they interlock to form a complete business schematic.

No individual architecture needs to be revolutionary for the whole architecture to be different.

Each architecture provides a distinct piece of the business. Singular ownership protects the meaning of each piece. Structural interoperability allows the pieces to connect. Together, the eleven architectures form the interlocking puzzle through which the business becomes legible as a coherent whole.

The completeness of AEA is therefore a property of the connected Architecture Set, not a claim that every individual architectural subject is novel.

5.7 Value Contribution and Commercial Wrappers

An architecture does not need to generate standalone commercial value to justify its place in AEA. Its architectural necessity is determined by the knowledge required to make the business complete and legible.

It may nevertheless generate standalone commercial value.

A commercial wrapper may be created from one architecture, a combination of architectures, or the Architecture Set as a whole.

Commercial potential does not determine whether an architecture belongs in AEA, and commercial use does not transfer ownership of canonical AEA to the wrapper.

5.8 Domain Economics

AEA's economics distinguish creation and maintenance of canonical domain knowledge from commercial exploitation of its application.

Investment is required to maintain, test, develop, govern and enable the canonical architecture.

Return may be generated through applications and extensions based upon one architecture, multiple architectures or AEA as a whole.

5.9 Domain Dependencies

AEA's domain knowledge depends upon the continued coherence of the Architecture Set.

Each architecture owns a distinct architectural concern while consuming propositions from other architectures where required. These dependencies do not transfer ownership.

A change within one architecture may therefore create consequences elsewhere, requiring Set Integrity and blast-radius assessment.

5.10 Domain Development

The knowledge, propositions, models and internal anatomy within an architecture may evolve substantially without changing the Domain structure of AEA.

Execution Architecture, for example, may evolve what AEA understands about instructions, processes, evidence, variants or the anatomy of an AEA Standard while the architectural phenomenon remains Execution.

AEA does not require structural expansion merely because its knowledge grows.

Growth within an architecture is evidence that AEA can adapt without structural proliferation.

Structural change to the Architecture Set is warranted only where evidence establishes a necessary architectural phenomenon for which the existing eleven provide no coherent home.

5.11 Domain Measurement Requirement

Domain requires continuing evidence that the eleven architectures remain sufficient; necessary architectural propositions have coherent homes; semantic collisions are not emerging; architecture boundaries remain viable; the Value Nucleus and Operating Ring remain coherent as a connected flat set; application is not repeatedly exposing unowned architectural phenomena; and AEA's value logic continues to produce meaningful consequence when applied.


6. Ecosystem Architecture — Interconnectedness

Ecosystem Architecture establishes the Actors, Relationships, Exchanges and Dependencies through which AEA is developed, challenged, applied, consumed and commercially interpreted.

6.1 Functional Actors

AEA requires the following functional Actor types:

  • Source — provides external knowledge, evidence, disciplines, research and observation from which AEA may learn without that material automatically becoming AEA doctrine.
  • Thinker — contributes to the development, challenge and extension of AEA thinking.
  • Implementer — applies AEA to actual businesses.
  • Customer — receives or consumes value created through AEA or its application.
  • Commercial Interpreter — creates commercially useful products, services, implementations or extensions from AEA without acquiring authority to redefine canonical AEA.

The explicit inclusion of Customer is essential. AEA's commercial and consequential ambitions require relationships with the parties for whom its application creates value.

These are Ecosystem Actors, not Workforce Roles or Participants. A single person or entity may instantiate more than one Actor where the relationships remain distinguishable.

6.2 Enterprise Relationship Model

Relationship Primary exchanges Resulting dependency
AEA ↔ Source External knowledge, research, evidence, disciplines and observations toward AEA; interpretation and citation may flow outward Access to relevant external knowledge without treating Source material as canon
AEA ↔ Thinker Canonical propositions and open questions outward; challenge, critique, development and candidate propositions inward Sufficient intellectual challenge to avoid stagnation
AEA ↔ Implementer Canonical AEA and application requirements outward; applied evidence, ambiguity, lessons and consequences inward Real application for testing, learning and demonstrated consequence
Implementer ↔ Customer AEA-enabled application, advice, product or outcome outward; requirements, adoption, feedback, evidence and economic value inward Applied and commercial value depends upon consequence for a Customer
AEA ↔ Customer Canonical knowledge, direct applications or products outward; adoption, evidence, feedback and economic value inward Direct Customer relationships may contribute to authority, learning and commercial value
AEA ↔ Commercial Interpreter Canonical knowledge and permitted use outward; wrappers, market reach, application evidence, feedback and economic value inward Propagation and value capture without surrendering canonical authority
Commercial Interpreter ↔ Customer Commercial wrapper, product or service outward; requirements, payment, adoption and outcome evidence inward Commercial success depends upon creating value Customers choose to consume

6.3 Ecosystem Boundary

Ecosystem participation does not confer architectural authority.

A Source may inform AEA without becoming doctrine. A Thinker may influence AEA without owning canon. An Implementer may expose a deficiency without independently changing AEA. A Customer may demonstrate or receive value without defining AEA. A Commercial Interpreter may derive substantial economic value from AEA without redefining it.

The existence of a Relationship or Dependency does not itself establish Trust.


7. Execution Architecture — Instructions

Execution Architecture establishes how the work required to perform, apply, maintain and develop AEA is instructed.

7.1 Instructional Source

An AEA Standard is not itself an Execution Instruction.

AEA does not require a second mirror set of Standards explaining how to perform the Standards.

The anatomy of each Architecture Standard package contains the authoritative material through which that architecture is understood and correctly applied.

7.2 Architecture Standard Package Anatomy

Each AEA Architecture Standard package contains the following core components:

  1. Published Standard — doctrine, scope, definitions, principles, ownership, boundaries and conformance requirements.
  2. Information Specification — the information and data captured about the architecture.
  3. Use Cases — defined ways in which the Standard is utilised for particular purposes.
  4. Construction Protocols — how the architecture's primary schematic, model or native construction is assembled.
  5. Native Render Specifications / Rendered Artefacts Register — additional artefacts that may be rendered or generated from the architecture.
  6. Conformance — conditions against which correct application or implementation is assessed.
  7. Reference Material — supporting material required to understand or apply the Standard without making it independent doctrine.
  8. Archive — superseded or historical package material preserved without masquerading as current authority.

The exact governed package and publication structure is controlled through AEA Governance. The enduring requirement is that AEA carries sufficient doctrine, information requirements, use, construction, rendering and conformance material for each architecture to be applied without inventing a parallel architecture.

7.3 Where the Instructions Sit

The instructional elements of AEA are principally contained in the construction requirements, application/use-case requirements and conformance conditions of the Standards, supported by their Information Specifications and governing doctrine.

The Published Standard establishes what must remain true. The Information Specification establishes what must be known or captured. The Use Cases establish how the architecture is utilised. The Construction Protocols establish how its primary representation is built. Conformance establishes how correct application is assessed.

7.4 Core Classes of Work

AEA requires executable work to apply AEA; maintain AEA; test and develop AEA; and govern and publish AEA.

Where repeatable work is required, it should conform to:

Canonical Invariant Contract → Approved Variants → Tasks → Instructions

Completion is a condition, not simply the end of an activity list. Evidence, exceptions and escalation must be explicit where required.

Lessons arising from performance must be capable of returning to AEA's learning mechanisms. Execution performs the work; it does not independently decide that canonical AEA should change.


8. Expression Architecture — Individuality

Canonical AEA and things created from AEA are distinct.

Canonical AEA must retain controlled architectural meaning independent of the audiences, contexts, products and services through which its application is encountered.

AEA itself is not transformed into different architectures for different audiences.

Applications, extensions and commercial wrappers derived from AEA may take forms appropriate to their particular audience, context and purpose.

A software product may apply AEA.

A methodology may operationalise AEA.

A service may use AEA.

A publication may explain AEA.

A certification may assess conformance with AEA.

None becomes an alternative canonical AEA merely because it derives from it.

The design therefore separates:

canonical AEA
continued development of AEA
application of AEA
extensions derived from AEA
commercialisation of those applications and extensions

The variability belongs to what is created from AEA, not to the canonical architecture itself.


9. Possibility Architecture — Optionality

AEA must preserve legitimate possibility for its own continued development.

AEA must permit current architectural propositions to be challenged and alternatives to be explored without those alternatives automatically becoming canonical AEA.

Any current AEA proposition may eventually prove insufficient as business changes or understanding develops.

Possibility provides the space in which that insufficiency can be considered.

It does not itself alter canonical AEA.

This enables AEA to remain adaptive without making its current authoritative state ambiguous.


10. Reality Architecture — Actuality

AEA must always be capable of establishing its actual state.

AEA must establish which published Standard is the current authoritative source of truth.

AEA must also preserve sufficient historical actuality to establish what was previously authoritative and how its published state has changed over time.

Reality establishes what AEA is and was.

It does not determine whether that state is desirable, sufficiently evidenced or worthy of Reliance.

This distinction is essential to an adaptive standards system: change is possible without making the current state unknowable.


11. Intelligence Architecture — Understanding

AEA requires continuing understanding of its own sufficiency.

That understanding cannot be established solely through theoretical development.

AEA must continuously measure and develop its understanding of itself through evidence arising from AEA in Action.

AEA in Action provides the proving ground through which the architecture encounters actual businesses.

Application can expose ambiguity, collision, missing architectural homes, usability issues, insufficiency and unintended consequence.

It can also demonstrate where the architecture performs as intended.

The learning relationship is:

AEA → AEA in Action → observed actuality and outcomes → Understanding → Possibility → governed development of AEA

An individual implementation does not independently define the architecture.

AEA must be capable of distinguishing, where possible, between:

implementation failure and architectural failure;
local anomaly and recurring pattern;
misunderstanding and genuine ambiguity;
contextual difference and architectural insufficiency.

AEA learns from the businesses it architects without allowing any individual implementation to become the architecture.


12. Workforce Architecture — Participation

AEA requires continuing participation in its operation and development.

The required forms of participation include:

Monitoring · Updating · Continued Development · Testing

These are participation requirements, not predetermined people or jobs.

AEA's participation requirements must remain independent of the particular Participants through which they are fulfilled.

Participation may therefore be fulfilled by humans, organisations, AI agents, automated systems, hybrid arrangements or future forms of participation.

The Participant may change without changing the underlying requirement.

Participation in monitoring, testing, updating or developing AEA does not itself confer authority to alter canonical AEA.


13. Environment Architecture — Enablement

AEA requires an enabling environment capable of supporting its continued operation.

That environment must be capable of preserving an authoritative source of AEA, its history and necessary traceability while enabling the monitoring, updating, development, testing, application and consumption required by the architecture.

AEA must also be capable of being reliably accessed by the legitimate human and non-human consumers that require it.

AEA's enabling requirements must remain independent of the particular technology selected to fulfil them.

Repositories, databases, knowledge graphs, APIs, LLMs, publishing systems, runtimes and other technologies are potential fulfilment choices.

They are not themselves AEA.

The environment may therefore evolve substantially without requiring the architecture it enables to be redefined.


14. Trust Architecture — Reliance

AEA intends to warrant Reliance through what it can demonstrate, not merely through what it claims.

Reliance on AEA must be capable of being supported by evidence of its coherence, application, testing, provenance and demonstrated consequence.

AEA is not intended to exist only as theoretical architecture.

Its application provides evidence of whether it works in actual business conditions.

Where appropriate to the application, demonstrated consequence may include economic measures such as:

return on investment; investment payback; realised value; performance improvement; avoided cost or loss; and other contextually appropriate measures of consequence.

Positive evidence is not the only legitimate evidence.

Evidence that challenges the sufficiency or effectiveness of AEA must be capable of entering its learning and development mechanisms.

A failed application, unexpected result or architectural insufficiency cannot simply be excluded because it weakens the appearance of authority.

The ability to expose, understand and respond to adverse evidence contributes to the conditions under which AEA can legitimately be relied upon.

AEA therefore builds Trust by being demonstrable, challengeable, traceable and adaptive.


15. Continued Development of AEA

AEA must simultaneously preserve its canonical integrity and permit its continued development.

These are not contradictory requirements.

Canonical integrity protects what constitutes authoritative AEA at a point in time.

Possibility permits current propositions to be challenged.

Reality establishes what is actually current.

Intelligence develops understanding from evidence.

Workforce provides the required participation.

Environment provides the required enablement.

Trust establishes the conditions under which the result can be relied upon.

Execution provides the instructional mechanisms through which required work is performed.

The Standards therefore remain stable enough to constitute an authoritative source while the architecture remains capable of adapting when warranted.


16. Enduring AEA System Hierarchy

AEA Design must distinguish the enduring architecture of AEA from the historical sequence through which that architecture was discovered.

Self-application was the derivation method used to establish this Design. It is not the permanent operating hierarchy.

The enduring hierarchy is:

AEA Standards — architectural authority. The Standards establish canonical AEA doctrine.

AEA Design — defines how AEA itself is constituted, operates, develops and remains coherent.

AEA Governance System — governs how canonical AEA is maintained, changed, approved, released, protected and assured in accordance with AEA Design.

AEA Body of Knowledge — the governed canonical knowledge structure through which AEA propositions are maintained, related, addressed, traced and published.

AEA in Action — the application and proving environment through which AEA is used against actual businesses, creates consequence and generates evidence and learning.

A further artefact sits alongside this hierarchy:

AEA Design Instance — records the current real-world instantiation of AEA Design: actual Sources, Actors, Roles, Skills, Participants, assignments, technologies, repositories, processes, products, evidence mechanisms and other current fulfilment choices.

The Design Instance is not another layer of authority. It records the current implementation of the enduring Design.

16.1 Authority Across the Hierarchy

The hierarchy does not mean that each layer is free to redefine the layer above it.

The Standards remain the source of architectural doctrine. AEA Design establishes what must be true of AEA when those Standards are applied to AEA itself. Governance controls the authorised mechanisms through which canonical AEA may change. The Body of Knowledge maintains the governed canonical propositions and their relationships. AEA in Action applies the architecture and generates evidence.

Governance has authority over the change process. It does not have authority to invent architectural truth.

16.2 Governance Operating Loop

The enduring operating model is not a one-way cascade.

AEA in Action → Reality → Intelligence → Possibility → proposed change → Governance → changed Standards → updated AEA Design where affected

Reality captures what actually occurred. Intelligence establishes what can be understood from that actuality. Possibility develops legitimate alternatives. Proposed change enters Governance. Governance controls assessment, blast radius, authority, approval, release and supersession.

Where a Standard changes, AEA Design is reassessed to determine whether the change alters the design of AEA itself. The governed Body of Knowledge is updated to reflect the resulting canonical state. The changed architecture returns to AEA in Action and the loop continues.

16.3 Historical Derivation

The present Design was initially established through:

AEA Standards → application of AEA to itself → AEA Design

That explains the provenance of this Design. It must not be mistaken for the permanent operating cascade.


17. Relationship to the AEA Body of Knowledge

The AEA Body of Knowledge is the governed canonical knowledge structure through which established AEA propositions are maintained, related, addressed, traced and published.

It is not an independent source of doctrine.

Its structure must support AEA Design and be controlled through the AEA Governance System. It may support multiple authorised publications, machine interfaces, educational forms and commercial uses without those outputs becoming independent sources of AEA truth.


18. Relationship to AEA in Action

AEA in Action is the principal application and proving environment for AEA.

It applies AEA to actual businesses and generates evidence of its operation and consequence. It may contain proprietary methods for traversal, composition, assembly, comparison, analysis, AI-supported application and other implementation practices.

Those methods do not independently constitute AEA doctrine.

AEA in Action connects architecture, application, evidence, economic consequence and continued development.


19. Relationship to the AEA Design Instance

AEA Design defines the enduring requirements and properties of AEA.

AEA Design = what must be true.

AEA Design Instance = what currently makes it true.

The Instance records current fulfilment choices and is expected to change more frequently than the Design.

It may record current Directional targets and waypoints; Domain products and commercial models; named Sources, Thinkers, Implementers, Customers and Commercial Interpreters; Execution processes; Expression wrappers and publications; active Possibility candidates; current Standards and observed states; Intelligence sources, measures and evidence stores; Workforce Roles, Skills, sourcing and Participants; Environment repositories, tools, LLMs and runtimes; and Trust evidence, assurance, ROI/payback and reliance conditions.

Moving these changeable facts into the Instance prevents temporary implementation choices from being mistaken for enduring AEA Design.


20. AEA Design Relationship

The AEA Standards define the architecture of business.

The eleven architectures constitute AEA's complete current domain knowledge structure.

AEA Design defines the enduring design of AEA itself.

The AEA Governance System controls how canonical AEA is maintained and changed in accordance with that Design.

The AEA Body of Knowledge maintains the governed canonical knowledge of AEA.

AEA in Action applies AEA to actual businesses and produces evidence, learning and economic consequence.

The AEA Design Instance records how the enduring Design is currently realised.

Evidence from application returns through Reality, Intelligence and Possibility into governed change.

The Architecture Set itself changes only where evidence establishes that a necessary architectural phenomenon has no coherent home within the existing eleven architectures.

AEA is a connected, governed and adaptive architecture of business whose eleven architectural domains interlock to form a complete business schematic, whose knowledge can continue to grow without structural proliferation, and whose application continuously tests whether that completeness remains true.

Keep readingEleven distinct architectures. One enterprise.Standards · Architecture Set Standard →
→Continue

Where to go next.