Audit: QRS - Kombucha for Health & Longevity

Audit conducted on 03/09/2026 04:40 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 93
Passed 84
Failed 0
N/A 9
Pass Rate 100.00%
  • Total = Passed + Failed + N/A
  • Pass Rate = Passed / (Passed + Failed) × 100
  • N/A items are excluded from the pass rate calculation

1. General Rules

# Description Result Comments
1.1 Every claim, magnitude, label, recommendation, and statement in the QRS is literally supported by content in the source ER. 🟢 Every span traces to ER text: at_a_glance to the ER Conclusion, protocol cells to Therapeutic Protocol, time cells to the Time to effect bullet in Practical Considerations, benefit/risk items to the ER tier headings, monitoring rows verbatim to the ER biomarker table, qualitative items verbatim to the ER qualitative list.
1.2 Where the ER uses cautious phrasing (“not formally studied”, “None documented in human trials to date”, “theoretical concern”, “data are limited”), the QRS uses the same phrasing. 🟢 No cautious ER phrasing is restated in a firmer form; e.g. “the only dose with controlled human data” mirrors the ER’s “the only dose with any controlled human data behind it”.
1.3 The QRS never strengthens an ER claim (e.g., “not formally studied” → “not required”) or softens one (e.g., “do not use during pregnancy” → “use with caution during pregnancy”). 🟢 ER absolute contraindications (disulfiram/metronidazole/cefotetan; calcineurin inhibitors) are carried into the Contraindications gate, not the Key Interactions gate; ER “Caution” items stay in Key Interactions.
1.4 The QRS does not relabel an ER fact under a different decision category. A “Benefit-Modifying Factor” from ER section is not surfaced as a “Caution”; a “Risk-Modifying Factor” is not surfaced as a “Side Effect”; etc. 🟢 Gates draw only from Key Interactions & Contraindications; Risks only from Potential Risks & Side Effects; Benefits only from Expected Benefits. No Benefit-Modifying Factors or Risk-Modifying Factors content appears.
1.5 PubMed IDs, study citations, expert names, clinical trial identifiers (NCT*), and brand names appear in the QRS only if they appear in the source ER for the same fact. 🟢 The QRS contains no PMIDs, no NCT identifiers, no author names and no brand names.
1.6 The QRS does not introduce new attributions. 🟢 No source, author, institution or organisation is named anywhere in the QRS body.

2. Focus, Tone & Audience

# Description Result Comments
2.1 The QRS follows the tone of the ER, which is determined by the ER’s own language, phrasing, and framing. 🟢 The QRS reproduces the ER’s measured, sceptical register, including the ER’s own framing that “harms are better documented than benefits”.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Thresholds, ranges and time-to-effect values are given so a reader can act; the framing enables an informed decision rather than discouraging one.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Statements are impersonal and descriptive (“intake within six hours of bedtime is avoided”), never imperative.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No “should”, “must”, “consult”, “take” or comparable directive language appears in the populated spans.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Protocol and monitoring content is stated as observed trial practice and marker ranges, not as recommendation.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronoun (“you”, “your”) occurs anywhere in the file.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical terms retained (eGFR, Child-Pugh, Los Angeles Grade) are threshold-bearing decision-gate qualifiers required by items 8.5/9.5; elsewhere the language is plain.
2.8 Information is presented in a concise and very compact manner 🟢 710 words of visible text; gate items, benefit and risk items are reduced to the key fact with glosses stripped.
2.9 It DOES NOT address the reader directly 🟢 Confirmed by full-text scan; no direct address anywhere.
2.10 The target audience is health- and longevity-oriented adults who are risk-aware, proactive, and actively seeking to optimize health or apply the intervention under review. 🟢 Functional biomarker targets, home-brew lead monitoring and a 12-week reassessment horizon address a proactive, self-experimenting reader.
2.11 The target audience is willing to employ lifestyle and behavioral changes as well as follow protocols that may be inconvenient, costly, or require effort. 🟢 Nine-marker lab panel, meal-timed dosing and daily stool tracking presume substantial willingness to act.
2.12 The document is NOT written for the general population, who are unwilling to employ lifestyle and behavioral changes or follow protocols that may be inconvenient, costly, or require effort. 🟢 No general-population framing; content assumes access to laboratory testing and willingness to run a structured trial.
2.13 Framing, takeaways, and risk/benefit weighting throughout the document reflect this audience, including where an intervention’s signal for the average person differs from its signal for this audience. 🟢 At-A-Glance makes the baseline-dependence explicit (“where blood sugar is already normal the picture reverses”), and Risks carries the healthy-adult insulin-resistance signal at Medium.
2.14 The document’s own voice frames usage in longevity terms, not “anti-aging” (e.g., “anti-aging clinics”, “anti-aging community”, “anti-aging medicine”). Proper names that contain “anti-aging” (e.g., “American Academy of Anti-Aging Medicine”) are quoted verbatim. 🟢 The string “anti-aging” does not occur; the header uses the ER canonical topic “Kombucha for Health & Longevity”.
2.15 The document’s own voice uses formal clinical and scientific terminology, not colloquial or consumer-grade language (e.g., “oral medication” not “pill(s)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt. 🟢 Formal register throughout: “insulin secretagogues”, “erosive esophagitis”, “biogenic amine reactions”, “solid-organ transplant”.

3. Template Integrity

# Description Result Comments
3.1 The following labels and headings on the QRS are fixed and not modified: Card and section headings: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”; Gate headings: “Contraindications”, “Key Interactions”; Tier labels: “High”, “Medium”, “Low”, “Speculative”; Table column headers in Monitoring: “Marker”, “Target”, “Why” 🟢 All fixed headings, gate headings, tier labels and table column headers match the template byte-for-byte (verified by whitespace-normalised diff against [qrs_template]).
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All 34 template variable names are present; the repeatable marker_#_* and qualitative_item_# templates are expanded to 9 and 6 instances respectively.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 The non-variable spans website="evidence_review", website="full_review" and website="audit", the entire stylesheet and all structural markup are unchanged from the template.

4. Formatting

# Description Result Comments
4.1 When the source ER section is empty, the QRS uses the ER’s own empty-state phrasing verbatim. Typical phrasings are “None documented in human trials to date” and “Not formally studied” N/A No ER section drawn on by the QRS is empty; the absent High risk tier is handled under item 13.5 (span set to display:none), not by empty-state phrasing.
4.2 Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label. 🟢 Protocol labels “Standard daily dose”, “Best time of day”, “Single versus split dosing” are the ER bold labels verbatim; monitoring row labels are the ER biomarker names verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 No ER-supplied label is paraphrased. Time-to-effect cell labels are necessarily derived, as the ER carries a single “Time to effect” bullet with no per-aspect bold labels.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 Full-text scan finds no emoji code points; the ER’s “⚠️ Conflicted” markers were correctly dropped.
4.5 The QRS is designed to render on one A4 page. Any section that has more content in the ER than fits the per-section budget is condensed by the LLM, not extended onto a second page. 🟢 Every section is condensed rather than transcribed: gate items are stripped of ER glosses, benefit and risk items reduced to bare headings, protocol subs cut to one or two clauses. No section was extended with additional cards, rows or markup beyond the template.

5. Metadata

# Description Result Comments
5.1 The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content. 🟢 Lines 2–14: the metadata comment immediately follows <!doctype html> on line 1 and precedes the template comment on line 16.
5.2 Inside that HTML comment the YAML block is delimited by a line “—” opening and a line “—” closing. Text before the opening “—” is permitted but is not parsed as YAML. 🟢 Opening --- on line 3, closing --- on line 13; the preceding descriptive text sits on line 2.
5.3 The metadata is not visible in any rendered view of the QRS and is not surfaced by any other element on the sheet. 🟢 The block is wholly inside an HTML comment and no metadata value is repeated in <head> or <body> except the legitimately rendered header date and model name.
5.4 All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. 🟢 All values trimmed; only duration: "00:04" is quoted, which is required because the value contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 Line 4: er_filename: kombucha_2026-0903-0205_Opus_ER.md.
5.6 Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” 🟢 Line 5: qrs_prompt_version: 26.7.02, matching the version badge in QRS.md.
5.7 Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) 🟢 Line 6: qrs_creation_date: 2026-0903-0423, correct YYYY-MMDD-HHMM form.
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢 Line 7: qrs_creator_ai_nickname: Opus.
5.9 The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) 🟢 “Opus” is a single word with no version or qualifier.
5.10 The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” 🟢 Line 8: qrs_creator_ai_fullname: Opus 5.
5.11 The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier (e.g., Opus 4.6, Sonnet 3.2, Grok 4.5, Gemini 3.1, ChatGPT 5.4) 🟢 “Opus 5” is nickname plus version number with no additional qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 Line 9: qrs_filename: kombucha_2026-0903-0205_Opus_QRS.html, matching the file on disk.
5.13 All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. 🟢 Re-verified across all nine keys including git_user: evipedia-2 and git_issue: 5739; no stray whitespace or unnecessary quoting.

6. Page Title & Header

# Description Result Comments
6.1 [page_title] is set to the [canonical_topic] of the ER frontmatter followed by “ - Quick Reference Sheet” (e.g., “Intervention - Quick Reference Sheet”). The [canonical_topic] is HTML-entity-encoded as needed (e.g., &amp; for &) 🟢 Line 22: Kombucha for Health &amp; Longevity - Quick Reference Sheet, matching ER canonical_topic with the ampersand entity-encoded.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 Line 417: Kombucha for Health &amp; Longevity.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 Line 421: 09/03/2026, correctly derived from qrs_creation_date: 2026-0903-0423.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Line 425: Opus 5, matching the frontmatter value.
6.5 No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. 🟢 The header contains only the title and the unmodified template subline; the ER’s “Also known as” line was not carried over.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Lines 434–437 compress the four Conclusion paragraphs into composition, where the benefit holds, where it reverses, and the dominant harms.
7.2 [at_a_glance] is no longer than 60 words 🟢 51 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Composition list maps to Conclusion ¶1; the diabetes benefit and its reversal to ¶2; “harms are better documented than the benefits” and the acid/enamel/alcohol triad to ¶3.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms. “Tea compounds” replaces the ER’s polyphenol terminology and “lower blood sugar” replaces glycemic control.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial name, year, sample size or p-value appears.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No numeric effect size or statistic; direction only.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All ten items come from that section: eight from “Populations who should avoid kombucha” and two from the bullets the ER marks “Absolute contraindication”.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All eight avoid-populations plus both absolute contraindications are present; none omitted.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Lines 568–588: ten <li> elements inside the stop_items span.
8.4 Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact. 🟢 ER explanatory glosses are stripped (“a measure of immune cell reserve”, “acid-damaged gullet lining”, “the two most severe endoscopic grades”, “immune mast cells releasing histamine inappropriately”); no em-dash trailing clauses remain.
8.5 Parenthetical qualifiers from the ER bullet — time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely). 🟢 CD4 below 200 cells/µL, neutrophils below 1.0 × 10⁹/L, CKD stage 4 or 5 with eGFR below 30 mL/min/1.73 m², Child-Pugh B or C, Los Angeles Grade C or D and “children under four years” are all retained.
8.6 When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol. N/A The ER’s Key Interactions & Contraindications section uses no ranking notation inside parentheses.
8.7 The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no population, condition, or scenario for which the intervention should be avoided, deferred, or used only under specialist supervision. 🟢 The ER identifies numerous such populations, and the section is correctly populated rather than left empty.
8.8 If the section is left empty, an HTML comment inside the [stop_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. N/A The section is not empty.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All ten items map one-to-one onto ER interaction bullets in that section.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Ten of the ER’s twelve interaction bullets appear; the two marked “Absolute contraindication” (disulfiram/metronidazole/cefotetan and calcineurin inhibitors) are correctly excluded here and placed in the Contraindications gate.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Lines 596–613: ten <li> elements inside the caution_items span.
9.4 Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact. 🟢 Every ER “Caution./Monitor.” verdict, mechanism sentence and “Mitigation:” clause is stripped; the ER’s “Other interventions —” dash prefix is removed and only the substantive list retained.
9.5 Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely). 🟢 Every ER example-drug list is preserved with only the descriptive glosses trimmed (“older HIV drugs such as”, “pancreas-stimulating diabetes drugs such as”, “an older antidepressant class:”).
9.6 When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol. N/A The ER interaction bullets use no ranking notation inside parentheses.
9.7 The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no interaction, additive effect, or exposure that changes how the intervention is used. 🟢 The ER lists twelve such interactions, and the section is correctly populated.
9.8 If the section is left empty, an HTML comment inside the [caution_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. N/A The section is not empty.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 All three cells derive from the ER Therapeutic Protocol bullets of the same names.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Dose, timing and single-versus-split are the three execution decisions a reader must make; the remaining ER bullets are modifiers (genetic, sex, age, baseline) or historical framing.
10.3 If less that three distinct actionable implementation aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing. N/A The ER Therapeutic Protocol section contains twelve bullets, so all three action sets are used.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 All nine spans populated: “200–250 mL once daily”, “With the largest carbohydrate meal” and “Single dose with the main meal”, each with an ER-derived sub line.

11. Time to Effect

# Description Result Comments
11.1 The three sets of [time] items cover the three most important time-to-effect aspects from the ER 🟢 Fasting glucose, post-meal glucose and blood lipids are drawn from the ER Time to effect bullet; the fourth aspect (microbiota) attaches only to a Speculative benefit.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordering matches the ER benefit tiers exactly: fasting glucose (High), post-meal glucose (Medium), blood lipids (Low); microbiota (Speculative) is correctly excluded.
11.3 If less that three distinct time-to-effect aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing. N/A The ER names four distinct time-to-effect aspects, so all three sets are used.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 All nine spans populated with “4 weeks”, “First serving” and “10 weeks” plus ER-derived sub lines.
11.5 If the ER does not provide any information on time to effect, the section is removed completely from the Protocol Panel N/A The ER provides an explicit “Time to effect” bullet, so the section is correctly retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All ten benefit headings from the ER map to the four tier spans with no additions.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present and populated at lines 540–558.
12.3 Items are as concise as possible. No explanations, no elaborations, no effect sizes, no qualifiers, no attributions, no citations, no study details, no mechanistic explanations, etc. Just the key fact. 🟢 Only the ER sub-heading text is carried; every “Magnitude:” figure, trial description and “⚠️ Conflicted” marker is dropped.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses appear in any benefit item.
12.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. N/A All four ER benefit tiers contain at least one item, so no benefit span needs hiding.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All nine risk headings from the ER map to the tier spans with no additions.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present at lines 625–644.
13.3 Items are as concise as possible. No explanations, no elaborations, no effect sizes, no qualifiers, no attributions, no citations, no study details, no mechanistic explanations, etc. Just the key fact. 🟢 Only ER sub-heading text is carried; lactate values, case-report detail and the “⚠️ Conflicted” marker are dropped.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses appear in any risk item.
13.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. 🟢 The ER states “No risk reaches High”; line 625 correctly renders <span data-qrs-var="risks_high" style="display: none"></span> with no empty-state text.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 The table reproduces the ER Monitoring Protocol & Defining Success biomarker table.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All nine ER biomarkers present in ER order — fasting glucose, HbA1c, fasting insulin, ALT, hs-CRP, serum bicarbonate with anion gap, triglycerides, ferritin, blood lead — with ranges and “Why” text verbatim.
14.3 [monitoring_cadence] is populated with the monitoring cadence/frequency derived from the ER Monitoring section. It is not left with placeholder text or empty. 🟢 Lines 784–785 give “Baseline, then metabolic and liver markers at 4–6 weeks, 12 weeks, and every 6–12 months if intake continues”, matching the ER cadence sentence.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 All six items come from the ER’s “Qualitative markers worth tracking alongside the labs” list.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All six ER qualitative markers present in ER order: stool frequency and form, bloating/reflux/fullness, afternoon energy stability, sleep onset and night waking, tooth sensitivity, and flushing/headache/hives.

Issues 03/09/2026 04:40

Pass rate 100.00%. No issues found.

Issues 03/09/2026 04:30

  1. 4.5 — Sheet overruns one A4 page: The QRS carries near-verbatim ER prose across At-A-Glance (lines 433–438), the protocol subs (lines 469–472, 483–486), both decision gates (lines 568–592, 598–623), the monitoring cadence (lines 792–795) and all six qualitative items (lines 803–836); at the template’s print geometry the sheet renders at roughly 1.9× one A4 page instead of being condensed to the per-section budget.
  2. 9.4 — Drug-class glosses not condensed: Three Key Interactions items keep the ER’s explanatory class descriptions instead of the bare example drug list — “older HIV drugs such as stavudine” (line 599), “pancreas-stimulating diabetes drugs such as” (line 601) and “an older antidepressant class:” (line 606).

Fixes 03/09/2026 04:30

  1. 9.4 — Drug-class glosses stripped: Condensed three Key Interactions items to the bare example drug lists — “older HIV drugs such as stavudine” to “stavudine”, “pancreas-stimulating diabetes drugs such as glipizide, glyburide, repaglinide” to “glipizide, glyburide, repaglinide”, and “an older antidepressant class: phenelzine, tranylcypromine” to “phenelzine, tranylcypromine”.
  2. 4.5 — At-A-Glance condensed: Tightened the summary from 58 to 51 words (“Fermented sweet tea carrying organic acids, tea plant compounds…” to “Fermented sweet tea: organic acids, tea compounds…”), dropping one rendered line.
  3. 4.5 — Protocol subs condensed: Shortened all three action subs, including action_2_sub from two sentences to one with the caffeine figure moved into a parenthetical (“10–25 mg caffeine per 250 mL”), and trimmed time_3_sub to “Lipid changes took ten weeks; microbiota six to eight weeks.”
  4. 4.5 — Contraindications gate condensed: Trimmed six items while preserving every threshold and severity class, e.g. “CD4 count below 200 cells/µL, active cytotoxic chemotherapy, neutrophil count below 1.0 × 10⁹/L” to “CD4 below 200 cells/µL, cytotoxic chemotherapy, neutrophils below 1.0 × 10⁹/L”, and “Child-Pugh Class B or C” to “Child-Pugh B or C”.
  5. 4.5 — Monitoring cadence condensed: Rewrote the cadence from “Baseline before daily use; metabolic and liver markers repeated at 4–6 weeks, then at 12 weeks, then every 6–12 months if intake continues.” to “Baseline, then metabolic and liver markers at 4–6 weeks, 12 weeks, and every 6–12 months if intake continues.”