Executive Explainer · September 16, 2026

The Rippel engagement, and a correction about our own data

The Command Center is live and gated. The Tuesday call with Bobby Milstein happened. The deck is built and unsent — and Bobby wrote this morning asking for links to share with his team. And the most important thing that changed this fortnight is not something we built — it is something we learned about what we had already built, after I told you twice that it was weaker than it is.

1 · The shift, in one page

Ten days ago I audited the live PHIT Scorecard and found 98 uses of hashVal() — a function that generates numbers deterministically from the county name. I told you that most of the composite PHIT Score was fabricated for any county where FFH is not operating, and that showing it to Bobby Milstein would be a credibility risk. That framing drove the whole Command Center design: show Domain H only, label everything else roadmap.

That framing was wrong, and you were right to keep pushing on it. A deeper read of the same file found what the first pass missed: 48 live federal API calls across 25 hosts, and — the part that matters — a deliberate three-tier provenance system that labels every field as LIVE, REAL·OFFLINE, or MODELED, with a hand-built cache of genuine published Census figures behind it.

The corrected read: the PHIT Scorecard is substantially real, and it is honest about the parts that are not. What looked like fabrication was mostly a documented fallback chain doing its job. The five genuinely generated metrics are named in section 2 and are worth fixing — but they are the exception, not the rule.

Why this matters for Rippel: we spent a week building a pitch around the idea that our data is thin and our honesty is the selling point. Half of that was right. The honesty is the selling point — but it is the honesty of a system that labels its own data quality field by field, not the honesty of admitting we have little. That is a materially stronger position, and it changes what we should say to Bobby.

2 · What our data actually is

48
Live API fetches in the PHIT Scorecard
25
Distinct data hosts (13 CDC datasets alone)
3
Provenance tiers, labelled per field
5
Metrics genuinely still generated

The three-tier system (Scorecard, line 9065)

TierWhat the user seesTag on the page
LIVEFetched in real time from the source APILIVE API (green)
REALGenuine published values from a hand-built offline cache — REAL_COUNTY_ACS_DATA, 50+ counties, each row carrying source:'ACS 2022 5-yr'REAL · OFFLINE (cyan)
MODELEDState-average proxy, when the county is in neither tier⚠️ MODELED (amber)

Pima shows poverty 13.7%, median income $64,324. Maricopa 11.5% and $78,396. Those are real published ACS figures sitting in the cache, not estimates.

Live sources actually wired

13 CDC datasets (PLACES, WONDER mortality, vaccination, injury) · CMS Provider Data Catalog and Care Compare · HRSA shortage areas · NPI Registry · SAMHSA treatment locator · BLS · USDA FNS · Census ACS · ArcGIS · Overpass · plus the Arizona state feeds (AZDHS, AZSHARE, DES, azcarecheck).

What is genuinely still generated

MetricCurrent sourceReal replacement
Life expectancy76.5 + (hashVal(county,120) % 10) / 2County Health Rankings annual CSV
Preventable hospitalisation45 + (hashVal(county,130) % 30)County Health Rankings
Voter turnout52 + (hashVal(county,99) % 25)MIT Election Lab county file
HS graduation rate82 + (hashVal(county,110) % 14)NCES / EDFacts ACGR
Domain F — activationNo Supabase query populates DEMO.ffhSupabase aggregation, real only where FFH operates
Domain F stays the honest gap. It is 35% of the composite and it cannot be faked or bought — it only becomes real in a place where members are actually doing things. That is not a weakness in the pitch. It is the pitch: it is the one block no public dataset contains, and the reason a pilot region matters.

The Census key — an upgrade, not a repair

None of the four api.census.gov calls carry a &key=, and Census now rejects keyless requests. I initially called this "broken in production." It is not. The live call fails, the page falls to the REAL·OFFLINE cache, and it says so on screen. Getting a key (free, ~15 min at api.census.gov/data/key_signup.html) upgrades cached counties to LIVE, and — the real win — rescues every county not in the Arizona-built cache. That includes most of Rippel's partner counties: Lehigh Valley, Palm Beach, King, Cook.

Caveat on my own work: I inspected the Deploy Ready copy, not the live repo copy. If certainty matters, diff them before acting.

3 · What shipped

ItemState
Rippel Command Center
/rippel-command-center/
LIVE Gated at tier:'admin' + noindexed. Incognito check verified — bounces to /gate/?next=. 20 panels: Ripple Simulator, partner registry (36 rows with county FIPS and each partner's own reported result), partner map, PHIT comparison leaderboard, outcomes-intersect scaffold, wiring plan, partnership ladder, run sheet, Dr. Rob explainers on every data panel.
Real scores for 18 Rippel communitiesLIVE PHIT Domain H computed in-browser from CDC PLACES (swc5-untb), using the Scorecard's own benchmark normalisation. Range 39.5–88.9. Morris County — Rippel's own front door — scores 86.4.
Two decksBUILT 10-slide detail deck and 7-slide on-screen deck, both with real CDC figures. Neither sent.
Ledger surfacesDONE Airtable record, Tech Command Center registry row, Showcase card (Section 15), Command Centers launcher tile.
Map basemapFIXED OpenStreetMap blocked our tiles under their Tile Usage Policy (403 "Access blocked"). Moved to Esri World Light Gray Canvas — no key, verified live.

4 · What's still open

ItemWhy it mattersEffort
Three PHIT Scorecard maps still on blocked OSM tilesSame 403 the Command Center had. Anyone opening the Scorecard sees "Access blocked" across the map. Highest-visibility fix on this list.~1 hr
Census API keyUpgrades REAL·OFFLINE → LIVE and rescues non-cached counties. Yours to request — it takes your name and email.15 min
Domain O from County Health RankingsOne CSV, one FIPS join. Kills the two largest generated numbers (life expectancy, preventable stays).~half day
Wedge 6 module not deployedRob's Reliable Transportation module is built (96 KB, games, tracker, meme kit) but never staged. Needs the Activator pass: real coin assets for 29 🪙 emoji, one base64 image, Clipboard, public nav, tag manifest. Health content also flagged DRAFT pending Rob's sign-off.~1 hr + Rob
/ffh-share-it-studio/ slugCarries the ffh- prefix the naming rule prohibits. Needs a 301 before rename.~20 min
Airtable record still "In progress"Page is live and gate verified — can flip to Done.1 min

5 · The access decision

Bobby's email this morning changes the question. He did not ask for member accounts. He wrote: "I am still thinking about our call and doing my best to share highlights with others on our team. When you have a moment, could you share links to the things that you showed me, including that Rippel demo you developed?" That is a warm signal — he is evangelising internally. But it means the real decision is not how long do we grant access. It is what do we hand over that will be forwarded to people we have never met.

Do not send the Command Center

The "Rippel demo" he is asking for is almost certainly /rippel-command-center/. That page must not be sent, and the reason is not data — it is the contents. It carries:

It is gated at tier:'admin' for exactly this reason. A forwarded link would bounce him to the gate — but the instinct to "just open it up for him" is the thing to resist. Seeing our negotiating position and our notes on his own temperament would damage the relationship in a way no amount of good data recovers.

What is safe to send, today

AssetSend?
The 7-slide on-screen deck (PDF)YES Built client-facing from the start — real CDC figures, Rippel attribution on every slide that uses their framework, no pricing, no deal shapes. Designed to be forwarded.
Public FFH pages he saw
/phit-scorecard/ · /advance-the-dream-scorecard/ · /academy-welcome/ · /live-it-trackers/
YES Already public. Fix the three blocked maps on the Scorecard first — right now anyone he forwards it to sees "Access blocked" across the map.
The Ripple Simulator + the 18 scored communitiesNOT YET This is the thing he actually wants and the strongest asset we have. It currently lives inside the gated Command Center. It needs a client-safe standalone page — the simulator, the scored communities, the vital-conditions mapping, and the Learn/Live/Share loop, with every internal panel stripped out.
The Command CenterNO Internal. See above.
Member credentialsNOT ASKED FOR He asked for links, not logins. Do not offer what was not requested — it changes the frame from partner to vendor on trial.

What is actually copyable, and what isn't

Copyable by looking

  • The Learn It / Live It / Share It concept
  • The coin and badge loop
  • The PHIT Score equation — already written down in our own strategy doc
  • The visual design of a scorecard

All idea-level. Anyone who has seen a gamified health app could describe it.

Not copyable in a week

  • 200+ wired data sources and the normalisation behind them
  • The F-block engagement data — which only exists because real people use the platform
  • The Ambassador → Group Leader → Community Director ladder, with actual people in it
  • Four-country footprint, Supabase infrastructure, 26 Partner Journey courses

The moat is the operating system and the data exhaust, not the screens.

Two things still worth weighing

Rippel is not a competitor, structurally. A non-commercial operating foundation whose entire model is publishing frameworks and coaching stewards. No product team, no intent to build one. The realistic risk is not Rippel cloning FFH — it is an idea travelling onward through a forwarded deck to someone who would. Which is an argument for controlling what gets forwarded, not for refusing to send anything.

The IP flow is currently one-way in their favour. Their definitions are © 2023, educational use only; commercial or co-brand use needs written permission we do not yet have. His request for shareable links is the natural moment to ask for that licence in return — a genuine exchange rather than a demand.

Recommendation

Answer generously, but send purpose-built assets — not internal ones.

Reply today with the deck and the public page links. Tell him plainly that the demo he is remembering is an internal working surface, and that you would rather build him a proper shareable version than send him a page written for our own team — which is true, and reads as care rather than evasion.

Then build the client-safe demo this week: the Ripple Simulator, the 18 scored communities, the vital-conditions mapping, the Learn/Live/Share loop. Public or VIP-coded, your call — VIP codes at /gate/ give you an access log and revocability without feeling closed.

Do not offer member credentials. He did not ask, and offering unprompted converts a pilot conversation into a free evaluation.

I am not a lawyer — licence and NDA terms should get a real review before anything is signed. This is a commercial-judgment read, not legal advice.

Read the signal, not just the request. "Doing my best to share highlights with others on our team" is a man building internal consensus for you, unprompted, ten days after one call. That is the strongest buying signal in this engagement so far. The correct response is speed and generosity on everything that is safe to send — not caution. The only thing to be careful about is which artifact, not whether.

6 · Recommended next moves

WhenMove
TodaySend Bobby the follow-up (section 7) with the on-screen deck attached. Ask for the pilot-team conversation. Do not attach credentials.
This weekFix the three PHIT Scorecard maps — they are showing "Access blocked" to every visitor right now. Request the Census key. Flip the Airtable record to Done.
Next weekDomain O from County Health Rankings — the half-day that retires the two biggest generated numbers. Run the Activator pass on Wedge 6 so there is a playable module to show.
On a yesName the pilot region. Draft the co-brand licence request (Ask #1). Scope Domain F wiring for that region only — everywhere else F stays null.

7 · The follow-up to Bobby

What Bobby actually wrote, this morning:

"Hi Rob and Lucy, I am still thinking about our call and doing my best to share highlights with others on our team. When you have a moment, could you share links to the things that you showed me, including that Rippel demo you developed? Thanks a bunch. Bobby"

Subject: Re: Introductions — links, and the eighteen communities we scored

Bobby,

That is good to hear, and thank you for carrying it to your team — that means a lot.

Links below. One note first: the Rippel demo you are remembering is an internal working surface, built for Rob and me to think with rather than for anyone else to read. Rather than send you our scratch pad, let me build you a proper version of it this week — the simulator and the scored communities, put together to be shared. I would rather you had something your colleagues can actually open than something written in our shorthand.

What you can look at today:

  • The deck — attached. Seven pages. The thing worth your team's attention is page four.
  • The PHIT Score Card — theforce.health/phit-scorecard/ — the county engine, including the civic tab Becky flagged.
  • Advance the Dream Community Score Card — theforce.health/advance-the-dream-scorecard/
  • The Academy — theforce.health/academy-welcome/ and theforce.health/live-it-trackers/ — the Learn It / Live It / Share It loop, which is the part of our system your data cannot see.

On page four of the deck: we scored eighteen of the communities named in your Impact Report on one method, from live CDC data — New Castle, Palm Beach, Washtenaw, Forsyth, King County, the Inland Empire and the rest. It is one block of our composite, the community health baseline, and we label it as one block rather than dressing it up as a whole score. Morris County sits near the top at 86. Several of the places you coach run thirty and forty points below it.

Which is the question I would like to put to you and your team: does it make sense to stand up a pilot around one region and find out what moves? Rippel introduces and coaches, we operate and instrument, and the case study carries both names.

Would 45 minutes in the next couple of weeks work, with whoever on your team should see it? I would rather walk you through the working system than send more slides.

Lucy

Why it is worded this way. Declining to send the Command Center is handled as an offer to build something better, which is true and generous rather than guarded. The deck goes out immediately so he has something to forward today. The ask lands on a pilot question rather than an access offer — it keeps you co-deciding partners rather than a vendor under evaluation. And inviting "whoever on your team should see it" turns his internal evangelism into a meeting.