HHE Tier Refactor (5→3) — Technical Briefing

Action Needed

Amy — Your Input Needed

Four decisions that gate the entire migration. Each has a recommended path. Estimated time: 3 minutes.

A. Which products qualify as “Certified” tier?

✓ Recommended: HHP Portal + HHE Educator Certification (2 products)

Confirmed: HHP Portal (2148756329), HHE Educator Cert (2148721952)
Needs your call: TNC Certification (492485), Holistic Health Coaching (341533), Product 2148679039
Why it matters: If TNC/HHC are Certified, their 7,821+ chunks gate behind the highest tier. If Student, any paid user can access them.

B. Any paid products that should NOT be Student tier?

✓ Recommended: No exceptions — all paid = Student

Simplest model. Resolves all 3 existing access mismatches automatically. Adding exceptions recreates the complexity we’re eliminating.

C. Should FLY (Neuro Wellness) stay FREE or become Student?

✓ Recommended: Member (free) — 30 members already enrolled at no cost

FLY is Product 2149250013 (Neuro Wellness, 30 free members). Changing to paid would disrupt existing access. Lamonte’s agentic UX project depends on this remaining accessible.

D. Keep segment boosts within Student tier?

✓ Recommended: Keep all 4 boosts as-is

Segments (aoscan 1.15x, coach 1.15x, educator 1.15x, practitioner 1.20x) are orthogonal to tiers — they boost content relevance within a tier, they don’t gate access. No change needed.

Interactive form available: We’ve prepared a fillable decision form that captures your responses and posts them to Slack. Takes ~3 minutes.

Current State

Why This Refactor Is Needed

The 5-tier system has a dead tier, 3 confirmed mismatches, and unnecessary complexity.

3

Active Access Bugs

Real users blocked from content they paid for, or accessing content they shouldn’t.

1

Dead Tier (level-3)

Supabase view never emits level-3. It exists in config but not in production.

41

Unmapped Products

Paid products with no course context in RAG. Tier refactor simplifies future tagging.

Confirmed Mismatches

Course	ChromaDB Tier	Config Tier	Chunks	Impact
tnc-hhc	certified	level-2	7,821	level-2 users BLOCKED from content they should access
autoimmune	level-1	level-2	915	level-1 users ACCESS content they shouldn’t
10-steps	level-2	level-1	470	level-1 users BLOCKED from their content

All 3 mismatches resolve automatically under the new model. All three courses become Student tier — any paid user can access them.

New Model

The 3-Tier Model

Member → Student → Certified. Simple, consistent, and immediately actionable.

New Tier	Replaces	Rule	Products
Member	guest	Free / no purchase	37 free products
Student	level-1 + level-2 + level-3	Any paid product or bundle	~66 paid products
Certified	certified	Certification product ownership	2-3 products (pending Amy)

Key design decision: Collapsing level-1/level-2/level-3 into Student means any paid user sees ALL paid content. This eliminates the source of all 3 existing mismatches and removes the “dead” level-3 tier.

Migration Pipeline

6-Layer Migration Sequence

Amy’s decisions flow through 6 system layers. Each layer must update before the next.

Tier Refactor Migration Pipeline

1 Supabase: v_user_tier_calculation CASE statement → certified / student / member
2 SQL Views: v_course_tier_access + v_segment_bundle_course_map rebuilt for 3-tier
3 Config: course-mapping-v2.json tier definitions, standalone_tier, bundles
4 Code: tier-service.js + supabase-sync.js + chroma-client.js + context-builder.js (atomic)
5 ChromaDB: Bulk remetadata on ~17K chunks
6 Documentation: Skill files + course tables + SQL view references

Code Deploy

Atomic Code Deployment

These 4 files must deploy together — partial deployment breaks tier calculation.

Atomic Deploy — 4 Files Together

File	Key Change
`tier-service.js`	TIERS array → [member, student, certified]; rewrite calculateTier() and getTierDisplayName()
`supabase-sync.js`	bundleOfferMap: all level-3 entries → student
`chroma-client.js`	queryWithAccess() auto-inherits from tier-service update
`context-builder.js`	getMembershipContext() display strings; buildUpsellGuidance() 3-tier checks

Data Migration

ChromaDB Bulk Remetadata

~17,000 chunks need access_tier remapped. Can lag behind code deploy.

ChromaDB Chunk Distribution by New Tier

Old Value	New Value	Estimated Chunks
guest	member	~4,400
level-1	student	~1,800
level-2	student	~1,500
level-3	student	minimal
certified	certified (unchanged)	~10,000

Timeline

Execution Timeline

~2-3 days of engineering after Amy’s decisions are confirmed. Layers execute sequentially.

HHE Tier Refactor — Execution Timeline

Amy’s Decisions Gate Everything

Downstream impact: The G-Drive ingestion pipeline (CSA Handoff #2) depends on this refactor completing. New ingested content needs the 3-tier metadata schema to be live before it can be tagged correctly.