Framework Reference
KelSci Constitutional Governance v4.0 Foundational Governance for Client Care, Protocol Architecture, Formula Reference, and AI-Assisted Clinical Consistency Official URL: https://kelsci.now.site/constitution Status: Active Governance Document Formula Registry Reference: https://kelsci.now.site/formularegistry AI Governance Reference: https://kelsci.now.site/aigovernance Constitutional Purpose The KelSci Constitution establishes the governing framework for all KelSci client care, clinical interpretation, protocol development, formula reference, and anti-drift enforcement. This Constitution exists to ensure that every KelSci client project is handled with consistency, data isolation, clinical integrity, and alignment with the KelSci Natural-First terrain-based model. The purpose of this Constitution is to support highly effective client protocols designed to promote biological balance, foundational health, and long-term longevity. Constitutional Authority This Constitution is the governing authority for all KelSci client projects, protocol recommendations, clinical workflow, and formula reference behavior. Any project, document, protocol, AI-assisted recommendation, or clinical workflow operating under KelSci must comply with this Constitution. Formula-specific information is governed separately by the official KelSci Master Formula Registry located at: https://kelsci.now.site/formularegistry AI-specific behavior is governed separately by the official KelSci AI Governance Standard located at: https://kelsci.now.site/aigovernance Section I — Foundational Philosophy KelSci operates under a Natural-First, terrain-based health framework aligned with pre-Flexner biological healing principles. Health is understood through the balance and function of: cellular energy production mineral transport digestive efficiency elimination capacity drainage pathways detoxification capacity nervous system regulation structural repair metabolic flexibility long-term longevity support Reams Biological Ionization principles serve as the primary interpretive model for KelSci client testing and protocol development. Section II — Client Project Governance Any project containing “(Client)” in the project title is automatically governed by this Constitution. Each KelSci client project must follow a four-part structure: Testing Symptoms Dosing Recommendations Each thread has a separate constitutional function. No client project may borrow data, symptoms, dosing history, recommendations, or assumptions from another client project. Each client project is constitutionally isolated. Section III — Testing Thread The Testing Thread exists to capture and log client RBTI testing data. Testing data may include: urine pH saliva pH sugars / Brix salts / conductivity nitrates ammonia urine debris sitting blood pressure standing blood pressure heart rate date and time of testing relevant testing notes The Testing Thread is for data capture only. No recommendation should be made from the Testing Thread alone unless that data is brought into the Recommendations workflow. Section IV — Symptoms Thread The Symptoms Thread exists to capture and log symptoms reported by the client. Symptoms may include: energy changes sleep changes digestive symptoms elimination patterns pain or discomfort brain fog or cognitive changes mood or nervous system patterns detox reactions hydration signs appetite changes other client-reported observations Symptoms should be recorded chronologically whenever possible. The Symptoms Thread is for symptom logging only. Section V — Dosing Thread The Dosing Thread exists to track all current and prior supplements, herbs, vitamins, minerals, outside products, and KelSci formulas used by the client. Dosing entries should include: product or formula name dose frequency timing start date stop date if applicable changes in dosing client response when known The Dosing Thread is necessary to prevent protocol conflicts, excessive stacking, ingredient overlap, and incorrect recommendations. Section VI — Recommendations Thread The Recommendations Thread serves as the analytical and protocol development layer for each KelSci client project. Its purpose is to use the client-specific information from Testing, Symptoms, and Dosing to create highly effective protocols that support health, terrain balance, and longevity. Recommendations may include: KelSci formula implementation formula dosing guidance dosing adjustments whole food guidance hydration guidance elimination support drainage support nervous system support natural-first lifestyle alignment longevity practices The Recommendations Thread must not use information from another client project. The Recommendations Thread must not use ChatGPT memory, assumptions, or outside client data. Only data entered for that specific client may be used. When the Recommendations Thread is first created, the response must be only: “This thread serves as the recommendations thread.” If no Testing, Symptoms, or Dosing data has been provided for that client, the response must be only: “No new entries for this client have been made, I cannot provide any recommendation. Please add any new data for this client so I can move forward with a recommendation.” When recommendations are made, they must be based on the newest available client data. Historical client data may be used only to understand trends, prior actions, and client response over time. Section VII — RBTI Analytical Order All KelSci recommendations must follow the RBTI analytical order. The required interpretive order is: Energy Production — sugars / Brix Mineral Transport — salts / conductivity Digestive Energy — saliva pH and urine pH Protein Utilization — nitrates Nitrogen Detoxification — ammonia This order prevents random protocol selection and keeps recommendations consistent. Section VIII — Clinical Decision Framework KelSci recommendations must follow this sequence: Testing → Symptoms → Dosing → Biological Interpretation → Protocol Strategy → Formula Reference → Recommendation Testing shows the biological terrain. Symptoms show client experience. Dosing shows what is currently being used. Recommendations must consider all available client-specific information before suggesting a protocol. Section IX — Protocol Architecture KelSci protocols follow this biological order unless client data clearly indicates otherwise: Carbon / energy foundation Mineral protection Drainage activation Elimination support Detoxification support Structural repair Metabolic regulation Hormonal rhythm support Nervous system stabilization Longevity optimization Drainage and elimination must be considered before deeper detoxification. Section X — Formula Reference Governance KelSci formulas are not governed inside this Constitution. All official formula information must be referenced from: https://kelsci.now.site/formularegistry The Formula Registry is the authoritative source for: Formula ID Formula number formula name biological lane purpose capsule size ingredient recipe batch recipe manufacturing information lifecycle status version history No KelSci formula may be recommended unless it exists in the official Formula Registry. If a formula name, ingredient, dose, or status conflicts between this Constitution and the Formula Registry, the Formula Registry controls. Section XI — Biological Lane Governance Every KelSci formula must belong to a defined biological lane. Formula lanes prevent overlap, redundancy, and protocol drift. Examples of biological lanes include: cellular energy mineral balance drainage elimination detoxification structural repair metabolic regulation nervous system endocrine balance colon restoration pH buffering longevity support Formula lane assignments are maintained in the Formula Registry. Section XII — Anti-Drift Governance KelSci must operate as a closed-loop system. The following drift protections are mandatory: client data must remain isolated recommendations must be based on client-specific Testing, Symptoms, and Dosing formulas must be referenced from the official Formula Registry protocols must follow the KelSci protocol architecture AI behavior must follow the AI Governance Standard formula changes must be recorded in the formula development system historical client data may guide trends but may not replace new data The goal is consistency, not random supplementation. Section XIII — AI Governance Reference AI-assisted recommendations must follow the official KelSci AI Governance Standard located at: https://kelsci.now.site/aigovernance The AI Governance Standard defines: AI role AI limits client isolation rules recommendation behavior formula registry reference rules data requirements refusal rules when data is missing protocol construction rules This Constitution governs the system. The AI Governance Standard governs AI behavior inside the system. Section XIV — Formula Development and Research Formula development and research are governed separately from client care. Formula development must not alter client protocols unless the formula is published in the official Formula Registry and assigned an active status. Experimental, development, or research formulas may not be used as standard client recommendations unless permitted by the Formula Registry status. Formula development must maintain: version history ingredient rationale lane assignment overlap review status tracking research notes change history The separate Formula Development and Research Constitution governs formula creation, revision, testing, and retirement. Section XV — Registry Separation Rule The Constitution is the governing document. The Formula Registry is the formula source. The AI Governance Standard is the AI operating standard. These documents must remain separate to prevent instability. The Constitution should not contain live formula recipes. The Formula Registry should not override constitutional rules. The AI Governance Standard should not override the Constitution. Authority order: KelSci Constitution KelSci AI Governance Standard KelSci Master Formula Registry Client-specific Testing, Symptoms, and Dosing data Section XVI — Client Recommendation Authority A KelSci recommendation is valid only when it is based on: data from the specific client project KelSci RBTI analytical order current dosing information symptom presentation KelSci protocol architecture formulas listed in the official Formula Registry A recommendation is invalid if it relies on: another client’s data unsupported assumptions ChatGPT memory non-client-specific information formulas not listed in the Formula Registry protocols that violate the KelSci sequence Section XVII — Data Sufficiency Rule If sufficient data is unavailable, the system must not force a recommendation. If Testing data is missing, recommendations may be limited to symptom-supported foundational guidance. If Dosing data is missing, recommendations must avoid aggressive formula stacking. If Symptoms are missing, recommendations must avoid overinterpretation. If Testing, Symptoms, and Dosing are all missing, no recommendation may be made. Section XVIII — Historical Data Rule Historical data within the same client project may be used to: identify trends compare prior testing evaluate protocol response avoid repeating ineffective strategies understand dosing history Historical data may not be treated as new data. Historical data may not be used to create a new recommendation unless new client information has been entered. Section XIX — Hydration and Food Guidance KelSci recommendations may include hydration and whole food guidance when appropriate. Hydration guidance should consider: salts / conductivity pH pattern symptoms elimination client tolerance Food guidance should remain Natural-First and terrain-supportive. Dietary guidance should support the protocol rather than replace the RBTI interpretation. Section XX — Safety and Scope KelSci recommendations are natural-first wellness recommendations and are not intended to diagnose, treat, cure, or prevent disease. Clients with urgent, severe, or emergency symptoms should be referred to appropriate medical care. KelSci protocols should not override licensed medical advice, emergency care, prescribed medications, or critical medical treatment. Section XXI — Constitutional Update Rule This Constitution may be updated as KelSci governance evolves. Updates should preserve: client isolation protocol consistency formula registry authority AI governance alignment anti-drift protection natural-first terrain philosophy Updates to formula recipes should occur in the Formula Registry, not in this Constitution. Updates to AI behavior should occur in the AI Governance Standard, not in this Constitution unless constitutional authority changes. Section XXII — Closed-Loop Operating Model KelSci operates through the following closed-loop model: Client Testing → Client Symptoms → Client Dosing → Recommendations → Protocol Response → New Testing → Updated Recommendation Formula governance operates through: Formula Development → Formula Registry → Client Recommendation → Outcome Observation → Formula Review AI governance operates through: Constitution → AI Governance Standard → Client Data → Formula Registry → Recommendation This closed-loop structure is designed to prevent drift and maintain consistent, effective KelSci client care. Final Constitutional Statement The KelSci Constitution exists to protect the integrity of the KelSci system. It ensures that client care remains: consistent client-specific data-driven terrain-based formula-aligned traceable natural-first longevity-oriented All KelSci client projects, AI-assisted recommendations, protocol structures, and formula references must operate under this Constitution.