📝 Verification & Risk Routing Algorithm
This document outlines the logic used by the Verification Hub to categorize a user’s wellness risks into three routing buckets: Priority Risks, Missing Analytics, and Low Risk. It details how the interface reads the GOD JSON, handles overrides, and routes specific markers.
1. The Smart Routing System (UI Buckets)
Every assessed wellness condition is sorted into one of three distinct lists on the frontend. The system evaluates the status of the condition (e.g., Severe, Normal) found in the user’s GOD JSON to decide where it belongs.
If a user logs an independent test or monitor result via the Verification Hub, the system ignores the original AI-assessed status and routes the card based purely on the user’s manual input (e.g., if the AI said “Severe”, but the user took a test and logged “Normal”, the card is instantly moved to the Low Risk bucket and flagged as ✅ VERIFIED).
| Dashboard Bucket | Triggered By (Status Levels) | System Rationale |
|---|---|---|
| 🔴 Priority Risks to Verify |
Severe
High
Elevated Special Rule: Biomarkers assessed as Low or Very Low |
Conditions where significant wellness risk was detected, or where the user manually logged a positive/high test result. Note: Low blood biomarkers (like Low Iron) are dangerous and explicitly forced into this priority bucket. |
| ⚪ Analytics Missing | No Data Missing | The user has not completed the required assessment modules for this specific condition. Includes a “View Progress →” link that returns the user to the main assessment questionnaire. |
| 🟢 Assessed As Low Risk | Normal Low Verified Good | Standard wellness conditions cleared by the AI assessment, or risks that the user has verified as “Normal/Negative” via independent testing. |
2. Biomarker Inheritance (Bloodwork)
Crucial Distinction: The Verification Hub does not perform any mathematical calculations or threshold checks on raw bloodwork numbers. All biomarker math is completed upstream.
This script simply reads the pre-calculated text strings (e.g., "tsh_status": "Very High") already sitting inside the GOD JSON and routes them accordingly.
| GOD JSON String Found | Verification Hub Routing Action |
|---|---|
| “High” / “Very High” | Routed to 🔴 Priority Risks |
| “Low” / “Very Low” | Routed to 🔴 Priority Risks (Low nutrients/hormones require verification). |
| “OK” / “Normal” | Routed to 🟢 Low Risk |
3. Mind & Nervous System Overrides
Mental wellness risks have unique Javascript cross-referencing logic built into verification_index to ensure extreme states are caught and prioritized immediately before rendering the page.
| Condition Card | Logic / Trigger in JS | Assigned Status | Notes |
|---|---|---|---|
| Nervous System Burnout | neuro_state.state = “BURNT OUT” OR “FREEZE” OR “DROWNING” |
Severe | If the user explicitly selected an extreme nervous system state during the Mind Assessment, this overrides all other data and forces the Burnout card to Severe. |
| None of the above selected. | Inherits GAD | If no extreme state is found, it copies the user’s General Anxiety (GAD) status (e.g., if GAD is Normal, Burnout is Normal). |
4. Standard Inheritance Variables
The following conditions simply pull their status directly from the pre-computed strings (e.g., “High”, “Severe”, “Normal”) generated during the core body/mind/sleep assessments and saved in the GOD JSON.
- 💨 SIBO (Bacterial Overgrowth): Inherits
sibo_status - 🚽 IBS & Gut Inflammation: Inherits
ibs_status - 🌾 Coeliac & Gluten Sensitivity: Inherits
celiac_status - 🥛 Lactose Intolerance: Inherits
lactose_status - 😮💨 Sleep Apnea Risk: Inherits
osa_status - 🦉 Insomnia & Sleep Architecture: Inherits
insomnia_status - 🌗 Circadian Rhythm Dysfunction: Inherits
circadian_status - 🧠 Anxiety & General Stress: Inherits
gad_status - 🫀 BMI / Body Composition: Inherits
bmi_status - 🫀 Visceral Fat Index: Inherits
vfa_status - 🩸 Blood Sugar & Diabetes: Inherits
diabetes_status - 🩸 Blood Pressure: If
bp_highin GOD JSON is “Yes”, JS assigns “High”. Otherwise, assigns “Normal”.
5. Schema & Custom Verification Limitations
When a user logs a verified test, the script writes the data directly into predefined folders within the GOD JSON (e.g., sibo_verification, ibs_verification).
custom_verifications intended for user tests that are not on the standard curated list, verification_index does not yet have the visual UI or the backend saving rules to allow a user to add those extra tests. Currently, the tool only supports and updates the predefined wellness conditions.