<?xml version="1.0" encoding="UTF-8"?>
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1400 1320" font-family="'Source Serif Pro', 'Georgia', 'Times New Roman', serif">
  <title>El Mundo — The Methodology Itself</title>
  <desc>The meta-diagram. Six canonical steps from "Constructing Generative Metaphor Vocabularies for Distributed System Architecture" (Rodriguez and Graña, draft-rodriguez-grana-metaphor-vocabularies-00, §4), paired with the El Mundo worked example from §5, with the four anti-patterns from §4.8 as a side panel.</desc>

  <defs>
    <style type="text/css"><![CDATA[
      .doc-title { font-size: 22px; font-weight: 600; fill: #0f172a; }
      .doc-sub { font-size: 13px; font-weight: 400; fill: #475569; font-style: italic; }
      .citation { font-size: 11px; font-weight: 500; fill: #334155; font-family: 'Inter', 'Helvetica Neue', sans-serif; font-style: italic; }
      .tier-label { font-size: 12px; font-weight: 700; letter-spacing: 0.08em; text-transform: uppercase; fill: #475569; font-family: 'Inter', 'Helvetica Neue', sans-serif; }
      .step-num { font-size: 24px; font-weight: 800; fill: #ffffff; font-family: 'Inter', 'Helvetica Neue', sans-serif; }
      .step-name { font-size: 13px; font-weight: 700; font-style: italic; fill: #0f172a; }
      .step-text { font-size: 10.5px; fill: #1f2937; font-family: 'Inter', 'Helvetica Neue', sans-serif; }
      .step-fail { font-size: 10px; fill: #991b1b; font-family: 'Inter', 'Helvetica Neue', sans-serif; font-style: italic; }
      .example-name { font-size: 13px; font-weight: 700; font-style: italic; fill: #0f172a; }
      .example-text { font-size: 10.5px; fill: #334155; font-family: 'Inter', 'Helvetica Neue', sans-serif; }
      .panel-title { font-size: 13px; font-weight: 600; fill: #0f172a; font-family: 'Inter', 'Helvetica Neue', sans-serif; }
      .panel-text { font-size: 11px; fill: #334155; font-family: 'Inter', 'Helvetica Neue', sans-serif; }
      .footer { font-size: 10px; fill: #64748b; font-family: 'Inter', 'Helvetica Neue', sans-serif; }
      .step-card-fill { fill: #f8fafc; stroke: #1e40af; stroke-width: 1.5; }
      .example-card-fill { fill: #fff; stroke: #cbd5e1; stroke-width: 1.5; }
      .antipattern-fill { fill: #fef2f2; stroke: #b91c1c; stroke-width: 1.5; }
      .antipattern-title { font-size: 11.5px; font-weight: 700; fill: #991b1b; font-family: 'Inter', 'Helvetica Neue', sans-serif; font-style: italic; }
      .antipattern-text { font-size: 10px; fill: #991b1b; font-family: 'Inter', 'Helvetica Neue', sans-serif; }
      .scope-fill { fill: #fffbeb; stroke: #ca8a04; stroke-width: 1.5; }
      .scope-title { font-size: 11.5px; font-weight: 700; fill: #78350f; font-family: 'Inter', 'Helvetica Neue', sans-serif; font-style: italic; }
      .scope-text { font-size: 10px; fill: #78350f; font-family: 'Inter', 'Helvetica Neue', sans-serif; }
    ]]></style>
    <marker id="step-arrow" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="7" markerHeight="7" orient="auto">
      <path d="M 0 0 L 10 5 L 0 10 z" fill="#1e40af"/>
    </marker>
    <marker id="iter-arrow" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="9" markerHeight="9" orient="auto">
      <path d="M 0 0 L 10 5 L 0 10 z" fill="#7e22ce"/>
    </marker>
    <marker id="reject-arrow" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="9" markerHeight="9" orient="auto">
      <path d="M 0 0 L 10 5 L 0 10 z" fill="#b91c1c"/>
    </marker>
  </defs>

  <!-- Background -->
  <rect width="1400" height="1320" fill="#ffffff"/>

  <!-- Title -->
  <text x="60" y="44" class="doc-title">El Mundo — The Methodology Itself</text>
  <text x="60" y="64" class="doc-sub">Six canonical steps for constructing generative metaphor vocabularies, applied to El Mundo as worked example. The recipe transfers across</text>
  <text x="60" y="82" class="doc-sub">platforms and domains; the vocabulary it produces does not. Diagram 7 — The Methodology Itself.</text>

  <!-- Citation -->
  <text x="60" y="104" class="citation">Method canonically described in: R. Rodriguez and M. P. Graña, "Constructing Generative Metaphor Vocabularies for Distributed System Architecture," draft-rodriguez-graña-metaphor-vocabularies-00 (2026), §§4–5.</text>

  <!-- ============== TIER 1: THE SIX-STEP METHOD ============== -->
  <text x="60" y="140" class="tier-label">The Method — six canonical steps (I-D §4)</text>
  <line x1="60" y1="150" x2="1340" y2="150" stroke="#cbd5e1" stroke-width="1"/>

  <!-- Step cards: 200px wide, 16px gap, total span 1280px (60 to 1340) -->

  <!-- Step 1 -->
  <rect x="60" y="164" width="200" height="200" rx="10" class="step-card-fill"/>
  <circle cx="98" cy="200" r="20" fill="#1e3a8a"/>
  <text x="98" y="208" class="step-num" text-anchor="middle">1</text>
  <text x="76" y="246" class="step-name">Characterize</text>
  <text x="76" y="262" class="step-name">target architecture</text>
  <text x="76" y="284" class="step-text">Write down the system's principal</text>
  <text x="76" y="298" class="step-text">commitments (immutability, prov-</text>
  <text x="76" y="312" class="step-text">enance, audit, federation, etc.).</text>
  <text x="76" y="326" class="step-text">Inventory components — recognized</text>
  <text x="76" y="340" class="step-text">and anticipated. Output is the</text>
  <text x="76" y="354" class="step-text">basis for Step 3's mapping test.</text>

  <!-- Step 2 -->
  <rect x="276" y="164" width="200" height="200" rx="10" class="step-card-fill"/>
  <circle cx="314" cy="200" r="20" fill="#1e3a8a"/>
  <text x="314" y="208" class="step-num" text-anchor="middle">2</text>
  <text x="292" y="246" class="step-name">Identify candidate</text>
  <text x="292" y="262" class="step-name">source domains</text>
  <text x="292" y="284" class="step-text">Multiple candidates, not one.</text>
  <text x="292" y="298" class="step-text">Each evaluated on four properties:</text>
  <text x="292" y="312" class="step-text">internal richness, structural</text>
  <text x="292" y="326" class="step-text">articulation, historical depth,</text>
  <text x="292" y="340" class="step-text">connotational vitality.</text>
  <text x="292" y="354" class="step-text" font-style="italic">Comparison sharpens Step 3.</text>

  <!-- Step 3 -->
  <rect x="492" y="164" width="200" height="200" rx="10" class="step-card-fill"/>
  <circle cx="530" cy="200" r="20" fill="#1e3a8a"/>
  <text x="530" y="208" class="step-num" text-anchor="middle">3</text>
  <text x="508" y="246" class="step-name">Test source-target</text>
  <text x="508" y="262" class="step-name">mapping</text>
  <text x="508" y="284" class="step-text">For each component, does the</text>
  <text x="508" y="298" class="step-text">candidate offer a defensible match?</text>
  <text x="508" y="312" class="step-text">Three failure modes:</text>
  <text x="508" y="328" class="step-fail">·  coverage failure</text>
  <text x="508" y="340" class="step-fail">·  strain</text>
  <text x="508" y="352" class="step-fail">·  inversion</text>

  <!-- Step 4 -->
  <rect x="708" y="164" width="200" height="200" rx="10" class="step-card-fill"/>
  <circle cx="746" cy="200" r="20" fill="#1e3a8a"/>
  <text x="746" y="208" class="step-num" text-anchor="middle">4</text>
  <text x="724" y="246" class="step-name">Adopt or reject</text>
  <text x="724" y="284" class="step-text">Adoption is a substantive</text>
  <text x="724" y="298" class="step-text">commitment — vocabulary used</text>
  <text x="724" y="312" class="step-text">throughout, no translation drift.</text>
  <text x="724" y="334" class="step-text">Rejection is legitimate. Defer</text>
  <text x="724" y="348" class="step-text">vocabulary if no candidate is</text>
  <text x="724" y="362" class="step-text">strong; document the reasoning.</text>

  <!-- Step 5 -->
  <rect x="924" y="164" width="200" height="200" rx="10" class="step-card-fill"/>
  <circle cx="962" cy="200" r="20" fill="#1e3a8a"/>
  <text x="962" y="208" class="step-num" text-anchor="middle">5</text>
  <text x="940" y="246" class="step-name">Apply iteratively</text>
  <text x="940" y="284" class="step-text">Ongoing practice, not one-time</text>
  <text x="940" y="298" class="step-text">renaming. New components consult</text>
  <text x="940" y="312" class="step-text">the source domain for their</text>
  <text x="940" y="326" class="step-text">institutional name. Repeated</text>
  <text x="940" y="340" class="step-text">generation failure suggests the</text>
  <text x="940" y="354" class="step-text">source domain may be wrong.</text>

  <!-- Step 6 -->
  <rect x="1140" y="164" width="200" height="200" rx="10" class="step-card-fill"/>
  <circle cx="1178" cy="200" r="20" fill="#1e3a8a"/>
  <text x="1178" y="208" class="step-num" text-anchor="middle">6</text>
  <text x="1156" y="246" class="step-name">Document the</text>
  <text x="1156" y="262" class="step-name">lexicon canonically</text>
  <text x="1156" y="284" class="step-text">Versioned, single canonical</text>
  <text x="1156" y="298" class="step-text">location, conventions for use.</text>
  <text x="1156" y="312" class="step-text">Each term: source institution,</text>
  <text x="1156" y="326" class="step-text">target component, rationale,</text>
  <text x="1156" y="340" class="step-text">nuances. Derivative documents</text>
  <text x="1156" y="354" class="step-text">reference the version they reflect.</text>

  <!-- Step 1↔2 parallel indicator (the canonical text says they may be done in either order) -->
  <path d="M 260 218 Q 268 200 276 218" fill="none" stroke="#94a3b8" stroke-width="1.5" stroke-dasharray="3,2"/>
  <path d="M 260 264 Q 268 282 276 264" fill="none" stroke="#94a3b8" stroke-width="1.5" stroke-dasharray="3,2"/>
  <text x="268" y="166" font-size="9" fill="#64748b" font-style="italic" text-anchor="middle" font-family="'Inter', 'Helvetica Neue', sans-serif">parallel</text>

  <!-- Inter-step arrows (steps 2→3, 3→4, 4→5, 5→6) -->
  <line x1="476" y1="240" x2="492" y2="240" stroke="#1e40af" stroke-width="1.5" marker-end="url(#step-arrow)"/>
  <line x1="692" y1="240" x2="708" y2="240" stroke="#1e40af" stroke-width="1.5" marker-end="url(#step-arrow)"/>
  <line x1="908" y1="240" x2="924" y2="240" stroke="#1e40af" stroke-width="1.5" marker-end="url(#step-arrow)"/>
  <line x1="1124" y1="240" x2="1140" y2="240" stroke="#1e40af" stroke-width="1.5" marker-end="url(#step-arrow)"/>

  <!-- "Iterative — steps 3-5 may cycle" loop -->
  <path d="M 1024 376 Q 800 410 800 376" fill="none" stroke="#7e22ce" stroke-width="2" stroke-dasharray="6,4" marker-end="url(#iter-arrow)"/>
  <text x="900" y="404" font-size="10.5" fill="#7e22ce" font-style="italic" text-anchor="middle" font-family="'Inter', 'Helvetica Neue', sans-serif">Steps 3–5 are iterative — early candidates may be rejected after substantial work.</text>

  <!-- Step 4 reject branch - back to Step 2 (rejection means re-identify candidates) -->
  <path d="M 740 386 Q 740 432 380 432 Q 376 432 376 376" fill="none" stroke="#b91c1c" stroke-width="1.5" stroke-dasharray="4,3" marker-end="url(#reject-arrow)"/>
  <text x="540" y="450" font-size="10" fill="#b91c1c" font-style="italic" text-anchor="middle" font-family="'Inter', 'Helvetica Neue', sans-serif">If reject: return to Step 2 with new candidates, or defer.</text>

  <!-- ============== TIER 2: EL MUNDO WORKED EXAMPLE ============== -->
  <text x="60" y="488" class="tier-label">Worked Example — El Mundo (I-D §5)</text>
  <line x1="60" y1="498" x2="1340" y2="498" stroke="#cbd5e1" stroke-width="1"/>

  <!-- Example 1: Target architecture -->
  <rect x="60" y="512" width="200" height="200" rx="10" class="example-card-fill"/>
  <text x="76" y="534" class="example-name">Commitments listed</text>
  <text x="76" y="556" class="example-text">Append-only preservation;</text>
  <text x="76" y="570" class="example-text">original timestamps + units</text>
  <text x="76" y="584" class="example-text">verbatim; full provenance;</text>
  <text x="76" y="598" class="example-text">conflicts-as-conflicts (not</text>
  <text x="76" y="612" class="example-text">silent reconciliation); SOC 2</text>
  <text x="76" y="626" class="example-text">as natural expression; multi-</text>
  <text x="76" y="640" class="example-text">tenant cloud + on-prem +</text>
  <text x="76" y="654" class="example-text">optional federation.</text>
  <text x="76" y="676" class="example-text" font-style="italic">11+ component categories</text>
  <text x="76" y="690" class="example-text" font-style="italic">inventoried (sensors, ledgers,</text>
  <text x="76" y="704" class="example-text" font-style="italic">notary, archive, exchange, etc.).</text>

  <!-- Example 2: Candidates -->
  <rect x="276" y="512" width="200" height="200" rx="10" class="example-card-fill"/>
  <text x="292" y="534" class="example-name">Candidates considered</text>
  <text x="292" y="556" class="example-text">Generic-city geography</text>
  <text x="292" y="570" class="example-text">Medieval European guilds</text>
  <text x="292" y="584" class="example-text">19th-century railroad ops</text>
  <text x="292" y="598" class="example-text">Post-industrial logistics</text>
  <text x="292" y="612" class="example-text" font-weight="700" fill="#1e3a8a">Rural Spanish-American pueblo</text>
  <text x="292" y="640" class="example-text" font-style="italic">All five tested in Step 3.</text>
  <text x="292" y="654" class="example-text" font-style="italic">Connotational vitality matched</text>
  <text x="292" y="668" class="example-text" font-style="italic">team's bilingual context</text>
  <text x="292" y="682" class="example-text" font-style="italic">(Argentine Spanish; oilfield</text>
  <text x="292" y="696" class="example-text" font-style="italic">engineering practice).</text>

  <!-- Example 3: Mapping test -->
  <rect x="492" y="512" width="200" height="200" rx="10" class="example-card-fill"/>
  <text x="508" y="534" class="example-name">Mapping validations</text>
  <text x="508" y="556" class="example-text">append-only ↔</text>
  <text x="508" y="568" class="example-text" font-style="italic" fill="#1e3a8a">  pulpería + cabildo</text>
  <text x="508" y="586" class="example-text">provenance ↔</text>
  <text x="508" y="598" class="example-text" font-style="italic" fill="#1e3a8a">  posta (relay+authority)</text>
  <text x="508" y="616" class="example-text">conflict-as-conflict ↔</text>
  <text x="508" y="628" class="example-text" font-style="italic" fill="#1e3a8a">  careo + árbitro</text>
  <text x="508" y="646" class="example-text">notarization ↔</text>
  <text x="508" y="658" class="example-text" font-style="italic" fill="#1e3a8a">  escribanía</text>
  <text x="508" y="676" class="example-text">accumulating identity ↔</text>
  <text x="508" y="688" class="example-text" font-style="italic" fill="#1e3a8a">  cartilla</text>
  <text x="508" y="704" class="example-text" font-style="italic">No coverage failure, strain, inversion.</text>

  <!-- Example 4: Adopt/Reject -->
  <rect x="708" y="512" width="200" height="200" rx="10" class="example-card-fill"/>
  <text x="724" y="534" class="example-name">Decisions</text>
  <text x="724" y="556" class="example-text" font-weight="700" fill="#1e3a8a">Adopted: rural pueblo.</text>
  <text x="724" y="578" class="example-text" font-weight="700" fill="#991b1b">Rejected:</text>
  <text x="724" y="592" class="example-text">·  generic-city — coverage</text>
  <text x="724" y="604" class="example-text">    OK but flat connotation</text>
  <text x="724" y="618" class="example-text">·  guilds — connotation rich</text>
  <text x="724" y="630" class="example-text">    but field/center coverage</text>
  <text x="724" y="642" class="example-text">    failure</text>
  <text x="724" y="660" class="example-text">·  railroad, logistics —</text>
  <text x="724" y="672" class="example-text">    less defensible across the</text>
  <text x="724" y="684" class="example-text">    component inventory</text>
  <text x="724" y="704" class="example-text" font-style="italic">Reasoning recorded in §5.2.</text>

  <!-- Example 5: Iterative application -->
  <rect x="924" y="512" width="200" height="200" rx="10" class="example-card-fill"/>
  <text x="940" y="534" class="example-name">Generative episodes</text>
  <text x="940" y="556" class="example-text">v2026-05-03 (D-015):</text>
  <text x="940" y="568" class="example-text">Methodology versioning</text>
  <text x="940" y="580" class="example-text">demanded a corporate ledger;</text>
  <text x="940" y="592" class="example-text">colonial accountancy supplied</text>
  <text x="940" y="604" class="example-text" font-style="italic" fill="#1e3a8a">Contaduría, Asiento, Cierre,</text>
  <text x="940" y="616" class="example-text" font-style="italic" fill="#1e3a8a">Plan de Cuentas.</text>
  <text x="940" y="638" class="example-text">v2026-05-07 (D-021):</text>
  <text x="940" y="650" class="example-text">Lifecycle-state model surfaced</text>
  <text x="940" y="662" class="example-text">in Diagram 5 design session;</text>
  <text x="940" y="674" class="example-text">no new terms — three primitives</text>
  <text x="940" y="686" class="example-text">absorbed the new commitments.</text>
  <text x="940" y="704" class="example-text" font-style="italic">Generation succeeded each time.</text>

  <!-- Example 6: Lexicon as artifact -->
  <rect x="1140" y="512" width="200" height="200" rx="10" class="example-card-fill"/>
  <text x="1156" y="534" class="example-name">Lexicon today</text>
  <text x="1156" y="556" class="example-text" font-weight="700" fill="#1e3a8a">v2026-05-07</text>
  <text x="1156" y="572" class="example-text">31 terms, 7 versions in 5 days.</text>
  <text x="1156" y="586" class="example-text">Append-only history; every</text>
  <text x="1156" y="600" class="example-text">refinement carries rationale.</text>
  <text x="1156" y="618" class="example-text">Decisions tracked separately</text>
  <text x="1156" y="632" class="example-text">(D-014, D-015, D-016, D-019,</text>
  <text x="1156" y="646" class="example-text">D-021).</text>
  <text x="1156" y="664" class="example-text">Conventions explicit:</text>
  <text x="1156" y="676" class="example-text">·  holism by default</text>
  <text x="1156" y="688" class="example-text">·  natural-Spanish keepers</text>
  <text x="1156" y="700" class="example-text">·  no customer-facing usage</text>

  <!-- Connecting dotted lines between method tier and example tier -->
  <line x1="160" y1="376" x2="160" y2="512" stroke="#cbd5e1" stroke-width="1" stroke-dasharray="2,3"/>
  <line x1="376" y1="376" x2="376" y2="512" stroke="#cbd5e1" stroke-width="1" stroke-dasharray="2,3"/>
  <line x1="592" y1="376" x2="592" y2="512" stroke="#cbd5e1" stroke-width="1" stroke-dasharray="2,3"/>
  <line x1="808" y1="376" x2="808" y2="512" stroke="#cbd5e1" stroke-width="1" stroke-dasharray="2,3"/>
  <line x1="1024" y1="376" x2="1024" y2="512" stroke="#cbd5e1" stroke-width="1" stroke-dasharray="2,3"/>
  <line x1="1240" y1="376" x2="1240" y2="512" stroke="#cbd5e1" stroke-width="1" stroke-dasharray="2,3"/>

  <!-- ============== TIER 3: ANTI-PATTERNS (left) and SCOPE (right) ============== -->

  <text x="60" y="752" class="tier-label">Anti-Patterns to Recognize and Resist (I-D §4.8)</text>
  <line x1="60" y1="762" x2="700" y2="762" stroke="#cbd5e1" stroke-width="1"/>

  <!-- Anti-pattern 1: Decoration over commitment -->
  <rect x="60" y="776" width="640" height="92" rx="8" class="antipattern-fill"/>
  <text x="80" y="798" class="antipattern-title">Decoration over commitment</text>
  <text x="80" y="818" class="antipattern-text">Colorful names adopted without architectural commitments encoded. Test: would removing the chosen name</text>
  <text x="80" y="832" class="antipattern-text">in favor of a generic English equivalent change anything about how engineers think about the component?</text>
  <text x="80" y="846" class="antipattern-text">If not, the term is decoration. Names must be load-bearing.</text>

  <!-- Anti-pattern 2: Blending under pressure -->
  <rect x="60" y="880" width="640" height="92" rx="8" class="antipattern-fill"/>
  <text x="80" y="902" class="antipattern-title">Blending under pressure</text>
  <text x="80" y="922" class="antipattern-text">When stranding occurs in Step 5, the team borrows from a second source domain rather than rejecting the</text>
  <text x="80" y="936" class="antipattern-text">strand or revisiting Step 4. Coherence degrades; the vocabulary returns to a conventional blended state.</text>
  <text x="80" y="950" class="antipattern-text">Resist by going back to Step 4.</text>

  <!-- Anti-pattern 3: Preciousness -->
  <rect x="60" y="984" width="640" height="76" rx="8" class="antipattern-fill"/>
  <text x="80" y="1006" class="antipattern-title">Preciousness</text>
  <text x="80" y="1026" class="antipattern-text">Treating the lexicon as inviolable; resisting necessary revision when the architecture evolves or a term</text>
  <text x="80" y="1040" class="antipattern-text">proves wrong in practice. Lexicons should be respected but not frozen. Step 6's versioning allows evolution.</text>

  <!-- Anti-pattern 4: Translation drift -->
  <rect x="60" y="1072" width="640" height="92" rx="8" class="antipattern-fill"/>
  <text x="80" y="1094" class="antipattern-title">Translation drift</text>
  <text x="80" y="1114" class="antipattern-text">Translated equivalents allowed into code or docs as a courtesy to readers unfamiliar with the source domain.</text>
  <text x="80" y="1128" class="antipattern-text">Translations strip the connotational weight that motivated the choice. Defense: refuse translation as a</text>
  <text x="80" y="1142" class="antipattern-text">discipline, accepting adoption friction on new readers.</text>

  <!-- Right side: scope and applicability notes -->
  <text x="720" y="752" class="tier-label">Scope and Applicability (I-D §4.1)</text>
  <line x1="720" y1="762" x2="1340" y2="762" stroke="#cbd5e1" stroke-width="1"/>

  <rect x="720" y="776" width="620" height="100" rx="8" class="scope-fill"/>
  <text x="740" y="798" class="scope-title">Small group, not solo or crowdsourced</text>
  <text x="740" y="818" class="scope-text">The method is intended for a small group of architects and engineers working together. Step 3's mapping</text>
  <text x="740" y="832" class="scope-text">judgments require collective reasoning about both the target architecture and the candidate source</text>
  <text x="740" y="846" class="scope-text">domain, and the judgments are partly aesthetic. Fully individual application produces brittle vocabulary;</text>
  <text x="740" y="860" class="scope-text">fully crowdsourced application produces incoherence.</text>

  <rect x="720" y="888" width="620" height="100" rx="8" class="scope-fill"/>
  <text x="740" y="910" class="scope-title">Architecture must be characterizable</text>
  <text x="740" y="930" class="scope-text">The method assumes the target architecture is sufficiently stable that its principal commitments can be</text>
  <text x="740" y="944" class="scope-text">characterized. Applying the method to an architecture still in flux produces vocabulary that may need</text>
  <text x="740" y="958" class="scope-text">substantial revision once the architecture stabilizes. Deferring vocabulary construction until the</text>
  <text x="740" y="972" class="scope-text">architecture is settled is generally preferable.</text>

  <rect x="720" y="1000" width="620" height="116" rx="8" class="scope-fill"/>
  <text x="740" y="1022" class="scope-title">Connotational preservation as a secondary argument</text>
  <text x="740" y="1042" class="scope-text">Vocabularies drawn from non-dominant linguistic traditions can preserve architectural commitments that</text>
  <text x="740" y="1056" class="scope-text">the dominant technical English vocabulary has worn smooth. The trade-off is adoption friction on readers</text>
  <text x="740" y="1070" class="scope-text">unfamiliar with the source domain. The I-D treats this as a feature, not a bug — connotational weight</text>
  <text x="740" y="1084" class="scope-text">is what makes the names load-bearing rather than decorative. Translation drift (anti-pattern, left) is</text>
  <text x="740" y="1098" class="scope-text">the principal threat to this property; teams should refuse translation as a deliberate discipline.</text>

  <!-- ============== BOTTOM NARRATIVE ============== -->
  <rect x="60" y="1188" width="1280" height="92" rx="8" fill="#f1f5f9" stroke="#cbd5e1" stroke-width="1"/>
  <text x="80" y="1212" class="panel-title">The Recipe Transfers; The Vocabulary Does Not</text>
  <text x="80" y="1232" class="panel-text">El Mundo's specific names — Pulpería, Cabildo, Posta, Diligencias — belong to this platform's metaphor and should not be lifted into other platforms. The <tspan font-style="italic">methodology</tspan> that</text>
  <text x="80" y="1246" class="panel-text">produced them, however, transfers cleanly: characterize the target, identify candidates honestly, test mappings rigorously, adopt or reject deliberately, apply iteratively, document</text>
  <text x="80" y="1260" class="panel-text">canonically. A different team in a different domain — healthcare records, supply chain, scientific instrumentation — applies the same six steps and arrives at its own coherent vocabulary,</text>
  <text x="80" y="1274" class="panel-text">drawn from whichever source domain its Step 3 finds defensible. The methodology is what survives. The lexicon is the artifact this methodology produced for this platform.</text>

  <!-- Footer -->
  <text x="60" y="1306" class="footer">El Mundo lexicon, version 2026-05-07 — Roderick Consulting Inc. and RGC Argentina S.A. — Diagram 7 — The Methodology Itself — Per draft-rodriguez-graña-metaphor-vocabularies-00 §§4–5</text>
</svg>
