Wave 9 Dashboards — Data Map

The boards beyond the Leadership Dashboard: the derivation tree and the candidate pipeline · companion to the Leadership Dashboard's own Data Map

The derivation tree

Nine boards are generated from the gold Leadership Dashboard's HTML, not built from the raw sources. The gold file is the single source of truth: its embedded dataset is re-scoped and re-embedded, so the derived boards can never disagree with it — and they all go stale together until regenerated.

Thrive Wave 9 Engagement Leadership Dashboard.html THE GOLD COPY 20 engagements · 257 councils of PMP contacts · map geometry · logo (see its own Data Map for its sources) split at const DATA= same seam DERIVE — build_ws_dashboards.py • scope UI to one workstream's 5 slots • keep all 20 embedded — "Wave 9"   medians stay wave-wide & honest • drop Map tab + geometry (−200 KB) • drop workstream labels (redundant) • 2025 PMP column: rating pill only script preserved in Code/ · every patch anchor asserted — drift fails loudly DERIVE — per-engagement • scope to one engagement / lodge • tabs: Engagement · PMP — Lodge   (if a lodge is named) · PMP — National • Word/PDF brief generated alongside generator not preserved (dashed) — spec in the Developer Reference emits 4 Workstream 1 Dashboard.html Foose & Frederick Workstream 2 Dashboard.html Ferdig & Bonnet Workstream 3 Dashboard.html Johnson & Corr Workstream 4 Dashboard.html Hunt & Singletary same tabs minus Map · verified by verify_ws_dashboards.py emits 5 Engagement Dashboard — Mixti Wanaxe (720) Engagement Dashboard — Nentico (12) Engagement Dashboard — Wichita (35) Engagement Dashboard — Yokahu (506) Engagement Dashboard — Lester Lewis awaiting lodge WS3's five engagements · briefs per named lodge in Briefs/
Solid boxes and arrows are preserved, re-runnable steps; the dashed generator's method is documented but its script was not kept. Rule of the tree: edit the gold copy, then regenerate everything to its right — never edit a derived file by hand.

The candidate pipeline

The staffing boards don't hang off the gold dashboard — they hang off the Engagement Preference Form (EPF) responses in Asana, normalized once and reused. The draft board's export is the one place this pipeline feeds back into the Leadership Dashboard.

Asana — Lead EPF responses 19 Engagement Lead applications, pasted from the Thrive project Asana — Partner tracker export "K - Wave 9 Partner Tracker" — 39 partner EPFs (.xlsx) NORMALIZE — one record set • free-text time zones → ET/CT/MT/PT • form typos fixed ("Unite Relations") • topics/roles → canonical matrices • missing conditional fields → flagged,   never guessed (caveat notes) same conventions for leads & partners same normalization, separate records Thrive Engagement Lead Candidates.xlsx filterable roster + Reference + Lodges fit sheet regenerated by script, never hand-edited Thrive Draft Board.html Draft Board + Candidate Intel views · ran the 2026-08-18 live draft · state lives in the tab same records, two artifacts thrive-draft-results.csv the board's Export — now in Source Data/ Export on draft night Leadership Dashboard build lead e-mails & priors Wave 9 Engagement Partners.html Candidate-Intel-style board for the 39 EPFs 60 seats vs 39 in pool · no draft state records are embedded as JSON in each board — a rebuild can re-parse Asana or lift the JSON straight from the HTML
The dashed loop is the pipeline's one feedback edge: the draft board's export is how draft-night results reached the Leadership Dashboard. The workbook and draft board are twins from one record set — regenerate them together, and the lodge fit rules (own-lodge stop; section, size-band, time-zone, no-form warnings) are implemented in both and verified to agree.

Board → source map

Where each remaining board's data comes from, and what regenerates it.

BoardFolderData comes fromScope shownRegenerate when…
Workstream Dashboards (4)Workstream Dashboards/Gold dashboard HTML via build_ws_dashboards.py (in Code/) — full 20-engagement dataset re-embedded minus map geometryUI scoped to that workstream's 5 engagements; "Wave 9" comparisons stay wave-wide…the gold dashboard is rebuilt, always — then run verify_ws_dashboards.py
Engagement Dashboards (5) + briefsEngagement Dashboards/Same gold data, per-engagement generator (script not preserved; spec in the Developer Reference)One engagement: its lodge, team, and lodge PMP vs national…the gold dashboard is rebuilt, or a WS3 engagement's staffing/lodge changes
Thrive Draft BoardDraft Board/Normalized lead EPF records embedded as JSON shared with the workbookAll 19 lead candidates + 20 slots; live state only in the open tab (Export before closing!)…lead applications change — regenerate board + workbook together
Lead Candidates workbookDraft Board/The same records via an openpyxl script (rows 3–62 contract; COUNTIF/SUMPRODUCT ranges)Roster, coverage counts, per-lodge "Leads Clearing Fit"…same trigger; never hand-edit — the script reflows the schema
Wave 9 Engagement PartnersEngagement Partners/Asana partner-tracker export, normalized; 39 records embedded as JSONThe partner pool vs 60 seats; caveats flagged on cards…a fresh partner export lands, or partner staffing begins

What the derived dashboards keep and drop

The design contract for anything generated from the gold copy.

Workstream DashboardsEngagement Dashboards
TabsEngagements · Lodge Detail · PMP — Workstream · PMP — NationalEngagement · PMP — Lodge (named lodges only) · PMP — National
DroppedMap tab + geometry; every per-row/per-card workstream label; the x/30 score in the 2025 PMP columnEverything outside the one engagement; the Map
Kept honest"Wave 9" medians, trajectory lines, and histogram ticks compute across all 20 engagements; the by-workstream chart keeps all 4 bars with its own highlightedNational benchmarks computed against all 257 reporting councils, same as the gold copy
NeverHand-edited. Draft slot numbers. Phone numbers. Source citations on-screen. Summed PMP for merged lodges (Combined always averages).

Rebuild triggers

One rule covers most of this page: gold first, derivatives second.

When this lands……this is redone
The gold Leadership Dashboard is rebuilt (new draft sheet, PMP year, leadership export…)Regenerate all 4 workstream dashboards (Code/build_ws_dashboards.py, then the verifier) and the 5 engagement dashboards
A lodge is named for one of the 4 open slotsGold rebuild → derivatives; the affected engagement dashboard gains its PMP — Lodge tab
Partners are officially staffedGold rebuild flips the 0-of-60 hold → derivatives; the Partners board becomes the assignment record
New lead or partner applicationsRegenerate the candidates workbook + draft board together, or the Partners board, from re-normalized records
A future draft round is runUse the draft board live; Export that night; the CSV lands in Source Data/ and feeds the next gold rebuild

Companions: Leadership Dashboard/Wave 9 Dashboard - Data Map (the gold copy's own sources), Wave 9 Dashboard - Data Sources.md (the provenance ledger), Wave 9 Dashboards - Build & Data Documentation (.md/.docx), and Wave 9 Dashboards - Developer Reference.md with the Code/ folder. This page is the map of the remaining boards; those are the ledgers.