The EXA Lexicon

View raw

{
  "title": "The EXA Lexicon",
  "slug": "lexicon",
  "objectNumber": 1,
  "version": "1.0",
  "status": "published",
  "source": "Series One · Series Two",
  "summary": "Canonical, versioned glossary of every coined term in the Enterprise Experience Architecture framework. Covers all terms from Series One (The 2026 Field Guide) and Series Two (The Specification Economy), both complete and published, plus two role terms — Enterprise Experience Architect and Agentic Experience Architect — already in public use on reidexa.design/exa ahead of their full treatment in the forthcoming Series Three and Series Four.",
  "lastUpdated": "2026-06-30",
  "changelog": [
    {
      "date": "2026-06-30",
      "note": "Founding term set published: 26 terms drawn from Series One and Series Two in full, plus the two forthcoming role terms already live on the site's framework page. Replaces the prior placeholder starter set."
    },
    {
      "date": "2026-07-01",
      "note": "Added a category field to every term (governance/roles/economics/mechanics) to power the findability grouping added this session. Additive only — no definition text changed."
    }
  ],
  "type": "reference",
  "tagline": "The canonical, versioned glossary of every coined term in the Enterprise Experience Architecture framework — the shared language the Standard is built on.",
  "terms": [
    {
      "term": "The Adoption Contract",
      "slug": "adoption-contract",
      "source": "Series One",
      "definition": "The implicit agreement between a central architecture function and the product squads it serves: compliance with the specification follows from the specification's utility, not from a top-down mandate. A squad adopts the constitution because building against it is faster than building around it, not because it was told to.",
      "category": "governance",
      "seeAlso": [
        "design-as-a-service",
        "cultural-veto",
        "enterprise-experience-architecture"
      ],
      "firstPublished": "2026-05-27",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/ai-doesnt-need-a-better-design-system-it-needs-a-constitution-853f89c09038"
    },
    {
      "term": "The Agentic Constitution",
      "slug": "agentic-constitution",
      "source": "Series One · Article 4 — defended in EXA vs. SDD",
      "definition": "The machine-readable document that encodes an enterprise's Infrastructure of Intent for AI agent consumption. It is a constraint file — .md, .cursorrules, or equivalent — that an agent executes against directly, replacing the annotated screen a developer once interpreted by hand. The architect who writes it governs everything an agent subsequently builds. See The Agentic Constitution Format (Standard object 2) for the structured constraint-block syntax.",
      "category": "mechanics",
      "seeAlso": [
        "infrastructure-of-intent",
        "governed-autonomy",
        "semantic-handoff"
      ],
      "firstPublished": "2026-06-05",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/the-new-deliverable-why-your-design-architect-writes-markdown-2601b645ecf7"
    },
    {
      "term": "Agentic Experience Architect",
      "slug": "agentic-experience-architect",
      "source": "Series Four (forthcoming)",
      "definition": "The product-level counterpart to the Enterprise Experience Architect: the function that governs what agents generate in real time, on surfaces that are never assembled the same way twice and therefore have no static specification to review against. Track A of EXA's two practitioner tracks. The full role definition and evaluation rubric ship with Series Four; the term is already in public use.",
      "category": "roles",
      "seeAlso": [
        "enterprise-experience-architect",
        "reviewer-interface",
        "governed-autonomy"
      ]
    },
    {
      "term": "Cognitive Endurance",
      "slug": "cognitive-endurance",
      "source": "Series One · Article 3",
      "definition": "The design metric that matters for enterprise software: an operator's ability to sustain performance, accuracy, and clarity of judgment across an 8–10 hour shift inside a single application. Cognitive Endurance treats friction as a direct threat to operating margin rather than a polish problem — the relevant failure mode is not 'unintuitive,' it is 'degrades judgment by hour six.'",
      "category": "mechanics",
      "visual": {
        "kind": "stat",
        "value": 6,
        "suffix": "hrs",
        "label": "Until judgment degrades"
      },
      "seeAlso": [
        "experience-utility",
        "margin-multiplier"
      ],
      "firstPublished": "2026-05-21",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/your-design-system-is-not-decaying-it-is-obsolete-54e0dfe52438"
    },
    {
      "term": "Continuous Learning Loop",
      "slug": "continuous-learning-loop",
      "source": "Series One",
      "definition": "The mechanism by which real telemetry on component and pattern consumption flows back to the architect, making the specification more precise with every deployment. Engineering delivers consumption signals as a standing handoff; the architect does not need direct dashboard access for the loop to function.",
      "category": "mechanics",
      "seeAlso": [
        "infrastructure-of-intent",
        "specification-scorecard"
      ],
      "firstPublished": "2026-05-27",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/ai-doesnt-need-a-better-design-system-it-needs-a-constitution-853f89c09038"
    },
    {
      "term": "The Cultural Veto",
      "slug": "cultural-veto",
      "source": "Series One · Series Two",
      "definition": "The organizational risk in which senior practitioners resist shifting from a production role to a validation role, because the performance metrics that reward them still count screens produced, not specifications governed. A leadership and incentive-design problem, not a training problem — behavior does not change until the scorecard does.",
      "category": "governance",
      "seeAlso": [
        "reviewer-interface",
        "specification-scorecard",
        "enterprise-experience-architect"
      ],
      "firstPublished": "2026-05-27",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/ai-doesnt-need-a-better-design-system-it-needs-a-constitution-853f89c09038"
    },
    {
      "term": "Dark State",
      "slug": "dark-state",
      "source": "Series Two",
      "definition": "An operational condition that exists somewhere in the enterprise system but has never been named, mapped, or encoded in any specification. Dark states are not ambiguous requirements; they are requirements nobody discovered yet — typically surfaced by the people who already handle them informally (support escalations, manual overrides, sales-floor workarounds), at a fraction of the cost of discovering them in production.",
      "category": "mechanics",
      "seeAlso": [
        "legacy-anchor",
        "continuous-learning-loop"
      ],
      "firstPublished": "2026-06-16",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/the-unit-economics-of-intent-0c136df3cd46"
    },
    {
      "term": "Design as a Service (DaaS)",
      "slug": "design-as-a-service",
      "source": "Series One",
      "definition": "The operating model in which a central EXA function acts as a hub of truth that global product teams subscribe to, rather than a gatekeeping committee teams route requests through. Compliance is earned through utility, not imposed through mandate — see The Adoption Contract.",
      "category": "governance",
      "seeAlso": [
        "adoption-contract",
        "enterprise-experience-architecture",
        "90-day-governance-playbook"
      ],
      "firstPublished": "2026-05-21",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/your-design-system-is-not-decaying-it-is-obsolete-54e0dfe52438"
    },
    {
      "term": "Enterprise Experience Architect",
      "slug": "enterprise-experience-architect",
      "source": "Introduced Series One/Two — full treatment in Series Three (forthcoming)",
      "definition": "The permanent governing function the enterprise org chart is currently missing: the role that ratifies and enforces the Agentic Constitution, with standing authority alongside compliance, operations, and legal. Track B of EXA's two practitioner tracks. The deep-dive treatment, evaluation rubric, and career ladder ship with Series Three; the term is already in public use.",
      "category": "roles",
      "seeAlso": [
        "agentic-experience-architect",
        "reviewer-interface",
        "cultural-veto"
      ]
    },
    {
      "term": "Enterprise Experience Architecture (EXA)",
      "slug": "enterprise-experience-architecture",
      "source": "Series One",
      "definition": "The discipline of designing the governed, intelligent infrastructure that defines how digital products are built and experienced at enterprise scale. EXA succeeds the static design system: where a design system specifies what a product looks like, EXA specifies the semantic variables, business rules, interaction logic, and governance protocols that every downstream system — human or AI — builds against. The framework organizes around three pillars: Scale, Intelligence, and Clarity.",
      "category": "governance",
      "seeAlso": [
        "infrastructure-of-intent",
        "experience-utility",
        "semantic-layer"
      ],
      "firstPublished": "2026-05-21",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/your-design-system-is-not-decaying-it-is-obsolete-54e0dfe52438"
    },
    {
      "term": "The Experience Architecture Maturity Model",
      "slug": "experience-architecture-maturity-model",
      "source": "Series Two · Article 4",
      "definition": "The four-stage self-assessment an organization runs to locate its current state and name its next move: Ungoverned, Constrained, Instrumented, Compounding. Each stage names both the failure mode an organization is exposed to and the specific lever that advances it to the next stage.",
      "category": "governance",
      "visual": {
        "kind": "tiers",
        "stages": [
          {
            "label": "Ungoverned",
            "body": "A static design system only governs states it knew about at launch — everything after that goes unnamed, forked, or becomes a production incident."
          },
          {
            "label": "Constrained",
            "body": "A constitution now exists and rework drops measurably — but with no function defending it, drift starts the day after it's committed."
          },
          {
            "label": "Instrumented",
            "body": "Deviations are caught before merge and governance is finally measurable — real discipline, but still reactive until the loop closes itself."
          },
          {
            "label": "Compounding",
            "body": "The specification improves with every deployment, without anyone hunting for gaps — the architecture compounds correctness on its own."
          }
        ]
      },
      "seeAlso": [
        "90-day-governance-playbook",
        "specification-scorecard"
      ],
      "firstPublished": "2026-06-23",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/the-only-moat-left-is-the-one-you-specify-d55ff210383e"
    },
    {
      "term": "Experience Utility",
      "slug": "experience-utility",
      "source": "Series One",
      "definition": "The reframing of design from an aesthetic choice into high-availability, governed business infrastructure — held to the operational standard of a cloud architecture or a data pipeline, not the standard of a creative deliverable.",
      "category": "economics",
      "seeAlso": [
        "cognitive-endurance",
        "margin-multiplier",
        "enterprise-experience-architecture"
      ],
      "firstPublished": "2026-05-21",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/your-design-system-is-not-decaying-it-is-obsolete-54e0dfe52438"
    },
    {
      "term": "The Garbage-In Multiplier",
      "slug": "garbage-in-multiplier",
      "source": "Series Two · Article 3",
      "definition": "The observation that AI accelerates good architecture and bad architecture without discrimination. An ungoverned specification does not slow agents down — it produces broken systems faster. The operating consequence is a sequencing rule: govern the specification before scaling agents against it, or go slow to go fast.",
      "category": "economics",
      "visual": {
        "kind": "comparison",
        "left": {
          "label": "Governed specification",
          "body": "AI accelerates good architecture. Agents scale safely against a specification that was governed first."
        },
        "right": {
          "label": "Ungoverned specification",
          "body": "AI accelerates bad architecture too. Agents don't slow down — they produce broken systems faster."
        }
      },
      "seeAlso": [
        "retry-tax",
        "governed-autonomy",
        "margin-multiplier"
      ],
      "firstPublished": "2026-06-18",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/hiring-for-the-artifact-instead-of-the-function-is-the-most-expensive-shortcut-you-will-take-f155abe341fe"
    },
    {
      "term": "Governed Autonomy",
      "slug": "governed-autonomy",
      "source": "Series One · Article 2",
      "definition": "The operating condition in which AI agents act with full autonomy inside strict, mathematically defined architectural boundaries. Agents are not supervised turn-by-turn by a human reviewer; they are constrained by a specification written in advance. The result is execution speed without the chaos that comes from unconstrained agent behavior.",
      "category": "mechanics",
      "seeAlso": [
        "agentic-constitution",
        "reviewer-interface",
        "infrastructure-of-intent"
      ],
      "firstPublished": "2026-05-21",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/your-design-system-is-not-decaying-it-is-obsolete-54e0dfe52438"
    },
    {
      "term": "Infrastructure of Intent",
      "slug": "infrastructure-of-intent",
      "source": "Series One · Article 1",
      "definition": "The complete, machine-readable specification of an enterprise digital platform: semantic variables, design tokens, business rules, interaction logic, and governance protocols, encoded in one place. It is the artifact an architect writes and the artifact every agent, developer, and product team builds against — the layer that makes 'what the system is supposed to do' a queryable fact rather than tribal knowledge.",
      "category": "mechanics",
      "seeAlso": [
        "semantic-layer",
        "agentic-constitution",
        "variables-over-pixels"
      ],
      "firstPublished": "2026-05-21",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/your-design-system-is-not-decaying-it-is-obsolete-54e0dfe52438"
    },
    {
      "term": "The Legacy Anchor",
      "slug": "legacy-anchor",
      "source": "Series One · Series Two",
      "definition": "The structural challenge of deploying modern semantic governance against legacy backend infrastructure that was never built to expose the states a constitution needs to govern. Not a reason to delay governance — a constraint the State Inventory process has to plan around.",
      "category": "mechanics",
      "seeAlso": [
        "dark-state",
        "agentic-constitution"
      ]
    },
    {
      "term": "The Logic-Review Gate",
      "slug": "logic-review-gate",
      "source": "Series Two · Article 3",
      "definition": "The governing mechanism that moves a design leader's review function upstream — from approving finished surfaces after the build to approving constraint definitions before it. A leader who governs constraints at the gate governs everything built downstream without reviewing any of it directly. It sits at the 'Definition of Ready' checkpoint inside an existing agile workflow, not as an additional meeting.",
      "category": "governance",
      "seeAlso": [
        "90-day-governance-playbook",
        "reviewer-interface",
        "enterprise-experience-architect"
      ],
      "firstPublished": "2026-06-18",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/hiring-for-the-artifact-instead-of-the-function-is-the-most-expensive-shortcut-you-will-take-f155abe341fe"
    },
    {
      "term": "Margin Multiplier",
      "slug": "margin-multiplier",
      "source": "Series One",
      "definition": "EXA's business-value compression: a single architectural decision that simultaneously increases build velocity, reduces error rates, improves adoption, and shortens time-to-market, rather than trading one against another. The same mechanism runs in reverse under ungoverned conditions — see The Garbage-In Multiplier and The Retry Tax.",
      "category": "economics",
      "seeAlso": [
        "garbage-in-multiplier",
        "retry-tax",
        "experience-utility"
      ],
      "firstPublished": "2026-05-21",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/your-design-system-is-not-decaying-it-is-obsolete-54e0dfe52438"
    },
    {
      "term": "The 90-Day Governance Playbook",
      "slug": "90-day-governance-playbook",
      "source": "Series Two · Article 3",
      "definition": "The operating model that runs specification governance as a standing discipline rather than a one-time hire: a sequenced rollout covering pilot selection, state enumeration, token governance, the Logic-Review Gate, and an ongoing scorecard, executed over 90 days.",
      "category": "governance",
      "visual": {
        "kind": "stat",
        "value": 90,
        "suffix": "days",
        "label": "Sequenced rollout"
      },
      "seeAlso": [
        "logic-review-gate",
        "specification-scorecard",
        "experience-architecture-maturity-model"
      ],
      "firstPublished": "2026-06-18",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/hiring-for-the-artifact-instead-of-the-function-is-the-most-expensive-shortcut-you-will-take-f155abe341fe"
    },
    {
      "term": "Reviewer Interface",
      "slug": "reviewer-interface",
      "source": "Series One · Article 2 — organizational treatment in Series Three (forthcoming)",
      "definition": "The human role inside a governed agentic system. The practitioner's job shifts from producing screens to validating what an agent produced against what the specification required — governing the output, not operating the surface.",
      "category": "roles",
      "seeAlso": [
        "governed-autonomy",
        "enterprise-experience-architect",
        "cultural-veto"
      ],
      "firstPublished": "2026-05-27",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/ai-doesnt-need-a-better-design-system-it-needs-a-constitution-853f89c09038"
    },
    {
      "term": "The Retry Tax",
      "slug": "retry-tax",
      "source": "Series Two · Article 1",
      "definition": "The metered cost of specification ambiguity. AI inference costs generated when agents loop against an incomplete or ungoverned specification — observed running as high as roughly 50× the token cost of a single clean pass. Every retry cycle is a billable consequence of a definition gap the architecture did not close upstream.",
      "category": "economics",
      "visual": {
        "kind": "stat",
        "value": 50,
        "suffix": "×",
        "label": "Token cost of a clean pass"
      },
      "seeAlso": [
        "garbage-in-multiplier",
        "specification-economy",
        "margin-multiplier"
      ],
      "firstPublished": "2026-06-10",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/good-enough-is-the-most-expensive-thing-you-will-ever-ship-cd076eaf08c2"
    },
    {
      "term": "The Semantic Handoff",
      "slug": "semantic-handoff",
      "source": "Series One · Article 4",
      "definition": "The replacement of visual redlines with machine-readable constraint files. Where a traditional handoff gives a developer an annotated screen to interpret, a semantic handoff gives an AI coding agent a constraint file to execute — collapsing the translation step where intent traditionally got lost.",
      "category": "mechanics",
      "seeAlso": [
        "semantic-layer",
        "agentic-constitution",
        "infrastructure-of-intent"
      ],
      "firstPublished": "2026-06-05",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/the-new-deliverable-why-your-design-architect-writes-markdown-2601b645ecf7"
    },
    {
      "term": "The Semantic Layer",
      "slug": "semantic-layer",
      "source": "Series One · Article 2",
      "definition": "The machine-readable layer that sits between visual design and compiled code. It encodes why an interface behaves the way it does — the structural rules, conditions, and token bindings that make invalid states impossible — not merely what it looks like.",
      "category": "mechanics",
      "seeAlso": [
        "variables-over-pixels",
        "infrastructure-of-intent",
        "semantic-handoff"
      ],
      "firstPublished": "2026-05-21",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/your-design-system-is-not-decaying-it-is-obsolete-54e0dfe52438"
    },
    {
      "term": "The Specification Economy",
      "slug": "specification-economy",
      "source": "Series Two · Article 1",
      "definition": "The economic worldview of the agentic enterprise: once production approaches zero marginal cost, the specification becomes the primary unit of economic value. The only thing left worth paying for precisely is the definition of what agents are allowed to execute against.",
      "category": "economics",
      "seeAlso": [
        "retry-tax",
        "specification-scorecard",
        "infrastructure-of-intent"
      ],
      "firstPublished": "2026-06-10",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/good-enough-is-the-most-expensive-thing-you-will-ever-ship-cd076eaf08c2"
    },
    {
      "term": "The Specification Scorecard",
      "slug": "specification-scorecard",
      "source": "Series Two · Article 2",
      "definition": "The four-metric instrument that makes specification quality legible to finance: Retry Rate, Deviation Caught Before Merge, Escalation Rate, and Onboarding Velocity. Each metric carries a direct dollar translation, which is what makes specification quality defensible in a budget review rather than treated as a design preference.",
      "category": "economics",
      "seeAlso": [
        "retry-tax",
        "specification-economy",
        "logic-review-gate"
      ],
      "firstPublished": "2026-06-16",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/the-unit-economics-of-intent-0c136df3cd46"
    },
    {
      "term": "Variables Over Pixels",
      "slug": "variables-over-pixels",
      "source": "Series One",
      "definition": "The first structural shift EXA asks of a design practice: at enterprise scale, logical aliases — tokens, variables, conditional bindings — outperform manually managed pixel values. It is the move from visual thinking to conditional thinking, and the precondition for anything in the system being machine-readable at all.",
      "category": "mechanics",
      "seeAlso": [
        "semantic-layer",
        "infrastructure-of-intent"
      ],
      "firstPublished": "2026-05-21",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/your-design-system-is-not-decaying-it-is-obsolete-54e0dfe52438"
    }
  ]
}