The EXA Lexicon

View raw

{
  "title": "The EXA Lexicon",
  "slug": "lexicon",
  "objectNumber": 1,
  "version": "1.0",
  "status": "published",
  "source": "Series One · Series Two",
  "sourceArticleUrl": "https://medium.com/enterprise-experience-architecture/spec-driven-development-certifies-the-code-who-certifies-the-consequence-a3b0503af23a",
  "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-08-16",
  "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."
    },
    {
      "date": "2026-07-16",
      "note": "Worked example populated (Build Ledger §9 item 4 — the last founding-release content gap): an object-level diagnosis walking one organization across the Experience Architecture Maturity Model's four stages, threading Dark State, the Agentic Constitution, the Logic-Review Gate, and the Continuous Learning Loop. Reworded from Series Two, Article 4 ('The Only Moat Left Is the One You Specify'). Additive — no term definitions changed, version unchanged."
    },
    {
      "date": "2026-07-25",
      "note": "Five Series Three terms added following Article 1's publication ('Someone Just Asked Who Governs Your AI. Your Org Chart Has No Answer.'): The Governance Vacancy and The Authority Audit are fully defined by Article 1; The Provisional Surface, Specification Authority, and Blast Radius are seeded with Article 1's current wording pending fuller mechanical treatment in Articles 3 and 4. Term count 26 → 31. Resolves the standing exclusion previously noted in Build Ledger §3.2."
    },
    {
      "date": "2026-08-07",
      "note": "Two existing terms extended in place following Article 3's publication ('Your Kill Switch Works. Nobody Has the Standing to Pull It.') — no terms added, renamed, or removed; term count unchanged at 31, both slugs unchanged. The Cultural Veto: the Series One/Two risk framing is retained as the origin, with Article 3's deliberate promotion of that risk to an operational mechanism appended — the standing, executive-backed authority to halt a live deployment running against an uncertified constraint set, and the three conditions it holds on. The Continuous Learning Loop: the original component-consumption stream is retained, with Article 3's second telemetry stream appended — override events resolved to a shared versioned constraint ID and aggregated into one log, the substrate the Amendment Protocol's structural signal is matched across. Each term's source field gained a trailing Series Three clause; firstPublished and sourceUrl are unchanged, since both remain factual records of first appearance."
    },
    {
      "date": "2026-08-16",
      "note": "Enterprise Experience Architect's source field corrected following Article 4's publication ('You Can Describe the Job. You Cannot Name It.'): 'full treatment in Series Three (forthcoming)' replaced with 'full treatment in Series Three, Article 4', since Article 4 is confirmed as the article that delivered the deep-dive treatment, evaluation rubric, and career ladder this term's own definition text already promised. Source-field correction only — definition, seeAlso, firstPublished, and category unchanged; term count and slug unchanged. The Reviewer Interface term's own still-stale source field is a separate, unresolved judgment call (which article fulfills its 'organizational treatment' clause) and was deliberately left untouched pending the author's decision."
    },
    {
      "date": "2026-08-16",
      "note": "Reviewer Interface's source field corrected: 'organizational treatment in Series Three (forthcoming)' replaced with 'organizational treatment in Series Three', dropping the stale forthcoming status now that all four Series Three articles are published. Unlike Enterprise Experience Architect's fix above, this citation stays series-level rather than pinning to a single article — this term's definition makes no single-article promise the way Enterprise Experience Architect's did. The leading 'Series One · Article 2' clause (where the term was originally coined) is unchanged. Source-field correction only — definition, seeAlso, firstPublished, sourceUrl, and category unchanged; term count and slug unchanged. Closes Build Ledger item 36 in full."
    },
    {
      "date": "2026-08-16",
      "note": "workedExample gained one added sentence, cross-linking forward to the new Experience Architecture Maturity Model object (Standard object 11, draft) — the structured mechanism/symptoms/next-move reference table this walkthrough's own narrative diagnosis only implied, built the same session. Additive only: the existing walkthrough paragraph is unchanged, word for word, aside from the one new closing sentence. No terms added, changed, or removed; version unchanged, same precedent as this term's own 2026-07-01 category-field addition and the two source-field fixes above."
    },
    {
      "date": "2026-08-16",
      "note": "The Authority Audit's definition gained one added sentence, cross-linking forward to the new Authority Audit object (Standard object 3, draft) — the structured five-question table with 'what a failing answer sounds like' phrasing per question, content this term's own prose summary never carried. Additive only: the existing definition is unchanged, word for word, aside from the one new closing sentence. No terms added, changed, or removed; version unchanged, same precedent as the Maturity Model's own workedExample cross-link above."
    }
  ],
  "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.",
  "workedExample": "Read as a diagnosis rather than a summary, the Maturity Model's four stages are the Lexicon locating one organization on the ladder and naming each rung it climbed. Take an energy-trading firm that forked one terminal-status surface four ways across its regional desks — Ungoverned — where a single fork rendered a closed terminal as accepting cargo with a vessel already underway and the demurrage clock running: a Dark State, an operating condition no specification had ever named. Two peers in the same sector, running the same agent fleet, then split: the one that first ran a state inventory shipped clean and crossed into Constrained with an Agentic Constitution to build against, while the one that pointed its agents straight at the design system rendered an embargoed counterparty as clear to load — a sanctions state nobody had enumerated, caught only after the fact, at six figures in remediation, a regulator self-report, and a quarter under board scrutiny. Constrained is not the finish it feels like, since a constitution nobody defends drifts; the move to Instrumented is the Logic-Review Gate standing at the definition of ready, catching a deviation as a constraint check before the build instead of an incident after it. Compounding is the Continuous Learning Loop closing on its own — every regulatory change amended into the constitution before it can become the next Dark State — at which point the terms above have stopped being a glossary and become the instrument the diagnosis was run with. This walkthrough now has a structured companion: the same four stages as a self-diagnostic reference table — mechanism, observable symptoms, and next move per stage — at The Experience Architecture Maturity Model (Standard object 11).",
  "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": "The Authority Audit",
      "slug": "authority-audit",
      "source": "Series Three · Article 1",
      "definition": "A self-administered, five-question diagnostic that maps where binding AI-behavior decisions actually get made in an organization, and who holds the standing to make them: who ratifies a constraint set before it ships, who can halt a violating deployment, who is in the room when compliance and legal set policy, who owns the constitution when its author leaves, and whose performance review is affected when an ungoverned surface causes an incident. Designed to be run standalone, without reading the source article. Each question now has a structured companion: the same five questions paired with concrete 'what a failing answer sounds like' phrasing, at The Authority Audit (Standard object 3).",
      "category": "governance",
      "seeAlso": [
        "governance-vacancy",
        "enterprise-experience-architect",
        "agentic-constitution"
      ],
      "firstPublished": "2026-07-25",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/someone-just-asked-who-governs-your-ai-your-org-chart-has-no-answer-f332044f64d9"
    },
    {
      "term": "Blast Radius",
      "slug": "blast-radius",
      "source": "Series Three · Article 1 — career-ladder treatment due Article 4",
      "definition": "The breadth of surfaces governed by a practitioner's specification authority — the seniority axis paired with Specification Authority. Also used to describe risk-tiering: ratification requirements scale to blast radius, so low-risk assistive copilots keep moving through standard agile process rather than requiring the same ceremony as high-blast-radius autonomous agents.",
      "category": "mechanics",
      "seeAlso": [
        "specification-authority",
        "governance-vacancy"
      ],
      "firstPublished": "2026-07-25",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/someone-just-asked-who-governs-your-ai-your-org-chart-has-no-answer-f332044f64d9"
    },
    {
      "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 — extended to override telemetry in Series Three, Article 3",
      "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. Series Three applies the same mechanism to a second telemetry stream: override events, where a squad overrides a governed constraint, resolved to a shared versioned constraint ID and aggregated into a single log. The Amendment Protocol's structural signal — three squads overriding the same constraint independently — is matched across that log rather than across the org chart; without centralized override telemetry it is undetectable by construction.",
      "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 — promoted to a mechanism in Series Three, Article 3",
      "definition": "Originally named in Series One and Series Two as an organizational risk — senior practitioners resisting the shift from a production role to a validation role while the metrics that reward them still count screens produced, not specifications governed; a leadership and incentive-design problem, not a training problem. Series Three promotes that risk to a mechanism: the standing, executive-backed authority to halt a live deployment running against an uncertified constraint set. It holds on three conditions — executive air cover above the squad's delivery leadership, so a halt lasts until the constraint set is certified, not until the sponsor is available; cross-silo diplomacy, in which squads author their own constraints against a schema the authority supplies and it certifies, returns, or amends rather than co-authors; and a fallback state ratified at certification time, so a halt degrades rather than detonates. Distinct from the emergency technical stop: this governs what happens after the bleeding stops.",
      "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, Article 4",
      "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": "The Governance Vacancy",
      "slug": "governance-vacancy",
      "source": "Series Three · Article 1",
      "definition": "The org-design diagnosis at the center of Series Three: the org chart has no slot for the function that owns the Agentic Constitution — no seat with the standing to ratify it, enforce it, or sit alongside compliance, operations, and legal when binding decisions about system behavior are made. Not a design-credibility gap or a talent shortage; a seat that was never built. Interchangeable in running text with 'the org-design vacancy' and 'the empty seat.'",
      "category": "governance",
      "seeAlso": [
        "authority-audit",
        "enterprise-experience-architect",
        "agentic-constitution"
      ],
      "firstPublished": "2026-07-25",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/someone-just-asked-who-governs-your-ai-your-org-chart-has-no-answer-f332044f64d9"
    },
    {
      "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": "The Provisional Surface",
      "slug": "provisional-surface",
      "source": "Series Three · Article 1 — enforcement mechanism delivered in Article 3",
      "definition": "A 'temporary' agent behavior or interface shipped to hit a deadline and never replaced — functionally an unratified amendment to the constitution, deployed straight to production.",
      "category": "governance",
      "seeAlso": [
        "agentic-constitution",
        "governance-vacancy"
      ],
      "firstPublished": "2026-07-25",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/someone-just-asked-who-governs-your-ai-your-org-chart-has-no-answer-f332044f64d9"
    },
    {
      "term": "Reviewer Interface",
      "slug": "reviewer-interface",
      "source": "Series One · Article 2 — organizational treatment in Series Three",
      "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": "Specification Authority",
      "slug": "specification-authority",
      "source": "Series Three · Article 1 — career-ladder treatment due Article 4",
      "definition": "The substantive measure of seniority in this discipline — the scope of the constitution a practitioner is empowered to ratify and enforce. Replaces 'screens shipped' as the career-ladder metric.",
      "category": "roles",
      "seeAlso": [
        "blast-radius",
        "governance-vacancy",
        "enterprise-experience-architect"
      ],
      "firstPublished": "2026-07-25",
      "sourceUrl": "https://medium.com/enterprise-experience-architecture/someone-just-asked-who-governs-your-ai-your-org-chart-has-no-answer-f332044f64d9"
    },
    {
      "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"
    }
  ]
}