SCFA Contract Review — Response Gameplan

1 · The Situation

Kevin Johnston — SCFA's board technical lead (ex-Raytheon), resigning from the board and largely absent for the past couple of years — has surfaced at the final hour of the funded app period with a contract-review email raising seven points against the original July 2023 agreement.

This is best read as a closeout audit, not an attack: a departing engineer wants the technical gaps on the record before he goes. Our objective is not to win an argument — it is to close the chapter cleanly, protect a valued relationship (SCFA opened the Banner door and remains a good foundational partner, with two active follow-on contracts), and bridge to SCFA's next phase. The contract's dispute path is binding arbitration in Pima County; nobody wants that. We keep it collaborative — that is the leverage.

The posture in one line

Concede what is genuinely owed, graciously and fast. Provide calm context where the criticism misreads the architecture everyone agreed to. Never admit "breach." Model the 48-hour responsiveness he is asking for.

2 · The Core Reframe

DEFUSES POINTS 1 & 4

The 360° SCD Hub was never a custom-code build, and all parties signed knowing that. It intentionally duplicates the Force for Health stack: a WordPress core plus established third-party plugins (BuddyBoss, GamiPress, LearnDash) wrapped in BuddyBoss-generated native apps — a deliberate, grant-budget choice for a full-featured platform.

The implication: the living functionality and nearly all updates happen on the server/plugin side, not as commits to the app-wrapper repo. So the GitHub repository barely changing is the expected signature of this architecture — not evidence the platform is static.

On record: this architecture was presented to and accepted by SCFA — the board overview (with the tech slides kept in specifically for Kevin) was delivered April 2, 2024, and the full stack was demonstrated and accepted at the "Move to Maintenance" milestone, paid in full in 2024.

3 · The 7 Points — Position & Status

#	Point	Our stance	Class
1	Source code unchanged 2–3 yrs	Architecture by design; deliver an architecture map	Context
2	No build instructions (Exhibit B #12)	Owed — concede; deliver build runbook	Action
3	Bugs unresolved / response time	Already logged & tracked (12 items); triage in 48 hrs	Action
4	iOS vs Android ~1.5-yr gap	Different store regimes + SCFA-held Apple account; resync	Context
5	Google health-apps declaration	Owed maintenance; status + resolve in Android pass	Action
6	Google Play 16 KB page size	Owed maintenance; confirm / remediate in same pass	Action
7	Texas SB 2420 (age verification)	New law post-dating scope; deliver applicability assessment	Forward

Net: 2 points are context (defensible by design), 4 are gracious deliverables, 1 is forward-looking. Concede the fair, hold the line on the misread, never admit breach.

4 · Our Evidence & Paper Trail

The documentation timeline

Jul 2023

Contract signed

Apr 2024

Board presentation delivered (tech slides for Kevin)

2024

Move to Maintenance accepted · paid in full

Nov 2024

12 issues logged & tracked

Jun 2026

This response

Kevin's "missing" bug list — we have it (12 items, logged Nov 8 2024)

Nine bug fixes, two future enhancements, and one contractual item (the build instructions — his point #2, already logged). Four of the bugs were marked awaiting Kevin's own input on preferred behavior — the §6 shared-collaboration responsibility, in writing.

Tracker chart root cause (his items 5–8): the original trackers ran on Gravity Forms + WPDataTables, whose caching/JS-conflict behavior makes charts render unpredictably — a third-party-stack limitation with no reliable fix. Resolution: we rebuilt the tracker as a self-contained, offline-capable, MIT-licensed 360° Health Tracker and already shipped it as added value in the enhancement phase. Known issue → already fixed → reason to move to the new version.

Kevin's own emails work in our favor

"Apple Developer Account needs Update… This is done now, apologies" (6/28/25) — the iOS store account is SCFA-held; the fix sat on their side until late June 2025. Explains the iOS timing, in his words.
"Charts not working in app… It's working now" (6/11/25) — he reported and then confirmed the chart issue resolved himself.
"I don't think any of these changes apply to 360 SCD Hub" (12/12/25, Google payments policy) — he himself applies discernment about which store rules apply. Our card on the Texas-law item.

5 · Our Contract Footing (internal)

Term: 48 months from 7/27/2023 → runs to ~July 2027. Maintenance obligations still active, so deliver in good faith — but we are not "past due and exposed."
§6 collaboration: "both parties have limited resources… SCFA agrees to provide timely input… or modify based on mutual understanding and acceptance of delays." Delays are mutual.
§2(d): standard is "commercially reasonable" support — not perfection.
§14 Force Majeure: expressly includes "supplier failures" — BuddyBoss plugin defects are supplier-side, beyond our reasonable control.
§2(c)(ii): requires keeping the app free of "errors in users experience" — which is why we held some BuddyBoss updates. Defensible under the contract's own words.

6 · Talking Points & What to Say Live

HOLD IN RESERVE — DO NOT PUT IN WRITING

These corroborate that cadence gaps were mutual. Keep them as calm backup only if Kevin escalates toward blame — they read as defensive in writing:

Declined the 2025 Year-End Recap speaker invite (12/12/25).
Canceled the monthly Executive Zoom (11/1/24, "family comes first").
"Getting caught up between vacation and work" (6/28/25) — his own delay on the Apple account.

The judo move on SB 2420: if he presses, say — "I'd apply the same disciplined read you did on the Google payments policy." Validates our measured approach using his own judgment. Powerful live; left out of the written reply on purpose.

7 · What We're Delivering (the closeout packet)

Architecture map — where every piece of functionality lives.
iOS + Android build runbook (his point #2).
Status sheet for the store-compliance items (4–6), resolved in one Android pass.
Triage of the documented issues register, within the 48-hour window.
SB 2420 applicability assessment.
A 45-minute technical working session — Kevin, Lucy, Dr. Rob, and our development team — before he steps off the board.

Companion artifacts (already built)

Response & Resolution Log

Client-facing interactive log — all 7 points, the issues register, root-cause story.

HTML · for Kevin

Technical Documentation Packet

Curated Word "tech plan" cross-referencing each point to its evidence.

DOCX · for Kevin

This Explainer

Internal strategy & talking points for Lucy & Rob.

Gated · Super Admin

Decision Requested

Approve the response approach & the working session

Send the client-facing Response & Resolution Log + Technical Documentation Packet as a warm, firm reply, and propose the 45-minute technical working session before Kevin departs.

One-line approval: "Approved — send the response log + tech plan and book the working session with Kevin and our dev team." (Before sending, confirm current store-compliance status internally so we commit to deliverables, not dates we can't hit.)