Evidence Memo — 360° SCD Hub Architecture Agreement

▶ Recordings connected (Vimeo)

All five calls are wired to their Vimeo videos from your Team Library — every "Jump to this moment" button and embed below opens Vimeo at the exact second of that quote. IDs are pre-filled below; you can adjust any of them if a video is ever re-uploaded.

1. Bottom line

Yes — the transcripts support the framing in your draft reply. Across the 2023 weekly app-development calls, the Force for Health side repeatedly and openly explained that the 360° SCD Hub was being built on the same WordPressBuddyBossLearnDashGamiPress "mirror" of the Force for Health stack — explicitly as a cost- and time-driven choice rather than a custom, ground-up build — and the SCFA participants (Kevin, Moses, Dr. Gillio) were present, engaged, and voiced agreement and comfort with that approach.

The single most useful moment: after a detailed walkthrough of the WordPress-as-app architecture and its cost efficiency, the SCFA participant who had raised the concern says — "I'm glad we had this conversation… I'm feeling much more comfortable."

Caveat on attribution: the auto-generated captions do not label speakers. Attributions are inferred from context (who is presenting the platform vs. who is asking the owner/engineering questions). The recordings are the authoritative record; this memo points you to the exact moment to cite.

2. The recordings & their dates

Recording	Date	In Aug–Dec 2023 window?
Weekly App Dev Call F2	~Sep 8, 2023	Yes — "September 15th… literally next week"; targeting an Oct 7 publish
Weekly App Dev Call F1	Fri Oct 13, 2023	Yes — stated on tape: "Friday, October 13th… SCFA weekly app development call"
Architecture / Cost Call MAIN	Fri Nov 3, 2023	Yes — Vimeo title "SCFAZ/FFH: Weekly App Development Meeting 2023-11-03"; its 2:08:28 runtime uniquely matches this ~2h06 transcript. Holds the richest cost/architecture discussion.
Weekly App Dev Call F3	Fri Dec 1, 2023	Yes — stated: "today is Friday, December 1st… weekly SCF app development meeting"; present: Moses, Kevin Johnston, Dr. Gilio, Lucy
Contract Review Call 2026	Fri Jun 26, 2026	No — but on point: this IS the call where Kevin's email is discussed. Included as a bookend.

3. Evidence — the stack was a deliberate cost/time choice (2023)

4. Bookend — how it's described in the June 26, 2026 review call

The contract-review call (Lucy, Kevin Johnson, Adia Akpan present) restates the 2023 understanding plainly — the framing repeated to Kevin without objection on the record.

5. Honest gaps & how to firm this up

Speaker labels: captions are unattributed. Before citing a quote as "Kevin said," confirm the speaker by listening at the timestamp. Safest cites: the FFH-side explanations (clearly the presenter) plus the owner-side "much more comfortable" acknowledgment.
Main-file date — resolved: the richest call had no spoken date, but it's now matched to the Vimeo recording "Weekly App Development Meeting 2023-11-03" (runtime 2:08:28 vs the ~2h06 transcript), placing it firmly inside the Aug–Dec 2023 window.
No "magic words": nobody says "I agree to mirror the FFH stack to save money." The agreement is shown through the design discussion, the stated budget constraints, and the verbal sign-off — persuasive, but inference-by-context, not one signed sentence.
Strongest single cite: the MAIN call ~02:00:34 → 02:03:20 sequence — concern raised → cost/architecture rationale → "I'm feeling much more comfortable." Lead with that.

6. Suggested one-line for the reply to Kevin

"As we walked through together on the development calls — including the session where we reviewed the WordPress/BuddyBoss architecture and you noted you felt much more comfortable with the approach — the Hub was intentionally built to mirror the Force for Health stack as a deliberate, grant-budget choice. That's why the living functionality sits in the plugin layer rather than the app-wrapper repo."

Confidential — Internal Work Product · The Force for Health Network · Generated June 30, 2026
Timestamps are positions within each recording. Quotes are lightly cleaned of filler ("um", false starts) for readability; verify exact wording at the cited moment.