<!--
V7-HEADER
Title:     MamaDEX — Evidence-Source Map
Filename:  mamadex-locations.html
Path:      /mamadex/mamadex-locations.html
Version:   v0.9.0-prototype
Issued:    2026-07-15
Author:    Buktika Webdesk (Binka)
Purpose:   The MamaDEX evidence-source selection map. Correct sequence: South
           Africa map -> active Mama pins -> select a Mama -> see her story
           and canonically resolved centre -> inspect published Evidence
           Packs associated with that centre. This page does NOT own the
           Mama directory/grid — that is /mamadex/mamadex-mamas.html and
           stays untouched by this build. The centre registry is used only
           to resolve a selected Mama's canonical centre relationship; it
           never determines which pins appear on the map (see
           mamadex-locations.js v0.7.0-prototype header for the full
           rationale).
Status:    PROTOTYPE.
Map rule:  Pin source is the ACTIVE Mama roster (assets/data/mamadex/
           mamadex-mamas.roster.json) — same model as the accepted
           /mamadex/mamadex-mamas.html map. iso=ZA (or resolved default) ->
           flat South Africa map with active Mama pins. No ISO, or more than
           one ISO -> world/globe placeholder state (honestly labelled "not
           yet built"). The centre registry (assets/data/mamadex/
           mamadex-centres.registry.json) is read ONLY after a Mama pin is
           selected, to resolve her canonical centre.
Query params read: iso, channels, trigger_id, path (or intent, tolerated as
           an alias), eco_programme_type, centre_id, mama.
Changelog:
  v0.9.0-prototype — 2026-07-15 — BUILD THE SHARED RELATIONSHIP POPUP ENGINE (owner
    instruction). REMOVED the bespoke #mdl-card DOM element entirely (portrait/identity/
    quote/centre-state/CTA markup built earlier the same day, v0.8.0). The selected-Mama
    popup now renders through the shared relationship-popup-engine.js (SDXRelationshipPopup)
    inside #sdx-stage — the SAME engine now used by Eco Guilds and Viridians — fed by the new
    mamadex-relationship-popup.sidecar.js. Per the owner's explicit instruction ("Do not make
    the MamaDEX popup a separate portrait-card layout. The portrait fits within the shared
    relationship-block system."), the Mama's portrait is now the media slot of the "MamaDEX"
    relationship block (2x2 grid, first position) rather than a full-width hero image. Map
    geometry, pin count/positions, the "?" help control, context-routing and centre
    resolution are all UNCHANGED — only the selected-Mama popup's rendering mechanism moved.
  v0.8.0-prototype — 2026-07-15 — REDESIGN THE MAMA SELECTION PANE (owner
    instruction, "Human-first card"). Scope: the selected-Mama pane
    (#mdl-card) ONLY — map geometry, pin count/positions, the "?" help
    control, context-routing, centre resolution, and Evidence Pack routing
    are all UNCHANGED. REMOVED the broken stacked top-left label fragment
    (a bare kicker line above the title that could visually fragment a long
    name). REBUILT the pane's visual order to portrait -> identity (eyebrow
    "MamaDEX Mama" + full name + location) -> story quote -> centre/Evidence
    Pack state -> actions, so the woman is the first thing a visitor sees,
    not routing/centre metadata. ADDED a full-width 4:3 portrait
    (#mdl-card-portrait, same canonical roster image path already used —
    unchanged from v0.7.0). ADDED a dedicated top bar for the close control
    so it never overlaps the portrait, with a 44x44px hit target. The story
    line is now a simple left-rule quote instead of a heavily tinted box.
    The missing-centre state is now a quiet status row ("Centre and Evidence
    Pack route — Not yet published for this Mama" + a reassuring body line)
    instead of a dashed warning panel; it no longer implies rejection,
    inactivity, or failed verification. CTA hierarchy corrected: "View full
    profile" is now the PRIMARY action (canonical .sdx-btn-primary, MamaDEX
    violet), "View Evidence Packs from this Centre" is now SECONDARY
    (.sdx-btn-secondary, shown only when a canonical centre resolves), "Back
    to MamaDEX overview" stays a restrained tertiary text link. See
    mamadex-locations.css v0.6.0-prototype and mamadex-locations.js
    v0.8.0-prototype for the full styling/behaviour rationale.
  v0.7.0-prototype — 2026-07-14 — CORRECT THE EVIDENCE-SOURCE MAP (owner
    instruction: "the current mamadex-locations.html evidence-route map is
    not accepted... it uses the centre registry as the pin source, rendering
    only two pins"). REMOVED: the centre-registry-driven pin markup, the
    tagline ("Choose a centre to see its story and proof route."), the
    #mdl-country-label/#mdl-country-note "Selected country: South Africa"
    block, and the #mdl-route-badge "mdx · evidence-pack" badge — all
    replaced by a restrained heading ("Choose where to begin") + one short
    instruction line, with the country/help copy moved into a new "?" help
    control (SDXStage panel, same pattern as mamadex-mamas.html) instead of
    living permanently above the map. ADDED: i18n wiring (this page
    previously had none) — i18next + i18nextHttpBackend + i18n-core-loader,
    data-i18n attributes throughout, namespace 'mamadex-locations' derived
    by language-switcher.js from the .page-mamadex-locations body class (see
    /i18n/mamadex/mamadex-locations/<locale>.json). ADDED: sdx-stage-plugin-
    partial.js (required by the new "?" help control's SDXStage panel).
    REPLACED the four-block (ECO GUILD/MAMADEX/REPORTERS/EDUTOWER) centre-led
    card with a Mama-led card: portrait, kicker (broad location), title
    (Mama name), short public story context (roster "slogan" field),
    canonical centre block OR an honest "not yet available" state, a
    profile-link CTA, and an "Evidence Packs from this Centre" CTA shown only
    when a canonical centre resolves. See mamadex-locations.js's own
    v0.7.0-prototype changelog for the full pin-source/card/help-control
    rationale.
  v0.6.0-prototype — 2026-07-14 — FIX: "Missing iso ≠ unsupported country".
  v0.5.0-prototype — 2026-07-14 — BKT 35120 v2.1.0 corrective fix.
  v0.4.0-prototype — 2026-07-10 — ROUTE-RESUME LAYER WIRED.
  v0.3.0-prototype — 2026-07-09 — UGDA audit compliance.
  v0.2.0-prototype — 2026-07-09 — Visual correction to match existing
    MamaDEX map look.
  v0.1.0-prototype — 2026-07-09 — Initial prototype build.
License:   © Buktika, 2026. All rights reserved.
-->

<!doctype html>
<html lang="en-ZA" data-theme="light" data-locale="en-ZA">
<head>
  <script src="/assets/js/partials/auth-state.js?v=1.1.0"></script>
  <script>(function(){var t=localStorage.getItem('sdx-theme');var d=t||(matchMedia('(prefers-color-scheme:dark)').matches?'dark':'light');document.documentElement.setAttribute('data-theme',d);}());</script>
  <meta charset="utf-8">
  <title data-i18n="mamadex_locations.page_title">MamaDEX Evidence-Source Map — Choose Where to Begin | Buktika</title>
  <meta name="viewport" content="width=device-width,initial-scale=1">
  <meta name="description" content="Select a MamaDEX Mama to see her centre and available Human Restoration evidence.">
  <link rel="icon" href="/favicon.ico" sizes="any">

  <link rel="stylesheet" href="/assets/css/global.css?v=3.16.0">
  <link rel="stylesheet" href="/assets/css/themes.css?v=2.5.0">
  <link rel="stylesheet" href="/assets/css/partials/header.css">
  <link rel="stylesheet" href="/assets/css/partials/footer.css?v=4.9.3">
  <link rel="stylesheet" href="/assets/css/partials/sdx-stage.css?v=3.2.1">
  <!-- Shared relationship-popup engine (cross-pillar lego block; same engine Eco Guilds and
       Viridians use). Supersedes this page's own bespoke #mdl-card styling (BUILD THE SHARED
       RELATIONSHIP POPUP ENGINE, 2026-07-15). -->
  <link rel="stylesheet" href="/assets/css/partials/relationship-popup.css?v=1.10.0">
  <link rel="stylesheet" href="/assets/css/mamadex/mamadex-locations.css?v=0.8.1">
  <!-- Route-resume dock (shared partial, unchanged filename/classes this pass) — v0.4.0. -->
  <link rel="stylesheet" href="/assets/css/partials/sdx-resume-dock.css?v=1.2.0">

  <!-- Tippy + MapLibre: pin hover preview / map engine — same libraries the
       accepted mamadex-mamas.html map uses, via the shared
       mamadex-mama-pins.js pin module. -->
  <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/tippy.js@6.3.7/dist/tippy.css">
  <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/tippy.js@6.3.7/animations/shift-away-subtle.css">
  <link href="https://unpkg.com/maplibre-gl@5.13.0/dist/maplibre-gl.css" rel="stylesheet">

  <!-- i18n: language-switcher.js derives namespace 'mamadex-locations' from
       body class .page-mamadex-locations ('mamadex-' prefix) to
       /i18n/mamadex/mamadex-locations/<locale>.json. NEW this pass — this
       page previously had no i18n wiring at all. -->
</head>

<body class="page-mamadex-locations" data-i18n-extra-namespaces="relationship-popup">
  <div id="site-header" role="banner" data-include="/partials/header.html"></div>

  <!-- Map hero — same shell pattern as mamadex-mamas-map.html: hero band,
       centred content column, restrained headline + one short instruction
       above the map (v0.7.0-prototype: verbose routing copy, the country
       label/note, and the route badge all removed — see the "?" help
       control instead). The map and the Mama-led card are flex SIBLINGS
       inside .mdl-map-row, not overlay/child of the MapLibre container, so
       the card can never be clipped by the map viewport. -->
  <div id="mdl-map-section" class="hero-wrap">
    <section class="hero hero-mdl-map" aria-label="MamaDEX evidence-source map" data-i18n-aria="mamadex_locations.hero.aria">
      <div class="hero-inner">

        <div class="hero-title">
          <h1 class="headline" data-i18n="mamadex_locations.hero.title">Choose where to begin</h1>
          <p class="tagline" data-i18n="mamadex_locations.hero.instruction">Select a Mama to see her centre and available Human Restoration evidence.</p>
        </div>

        <div class="mdl-map-row">
          <div id="mdl-map-container" aria-label="South Africa map container" data-i18n-aria="mamadex_locations.map.container_aria">
            <div id="mdl-map" aria-label="MamaDEX Mamas map"></div>

            <div class="mdl-empty" id="mdl-empty" role="status" aria-live="polite" hidden>
              <span class="mdl-empty__label" id="mdl-empty-label">No Mamas to show</span>
              <span class="mdl-empty__body" id="mdl-empty-body"></span>
            </div>
          </div>

          <!-- Selected-Mama relationship popup — v1.0.0 (owner instruction, "BUILD THE
               SHARED RELATIONSHIP POPUP ENGINE", 2026-07-15). Renders through the shared
               SDXRelationshipPopup engine inside #sdx-stage (relationship-popup-engine.js +
               mamadex-relationship-popup.sidecar.js), the SAME engine Eco Guilds and
               Viridians use — this page no longer owns a bespoke #mdl-card DOM element.
               See mamadex-locations.js openMamaCard() for the resolve+open call. Map
               geometry, pins, help control, context-routing and centre resolution are
               unchanged by this pass. -->
        </div>

        <p class="mdl-hint" id="mdl-hint"></p>

      </div>
    </section>
  </div>

  <main></main>

  <div id="site-footer" role="contentinfo" data-include="/partials/footer.html"></div>

  <!-- MAPLIBRE REPAIR (2026-07-15, shared popup visual-contract repair, §A): this whole
       block is now REORDERED to be byte-for-byte the same relative sequence as the accepted,
       working /mamadex/mamadex-mamas.html (and eco-guilds-farms.html, the engine's other
       working MapLibre + relationship-popup consumer) — i18next/popper/tippy synchronous
       FIRST, then every deferred script in the exact same relative order those accepted pages
       use, with maplibre-gl.js positioned immediately before the page's own map controller.
       Root-cause note: the maplibre-gl.js <script> tag itself was already byte-identical to
       the accepted pages' (same CDN URL, same defer attribute, same version) — this page's
       defect was that it had drifted into its OWN bespoke script arrangement (i18next moved to
       the very end of the body; popper/tippy-bundle split away from includes.js/language-
       switcher.js; the relationship-popup engine pair inserted mid-sequence) across several
       rewrite passes (v0.1.0 through v0.10.0-prototype), instead of reusing the one accepted
       loader/include arrangement verbatim. mamadex-locations.js's own v0.10.0-prototype
       bootWhenReady() retry loop was a workaround layered ON TOP of that drift rather than a
       fix for it — see mamadex-locations.js's changelog for its replacement, which now reuses
       the accepted mamadex-mamas-map.js guard byte-for-byte instead of a second, drifted copy. -->
  <script src="https://unpkg.com/i18next@23.15.1/dist/umd/i18next.min.js"></script>
  <script src="/assets/js/i18n/i18nextHttpBackend.min.js?v=2.5.2" defer></script>
  <script src="https://unpkg.com/@popperjs/core@2.11.8/dist/umd/popper.min.js"></script>
  <script src="https://unpkg.com/tippy.js@6.3.7/dist/tippy-bundle.umd.min.js"></script>
  <script src="/assets/js/includes.js?v=2.0.1" defer></script>
  <script src="/assets/js/partials/language-switcher.js?v=2.5.4" defer></script>
  <script src="/assets/js/i18n/i18n-core-loader.js?v=1.7.0" defer></script>

  <!-- SDXStage: floating help panel opened by the map's "?" control (same
       pattern as mamadex-mamas.html / eco-guilds), PLUS the shared relationship-popup
       engine (content_type 'dynamic') opened on Mama-pin selection. -->
  <script src="/assets/js/partials/sdx-stage.js?v=3.7.0" defer></script>
  <script src="/assets/js/partials/sdx-stage-plugin-partial.js?v=1.0.0" defer></script>
  <script src="/assets/js/partials/sdx-stage-plugin-dynamic.js?v=1.0.0" defer></script>
  <script src="/assets/js/partials/relationship-popup-engine.js?v=2.5.0" defer></script>
  <!-- Public Storybook Viewer and Relationship Popup Integration work item, Section 16: the
       lawful entity-to-Storybook discovery client. Loaded as a module (see storybooks/storybook.html
       for the same convention) since it uses import/export for bun:test; attaches
       window.SDXStorybookEntityIndexClient for the plain-script sidecar below to consume. -->
  <script type="module" src="/assets/js/partials/storybook-entity-index-client.js?v=1.0.0"></script>
  <script src="/assets/js/mamadex/partials/mamadex-relationship-popup.sidecar.js?v=1.4.0" defer></script>

  <!-- Shared Mama-pin module (extracted from the accepted mamadex-mamas-
       map.js's own pin/jitter/tooltip logic) — must load before
       mamadex-locations.js, same relative position as mamadex-mamas-grid.js
       on the accepted map page. MapLibre itself loads immediately after,
       directly mirroring the accepted page's own ordering. -->
  <script src="/assets/js/mamadex/partials/mamadex-mama-pins.js?v=1.0.0" defer></script>
  <script src="https://unpkg.com/maplibre-gl@5.13.0/dist/maplibre-gl.js" defer></script>
  <!-- Shared map-runtime readiness poll (POINT 8, "SHARED POPUP VISUAL PARITY — REAL DEFECT PASS") —
       must load before mamadex-locations.js, which calls window.BTKMapRuntimeReady.wait(). Same
       module mamadex-mamas-map.js now uses — no more copied bootWhenReady() guards. -->
  <script src="/assets/js/partials/btk-map-runtime-ready.js?v=1.0.0" defer></script>
  <script src="/assets/js/mamadex/mamadex-locations.js?v=0.14.0" defer></script>

  <!-- Route resume — v0.4.0, unchanged by this pass. mamadex-locations.js
       still dispatches 'mamadex:centre-selected' when a resolved centre's
       Evidence Pack CTA is chosen from the Mama card. -->
  <script src="/assets/js/partials/sdx-resume-dock.js?v=1.1.0" defer></script>
  <script src="/assets/js/partials/btk-route-resume-engine.js?v=1.0.0" defer></script>
  <script src="/assets/js/mamadex/mamadex-route-resume.js?v=1.2.1" defer></script>
</body>
</html>