Director's Briefing · v1.1 · 2026-05-24

How Rob & Lucy Ship Together — Without the Manual Chaos

The Dr. Rob Activator Rule turns every drop in your "Ready to Test for Lucy" folder into a live, gamified, conversion-wired, fully-tagged FFH module — in 15 automated phases, with one human decision point. This page walks through how it works, where Dr. Rob's side plugs in, and how to add your two fellows without losing quality control.

Dr. Rob
CMO · Clinical Voice
Dr. Rob Gillio
Coach Lucy
CEO · Director
Coach Lucy Howell

What the Activator Replaces

Manual ingest time per drop~30 min → 3 min
Phases automated14 of 15
Human approvals needed1 (Greenlight Gate)
Skills orchestrated9
Standing-Rule ingredients enforced5 / 5
Canonical tag dimensions15 (SDGs · standards · conditions · gears · & more)
Deploy ledger entriesAuto (Airtable + TCC)
Section 1

The Big Picture

Four lanes. One direction. From Dr. Rob's keyboard to a live URL anyone in the world can visit.

DR. ROB ACTIVATOR (LUCY) DEPLOY READY VERCEL · LIVE Rob's Handoff Envelope Standardized README + tags THE ACTIVATOR · 15 Phases Ingest → Synopsis → Review → Gate → Scaffold → Cleanse → Brand → Gamify → PHIT → Clipboard → Landing → Conversion → Tag → Deploy → Ledger /Deploy Ready/<slug>/ module + landing + widget _deploy-<name>-<date>.py one-shot copy script GitHub Desktop commit + push to main https://theforce.health/<slug>/ Vercel auto-deploys in ~60 seconds

Lane 1 · Dr. Rob

Rob's Claude packages a drop into a standardized handoff envelope and posts it to "Ready to Test for Lucy."

Lane 2 · The Activator

Lucy's Claude runs all 14 phases automatically, pausing only at the Greenlight Gate for one approval.

Lane 3 · Deploy Ready

The cleaned, branded, gamified module + landing page lands here, plus a one-shot deploy script.

Lane 4 · Live on Vercel

GitHub Desktop pushes to main, Vercel deploys to production in about a minute.

Section 2

The 15 Phases — What Each One Does

Phases tagged DELEGATE call into existing FFH skills. Phases tagged GATE are decision points (one of them is yours, Lucy). Phase 13 (Standardize & Tag) is the canonical-categorization step — every module gets tagged against UN SDGs, education standards, conditions, body systems, FFH gears, and 10 more dimensions so the Network's data layer stays clean. Everything else runs automatically.

1

Ingest

Scan the drop folder, build an inventory, read Rob's README if present, classify primary asset type.

Auto
2

Synopsis

One-page "what is this drop?" summary with proposed slug, coach assignment, and one-line pitch.

Auto
3

Review

Value-add + duplicity check against existing Deploy Ready content. Markdown table for Lucy.

Delegate
4

Greenlight Gate

Lucy approves (or auto-approve for simple drops). The only human decision point.

Lucy Gate
5

Scaffold

Create /Deploy Ready/<slug>/ with module + landing + assets + lesson-plan folder.

Auto
6

Cleanse

Voice scrub (Rob keeps mic on health), compliance gates preserved, link cleanup, tracker unification.

Delegate
7

Brand

Canonical nav bar + footer, FFH colors, Segoe UI, typography balance, /brand-assets/ paths.

Delegate
8

Gamify

Real LEARN/LIVE/SHARE It coin assets, GamiPress hooks, rewards pop-ups at ≥3 milestones.

Auto
9

PHIT Attach

Wire to Supabase phit_scores, chna_priorities, ship_priorities + "Powered by PHIT" hub panel.

Auto
10

Clipboard

SMART Clipboard widget + pre-loaded coach greeting (Dr. Rob, Coach Lucy, or co-hosted).

Delegate
11

Landing Page

9-section marketing front door: hero, value prop, 4 audience CTAs, what's inside, sample experience, coach voice, gamification preview, conversion, footer.

Auto
12

Conversion

Sign In / Sign Up / Learn More CTAs on every public page + role-gate decisions for Member-tier content.

Auto
13

Standardize & Tag

Canonical categorization across 15 dimensions: education standards (ISTE, NHES, NGSS), UN SDGs, conditions, body systems, FFH gears, audience tier, coach, coins, careers, geo markets, PHIT priorities, module type, WCAG, compliance, status. Writes meta tags + manifest + Network registry.

NEW · Auto
14

Deploy

Pre-deploy checklist (refuses partial), then hands off to the deploy-ready skill for the Python script.

Delegate
15

Ledger + Memory

Auto-update Airtable Deploy Ledger (with the Phase 13 tags) + Tech Command Center registry + write project memory to CLAUDE.md.

Auto
Phase 13 deep-dive

The 15 Canonical Tag Dimensions

Every module that ships gets categorized against ALL 15 dimensions — "not applicable" is a valid answer for some, but every dimension is considered. Source of truth lives in FFH Skills/ffh-dr-rob-activator/references/canonical-taxonomies.md — never hand-invent a value.

1 · Education Standards
ISTE · NHES · ASCD · SHAPE America · NGSS
2 · UN SDGs
All 17 goals; default primary = SDG 3 (Health) + SDG 17 (Partnerships)
3 · Conditions
Sickle cell · asthma · diabetes · heart disease · opioid · maternal · dementia · cancers · & more
4 · Body Systems
Cardio · respiratory · MSK · GI · GU · neuro · endo · immune · mental · sensory · & more
5 · FFH By Gear
Chamber · PHIT · Academy · STEAM · Workforce · Omni · Command Center
6 · Audience Tier
Public · Member · Super Admin · Exec Explainer
7 · Coach Assignment
Dr. Rob · Coach Lucy · Co-hosted
8 · Coins & Badges
LEARN It · LIVE It · SHARE It + module-specific badge slugs
9 · Career Pathways
Physician · nurse · allied · public health · CHW · ambassador · 15+ more
10 · Geographic Markets
10 US states · 10 global countries · 11 RHG Regions
11 · Population Health
CHNA · SHIP · PHIT 5-tier breakdown priorities
12 · Module Type
Game · simulation · lesson · tracker · dashboard · landing · tool · explainer
13 · Accessibility
WCAG 2.1 AA · partial · not assessed
14 · Compliance
HIPAA · FERPA · COPPA · ADA · disclaimers · safety gates · clinical review
15 · Production Status
Todo · In progress · Internal review · Done · Held back
Why this matters → Tags get written to three places every time: the page's <meta> head, a per-page _tags.json manifest, and the Network-wide _taxonomy/tag-registry.json. That registry powers SDG-impact reports to funders, education-standards-coverage decks for school district sales, conditions-by-module heat maps for clinical partners, and career-pathway audits for workforce-development grants. Skip tagging once and every downstream report has holes.
Section 3 · Proposed Companion Skill

Where Dr. Rob Plugs In: The Handoff Envelope

The Activator works today against any drop Rob makes — but every minute Rob's Claude spends standardizing the handoff saves Lucy roughly 10 minutes of cleanse work on the receiving end. A small skill on Rob's side closes that gap.

Today — Reverse Archaeology

  • Mixed file naming — kebab-case, snake_case, Title Case all in one drop.
  • Spotty README — some drops have FFH-Handoff-README.html, most don't.
  • Voice mix — Coach Lucy framing sometimes appears on clinical content.
  • Prototype mocks — localStorage trackers, base64 brand images, hardcoded PHIT data.
  • Hidden duplicates — Rob may rebuild something we already have because his Claude can't see production state.
  • Implicit compliance gates — safety warnings live in Rob's head, not in the file.
Cost: ~30 min of Cleanse-phase work per drop, mostly reasoning about what Rob meant.

With the Envelope — Verification, Not Rebuild

  • Canonical README — intent, coach proposal, integration order, voice map, compliance gates all declared.
  • Pre-applied FFH primitives — /brand-assets/ paths, submitLiveItAction() shape, real coin asset filenames.
  • Voice tagging — HTML comments mark every section as <!-- voice: rob --> or <!-- voice: lucy -->.
  • Duplicity pre-check — Rob's Claude reads a published production snapshot and flags overlap before sending.
  • Naming convention — kebab-case files, no spaces in folder names, prototype-reference/ subfolder for non-deployables.
  • Audience tier proposal — Public / Member / Admin tagged per file so Phase 12 decisions are pre-made.
Payoff: Cleanse drops to ~5 min. Auto-Greenlight becomes the norm. Lucy reviews only flagged decisions.
Dr. Rob

For Rob to install

One skill file (~6 KB), one install command in his Claude project, and a 5-minute walkthrough. He keeps building the way he likes — the envelope skill just packages his output in the shape Lucy's Activator wants. We'll draft ffh-rob-handoff-envelope as the next deliverable and pair it with a "Dear Rob" install guide.

Section 4

Your Tech Team Stack — Who Does What

Four humans, two AIs, one production pipeline. The roles below are how a lean tech team of your size stays fast without dropping quality.

Role Person Owns Git Access Tier
CEO · Director Coach Lucy Brand gate, final merge to main, deploy ledger, memory write-back, Activator Greenlight Owner Approver
CMO · Clinical Dr. Rob Gillio Handoff envelope, clinical content authority, voice rule, compliance gates Maintainer Approver
Fellow #1 (To onboard) Feature branches, PRs to main, content drops, page builds under Lucy's review Collaborator Contributor
Fellow #2 (To onboard) Feature branches, PRs to main, content drops, page builds under Lucy's review Collaborator Contributor
AI Coach Coach Lucy AI In-platform wellness coaching, navigation, community activation None (runtime only) AI
AI Coach Dr. Rob AI In-platform clinical education, evidence-based explanations None (runtime only) AI
Section 5

Adding Your Fellows — Three Options

You asked the right question: do all changes funnel through you, or do fellows push their own commits? Here are the three real options. We strongly recommend Option C — it gives fellows independence without giving up your quality gate, and Vercel's automatic preview deployments make it almost effortless.

Option A · Sole-Source

Everything funnels through Lucy. Only Lucy pushes to GitHub.

No risk of off-brand or half-baked work shipping Single point of QA Lucy is the bottleneck — work waits on her availability Doesn't scale past 2-3 contributors Fellows can't see their work live without Lucy's help

Option B · Open Push Access

Each fellow can push directly to main and trigger Vercel deploys.

Maximum speed No bottleneck No QA gate — anything ships, broken or not Hard to roll back, no review trail Security risk if an account is compromised

Option C · Branch + PR with Vercel Previews

Fellows push to feature branches. Vercel auto-creates preview URLs. Lucy or Rob merges to main when ready.

Every branch gets its own live preview URL automatically Lucy keeps the QA gate without being the only one who can deploy Easy rollback, full audit trail, parallel work Fellows can share preview URLs for feedback before merge ~30 min learning curve on git branching (GitHub Desktop makes it easy)

What Option C Looks Like in Practice

Dr. Rob branch: feat/rob-* Fellow #1 branch: feat/fellow1-* Fellow #2 branch: feat/fellow2-* Coach Lucy branch: main (merger) GitHub Repo · theforce.health feat/rob-marstronaut feat/fellow1-bingo-cardio feat/fellow2-time-machine main (production) preview: theforcehealth-git-feat-rob-*.vercel.app preview: theforcehealth-git-feat-fellow1-*.vercel.app preview: theforcehealth-git-feat-fellow2-*.vercel.app production: theforce.health Pull Requests reviewed by Lucy/Rob → merged to main → ships to production Every branch gets a unique live preview URL automatically — share with Lucy/Rob for review before merge.
Section 6

Setup Checklist — Adding Each Fellow (≈45 min one-time)

One-time setup per fellow. Do it once and they're productive forever after. Lucy stays the only person who merges to main, so the gate holds.

Lucy's side (do once, then per-fellow)

  1. Add fellow as Collaborator on the repo — GitHub.com → theforce.health repo → Settings → Collaborators → Add. Send the invite to their GitHub email.
  2. Set branch protection on main — Settings → Branches → Add rule for main: ✅ Require pull request review (1 approver), ✅ Require status checks (Vercel preview must succeed), ✅ Do not allow bypassing.
  3. Verify Vercel previews are on — Vercel.com → theforce.health project → Settings → Git → Production Branch = main, Preview Deployments = "All branches". (Default behavior, free on Hobby tier.)
  4. Optional: add fellows to the Vercel team — only needed if they should see deployment logs. Not required to deploy.

Fellow's side (Lucy walks them through, ~30 min)

  1. Install GitHub Desktop — desktop.github.com, sign in with their GitHub account.
  2. Accept the collaborator invite from their email, then in GitHub Desktop: File → Clone Repository → theforce.health. Save to a friendly local path.
  3. Create a feature branch — Current Branch → New Branch, name it feat/yourname-what-youre-building. Example: feat/fellow1-prevention-bingo-cardio.
  4. Make changes — edit files in ~/theforce.health/public/<slug>/, save, see them in GitHub Desktop's diff view.
  5. Commit + push the branch — Commit to feat/... with a clear message, then Publish branch (first time) or Push origin.
  6. Open a Pull Request — GitHub Desktop will offer "Create Pull Request" — clicking it opens GitHub.com with the PR pre-filled. Add a screenshot and a one-line description of what changed.
  7. Share the Vercel preview URL — within ~60 seconds, Vercel comments on the PR with a live preview link. Share it with Lucy or Rob for review.
  8. Wait for review + merge — Lucy or Rob reviews, clicks Merge, Vercel ships to production.

Naming conventions (keeps the repo tidy)

  1. Branch names — feat/<name>-<short-desc> (new build), fix/<name>-<short-desc> (bug fix), content/<name>-<short-desc> (content update only).
  2. Folder names — kebab-case under /public/, prefix new top-level modules with ffh-. Example: /public/ffh-time-machine/.
  3. Commit messages — first line is the punch (e.g., "Add Marstronaut landing + 3 mission cards"), wrap at 72 chars.

What stays Lucy-only (the firewall)

  1. Merging to main — only Lucy (and optionally Rob) approves merges. This is the brand + quality gate.
  2. Edits to /brand-assets/ — only via the canonical sync script, never hand-edited in the repo.
  3. Edits to /_shared-assets/ (notepad widget, role gate, supabase client) — affects every page, so review carefully.
  4. Deploy scripts in /Deploy Ready/ — Lucy owns the orchestration layer.
  5. Airtable ledger + Tech Command Center registry updates — Lucy's Claude handles these in Phase 14 of the Activator.
Next Steps

Three Moves to Make This Real

Once you and Rob have walked this page together, here's the suggested sequence to get the full pipeline humming.

1. Build the Envelope

Draft ffh-rob-handoff-envelope + "Dear Rob" install guide. ~1 hour.

2. Onboard Fellow #1

Add as collaborator, walk through GitHub Desktop, do a first throwaway PR to learn the flow. ~45 min.

3. Run the Activator Live

On Rob's next drop, say "fire the Activator" and watch all 14 phases run. Refine from there.