---
name: ffh-pathway-engine
description: >
  The FFH Pathway Engine architecture, data model, node type taxonomy, content
  tagging system, routing logic, and extensibility protocol for the Force for
  Health Network. TRIGGER THIS SKILL for ANY conversation involving the Living
  Wellness Pathway, individual pathway steps, content recommendations, community
  resource matching, learning style routing, goal-based content filtering, or
  adding new stepping stones to the pathway. Also trigger for: "what goes on a
  pathway," "add a new node," "how does content get matched," "tagging content,"
  "routing users to content," "community resources on the pathway," "extensible
  pathway," or any reference to the Me/We/Ours framework in a technical context.
  This skill coordinates all other FFH skills — it is the connective layer.
---

# FFH Pathway Engine — Master Architecture

## What This Is

The Pathway Engine is the adaptive routing layer that assembles a personalized
route through the FFH ecosystem for each user. It is NOT a page or a module.
It is the data model + routing function that connects every module.

Every piece of content in the FFH ecosystem must be registered as a
content_object in Supabase with the correct tag arrays. The routing
function reads those tags against the user's profile and returns a ranked,
sequenced pathway. Adding new content = adding a row to the table. No code.

## The Nine Node Types

Every pathway step is one of these types. New types can be added
by defining a type string and a rendering template — no schema change.

learn      — Education content (video, visual, audio, game, reading, simulation)
live       — Behavior challenge, tracker, daily habit, streak
share      — Social sharing, referral, community multiplier
ours       — Civic action, volunteer, donation, legislation
assess     — Deeper validated screener that changes routing
clinical   — Doctor prep, telemedicine, CHW, clinic finder, referral
resource   — Director-managed local resource (park, market, program, clinic)
benefit    — SNAP, Medicaid, insurance, housing, transportation, WIC
custom     — Any new type defined by Director or FFH team. Open slot.

## Content Tagging Taxonomy

Every content_object row MUST have:
  content_types  — video | visual | audio | simulation | reading | social | game | tracker
  health_topics  — heart | diabetes | sleep | mental | lungs | sdoh | weight | ...
  goal_tags       — weight | diabetes | heart | sleep | stress | move | eat | family | community
  node_type       — one of the nine types above
  trigger_conditions — jsonb — optional conditions that must be met for node to appear

Learning style → content_type mapping:
  visual     → [video, visual]
  audio      → [audio]
  simulation → [simulation, game]
  social     → [social]
  reading    → [reading]

## Routing Priority Formula

priority = (goal_score * 0.5) + (risk_score * 0.3) + (style_match * 0.2)

goal_score  = overlap between content goal_tags and user.goals
risk_score  = relevance of health_topics to user risk_flags  
style_match = overlap between content_types and user learning_styles

## Extensibility Rules (NEVER BREAK THESE)

1. New content = new row in content_objects. Never hardcode.
2. New local resource = Director adds via dashboard. ZIP + goal_tags required.
3. New node type = new type string + rendering case. One dev, one afternoon.
4. Trigger conditions = jsonb on each row. No rule engine needed.
5. White-label org_id isolation is mandatory on every query.

## Key Supabase Tables

user_profiles       — goals[], learning_styles[], risk_flags jsonb, situation jsonb
content_objects     — node_type, content_types[], goal_tags[], trigger_conditions jsonb
pathway_routes      — assembled pathway per user, status, priority_score
community_resources — Director-managed, zip_codes[], goal_tags[], event_dates jsonb

## The Me / We / Ours Framework

Every pathway exists in three rings:
  Me    — individual health check, education, trackers, clinical navigation
  We    — family pathway, shared activities, family tracker and report
  Ours  — civic action, community projects, legislation, volunteer, donate

The pathway engine routes users through all three rings based on their
goals and engagement level. A user who selects 'community' as a goal gets
Ours nodes earlier. A user who selects 'family' gets We nodes earlier.

## What Claude Should Do With This Skill

When building ANY new FFH page or module:
- Register new content as content_objects with correct tags
- Never hardcode resource lists — they belong in community_resources
- Every new page should expose its content to the pathway engine via tags
- Use the nine node types as the vocabulary for all pathway decisions
- When a user describes a new stepping stone ("CHW assignment", "Meals on Wheels",
  "cheaper insurance guide") — identify the node_type, define trigger_conditions,
  and describe the content_objects row — don't build a one-off page

## Reference Files

Load these when needed:
  references/node-types.md       — Full inventory with examples per type
  references/supabase-schema.sql — Complete table definitions
  references/routing-function.sql — Full routing pseudocode + SQL
  references/content-taxonomy.md — Complete tag vocabulary
  references/director-guide.md   — How Directors add/manage resources