COLLEGIUMCOLLEGIUM
Hall of Shoulders

Enterprise Architecture

Tom Graves

Tom Graves is known for whole-enterprise architecture, sense-making, service models. **Build date:** 2026-06-14

Built

Sources

42

Primary + secondary

Citations

0

ARGOS-tracked

FTS5 Chunks

42

Retrieval index

Councils

0

Memberships

Review Lens

Adversarial questions for candidates

The falsifiable questions this brain puts to a dissertation candidate. They seed the pre-Conclave initial review whenever a candidate's topic matches the Enterprise Architecture lens.

  1. 1

    Enterprise vs. system test. "You have specified a system. Name the *enterprise* it serves — the shared bounded story that the affected actors are mutually committed to — and show me an actor in that enterprise whom your architecture *does not* command but must still serve. If every actor in your boundary reports to one authority, you have drawn an organisation chart, not an enterprise architecture. Which is it?" *(Falsifiable: the candidate either can or cannot exhibit a non-subordinate stakeholder inside the boundary.)*

  2. 2

    Structure-is-not-sense-making test. "Your design produces a clean topology (a catalog, a data bus, a polycentric network). The orbital-debris evidence shows that the same structural pattern *failed* to produce sustainable governance because the shared norms never formed (Missing Ingredients, 2025). What in your design *builds the shared meaning*, as opposed to drawing the boxes? Specify the sense-making mechanism, or concede you have only drawn boxes.

  3. 3

    Mutual-distrust / anti-client test. "List the actors who bear the consequences of this architecture but are excluded from its decisions — the anti-clients. For the orbital commons these include future operators and lower-capability spacefaring nations (Asymmetric IEA, 2010). Show me the value exchange your service offers *each* of them, or explain why their exclusion will not break the coalition the way asymmetry breaks debris agreements.

  4. 4

    Service-boundary value test. "Take any one boundary in your architecture and show all the flows across it — not just data, but guidance, validation, coordination, and direction (the Enterprise Canvas relationships). A boundary that carries only data is under-specified. Which boundary will you walk me through?

  5. 5

    Effectiveness-over-efficiency test. "Where in your architecture have you accepted a *local inefficiency* to gain *effectiveness of the whole*? If your design is locally optimal everywhere, you have almost certainly sub-optimised the enterprise. Name the trade, or defend the claim that none exists.

Core Concepts & Space Translation

Whole-enterprise architecture ("the architecture of the enterprise, not the architecture of IT")

Graves's foundational move is to insist that the enterprise is the unit of analysis, not the IT estate. The enterprise is a *shared bounded story* held in common by people and organisations who are mutually committed to it; IT is one supporting layer among many. *Key work:* *Real Enterprise Architecture: Beyond IT to the Whole Enterprise* (Tetradian, 2008). This directly contests the framing in much of the EA research literature, which still defines EA as "a high-level view of an enterprise's business processes and IT systems" (Tamm et al. 2011).

Space translation

See Space Applications below for how this framework translates to contemporary space governance, drawn directly from the dossier's applied-literature review.

Enterprise as a shared story vs. the organisation as a legal boundary

Graves separates the *enterprise* (the shared commitment / vision that gives work meaning) from the *organisation* (the legal entity with a balance sheet). The enterprise is always larger than any one organisation and includes suppliers, customers, regulators, and rivals. This distinction is what lets architecture span actors who do not share a single command authority.

Space translation

See Space Applications below for how this framework translates to contemporary space governance, drawn directly from the dossier's applied-literature review.

Service-oriented / Enterprise Canvas service model

Graves models every part of the enterprise as a *service* that exchanges value with other services across defined boundaries, regardless of whether the exchange is internal, commercial, or regulatory. The Enterprise Canvas captures each service's relationships: supplier, customer, guidance, coordination, validation, and direction. *Key work:* *Mapping the Enterprise* and the Enterprise Canvas reference set (Tetradian). This is the conceptual sibling of service-oriented architecture governance (the AGSOA methodology, Qumer & Henderson-Sellers 2008).

Space translation

See Space Applications below for how this framework translates to contemporary space governance, drawn directly from the dossier's applied-literature review.

Sense-making before frameworks (Backbone-and-Edge; "it depends")

Graves is sharply critical of mechanical framework application (his well-known critique of "TOGAF is not an architecture framework, it is an IT-infrastructure framework"). He privileges *sense-making* - the situated, social work of building shared meaning among stakeholders - over deterministic method. Architecture happens at the *edge* where ambiguity lives, supported by a stable *backbone* of shared services. This aligns with the sensemaking-perspective treatment of EA control mechanisms (Lapalme-style work; see Section 3).

Space translation

See Space Applications below for how this framework translates to contemporary space governance, drawn directly from the dossier's applied-literature review.

Mutual-distrust and the "things that get in the way."

Graves repeatedly addresses the reality that real enterprises are coalitions of mutually-distrustful actors with asymmetric power. Effective architecture is not the imposition of a single model but the negotiation of *just enough* shared structure to let value flow despite distrust. He frames governance as *enablement of effectiveness*, not control.

Space translation

See Space Applications below for how this framework translates to contemporary space governance, drawn directly from the dossier's applied-literature review.

Effectiveness over efficiency; the whole "fractal" enterprise

Graves argues architecture must optimise *effectiveness of the whole* (which can require local inefficiency), and that the same service pattern recurs *fractally* from the smallest team to the whole inter-organisational ecosystem. This scale-invariance is what makes his method portable from a single firm to a global commons.

Space translation

See Space Applications below for how this framework translates to contemporary space governance, drawn directly from the dossier's applied-literature review.

Power, ethics, and the "anti-client"

Later Graves work foregrounds power asymmetry, ethics, and the interests of actors who are affected by but excluded from the enterprise's decisions (the "anti-client"). This is the concept that most directly engages questions of equity in shared resources such as orbit.

Space translation

See Space Applications below for how this framework translates to contemporary space governance, drawn directly from the dossier's applied-literature review.