Audit: QRS - Tart Cherry for Health & Longevity
Audit conducted on 15/08/2026 22:01 using AI4L / Opus 5
Summary
| Items | Count |
|---|---|
| Total | 93 |
| Passed | 83 |
| Failed | 0 |
| N/A | 10 |
| 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. | 🟢 | Protocol cells, time-to-effect values, all four benefit tiers, all four risk tiers, both gates, all 10 markers and the cadence trace to ER Therapeutic Protocol, Practical Considerations, Expected Benefits, Potential Risks & Side Effects, Key Interactions & Contraindications and Monitoring Protocol & Defining Success. |
| 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. | 🟢 | “Potential blunting of adaptations to endurance training”, “Unknown safety of concentrated forms in pregnancy and lactation” and “theoretical only” on the anticoagulant gate item all mirror ER hedging. |
| 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”). | 🟢 | Form-specific scope is retained on every contraindication (“juice and concentrate forms”, “concentrates, extracts and powders”), so no gate is broadened or narrowed. |
| 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. | 🟢 | Contraindications come only from the ER’s “Populations who should avoid Tart Cherry” list; Key Interactions only from the ER’s interaction bullets; no Benefit- or Risk-Modifying Factor appears in either gate. |
| 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 carries no PMIDs, no NCT identifiers, no author names and no brand names. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | The extract cell states “Argued to isolate the polyphenols from the sugar load” without naming any group; no attribution absent from the ER is added. |
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. | 🟢 | Sober, sceptical register matching the ER, including the funding caveat and the sugar-load trade-off. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Tiered benefits and risks plus concrete monitoring targets give an actionable, non-alarmist frame. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Content is stated as protocols observed in trials and markers worth tracking, not as orders. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No “should”, “must”, or treatment recommendation appears in the sheet’s own voice. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | Monitoring cadence is phrased descriptively (“Baseline draw before starting; urate and C-reactive protein rechecked at 6 weeks”). |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronoun occurs anywhere in the populated spans. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms appear only where the marker or drug class requires them; At-A-Glance uses “the gout-driving waste product” rather than “uric acid”. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | All gate and tier entries are single clauses; no cell carries a second sentence. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed across header, At-A-Glance, protocol, gates, cards and qualitative items. |
| 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. | 🟢 | Optimal functional ranges (hsCRP < 0.5 mg/L, fasting glucose 75–86 mg/dL) are pitched above conventional cut-offs, as for an optimizing 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. | 🟢 | Twice-daily dosing, 4–7 day loading windows and a 10-marker panel are presented without hedging on effort. |
| 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 simplification to a “just drink cherry juice” message; the sheet retains loading schedules and biomarker rechecks. |
| 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 foregrounds industry funding, the sugar load and thirty-fold product variability — the considerations that matter to a longevity-focused reader. |
| 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. | 🟢 | “Longevity” is used in the title; “anti-aging” appears nowhere. |
| 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. | 🟢 | “Gastrointestinal discomfort”, “serum urate”, “antihypertensive medication”, “sleep efficiency” — clinical register throughout, with plain language confined to At-A-Glance as item 7.4 requires. |
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 headings match exactly (lines 445, 491, 533, 564, 582, 615, 642, 646–648, 790); tier labels are unaltered in both the benefits and risks cards. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | page_title, header_topic, header_subline_date, header_subline_model, at_a_glance, action_1–3 (label/value/sub), time_1–3 (label/value/sub), stop_items, caution_items, benefits_high/medium/low/speculative, risks_high/medium/low/speculative, marker_1–10 (name/target/why), monitoring_cadence and qualitative_item_1–5 are all present. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | The non-variable template spans website="evidence_review", website="full_review" and website="audit" (lines 423, 426, 439) are untouched. |
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 feeding the QRS is empty; every benefit tier, risk tier, gate list and monitoring row has source content. |
| 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. | 🟢 | “Standard recovery protocol”, “Standard sleep protocol” and “Competing approach — standardized extract” are carried verbatim from the ER Therapeutic Protocol bullets; marker names match the ER biomarker table verbatim. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Time-to-effect labels track the ER’s own wording (“Recovery benefits”, “Sleep and inflammatory changes”, “Acute blood-pressure and urate responses”); no label is fabricated. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | The ER’s tier emojis and “⚠️ Conflicted” markers are stripped; emphasis is carried by CSS classes and bold tier labels only. |
| 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 to the per-section budget: gates are single-clause items, benefit and risk tiers are semicolon-joined headings, and the ER’s mechanistic and magnitude prose is dropped entirely. |
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, immediately after the doctype on line 1. |
| 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 descriptive text on line 2 precedes the opening delimiter. |
| 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. | 🟢 | Enclosed in an HTML comment; no metadata value is echoed into the body except the values required by items 6.3 and 6.4. |
| 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. | 🟢 | Only duration: "00:02" is quoted, and it contains a colon; all other values are bare and trimmed. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Line 4: er_filename: tart_cherry_2026-0825-1911_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 QRS.md version badge. |
| 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-0815-2144. |
| 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” — single word, 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” — nickname plus version, no qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9: qrs_filename: tart_cherry_2026-0825-1911_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 ten keys; 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., & for &) |
🟢 | Line 22: “Tart Cherry for Health & Longevity - Quick Reference Sheet”. |
| 6.2 | [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &) |
🟢 | Line 417: “Tart Cherry for Health & Longevity”. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: “08/15/2026”, matching qrs_creation_date 2026-0815-2144. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Line 425: “Opus 5”. |
| 6.5 | No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. | 🟢 | Header holds only the title and the template subline; the ER’s “Also known as” list is 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 |
🟢 | Condenses both Conclusion paragraphs: strongest signal, weaker signals, funding, sugar load and product variability. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 55 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | “A food, not a drug”, the strength/power finding, the four weaker signals, industry funding, the juice sugar load and the thirty-fold variability each map to a distinct Conclusion sentence. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | Uses “blood inflammation” for CRP and “the gout-driving waste product” for uric acid; no acronym appears. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial, author, year or sample size is named. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No effect size, confidence interval or P value; “thirty-fold” refers to product-strength variation, not a statistical result. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All five items come from the “Populations who should avoid Tart Cherry” list in that ER section. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All five ER avoidance populations are present, none added. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Lines 567–577: five <li> elements inside the 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. | 🟢 | Explanatory tails are stripped (“ingested fructose causes hypoglycaemia and liver injury”, “extract capsules remain acceptable”, “pending symptom control”); only the form-scope qualifier required by item 1.3 is retained. |
| 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). | 🟢 | “(HbA1c > 8.0%)” and “(Rome IV, diarrhoea-predominant)” are preserved, the latter trimmed from the ER’s “Rome IV criteria”. |
| 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 uses “>” only as a numeric threshold (“HbA1c > 8.0%”), which is self-interpreting; no ranking notation occurs. |
| 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 names five such populations and the section is correspondingly populated. |
| 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 nine items map one-to-one to the nine ER interaction bullets. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | No overlap with the five contraindication entries. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Lines 585–605: nine <li> elements inside the 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. | 🟢 | Mechanistic and management prose (“Separated dosing and two weeks of home blood pressure readings address it”, “mitigated by taking both with food”) is stripped; only the applicability qualifiers permitted by 9.5 remain. |
| 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). | 🟢 | Named drug examples are retained and trimmed to one per class (lisinopril, losartan, amlodipine; glipizide, empagliflozin), and the antioxidant thresholds “above 1,000 mg/day” and “above 235 mg/day” are preserved. |
| 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’s interaction bullets contain no ranking notation. |
| 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 names nine such interactions and the section is correspondingly 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 ER Therapeutic Protocol bullets. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | The two named standard protocols (recovery, sleep) plus the standardized-extract alternative — the three bullets that specify an actual dose. |
| 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 supplies well over three actionable aspects; all three 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 (lines 449–486) carry substantive ER-derived content; none is empty or placeholder. |
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 | 🟢 | Muscle recovery (4–7 days), sleep and inflammation (7–14 days), acute urate and blood pressure (1–3 hours) — the three windows given in the ER “Time to effect” bullet. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Muscle recovery is the ER’s only High benefit and leads; sleep/inflammation are Medium; the acute urate and blood-pressure pairing spans Medium and Low and sits last. |
| 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 windows; 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 (lines 497–526) carry ER-derived content, including the 8-hour metabolite clearance from the ER “Half-life” bullet. |
| 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’s Practical Considerations section provides explicit time-to-effect data. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | All twelve entries are ER benefit headings, tier for tier. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans present at lines 535, 541, 547, 555. |
| 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. | 🟢 | Headings only; every “Magnitude” figure, mechanism sentence and “⚠️ Conflicted” marker is dropped. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical survives in any of the four tiers. |
| 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 tiers have ER content (1 high, 4 medium, 6 low, 1 speculative). |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | All six entries are ER risk headings, tier for tier. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans present at lines 617, 623, 629, 634. |
| 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. | 🟢 | Headings only; the osmotic mechanism, the 7.94 mg/dL glucose figure and the 143–2,140 mg polyphenol range are all omitted. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical survives in any of the four tiers. |
| 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. | N/A | All four tiers have ER content (2 high, 2 medium, 1 low, 1 speculative). |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Rows mirror the ER Monitoring Protocol & Defining Success biomarker table. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All 10 ER biomarkers appear, with targets and “why” text carried verbatim; the creatine kinase target is condensed to the usable signal (“Change from the individual’s own post-exercise baseline”). |
| 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 780–784 reproduce the ER cadence: baseline, urate and CRP at 6 weeks, glucose/HbA1c/lipids at 12 weeks, then every 6–12 months. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | All five 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 five ER qualitative markers are present verbatim (lines 793–819), none omitted or added. |
Issues 15/08/2026 22:01
Pass rate 100.00%. No issues found.
Issues 15/08/2026 21:54
- 9.5 — Example drug lists dropped: The Antihypertensive medication item (line 585) reduces the ER’s six named example drugs (lisinopril, ramipril, losartan, valsartan, amlodipine, diltiazem; ER 321) to bare class names, and the Glucose-lowering medication item (line 587) drops glipizide, glyburide and empagliflozin (ER 325), so both parenthetical drug lists are dropped entirely rather than trimmed.
Fixes 15/08/2026 21:54
- 9.5 — Example drug lists restored: Added representative ER-named example drugs to the two Key Interactions items that had dropped them — “Antihypertensive medication (ACE inhibitors, ARBs, calcium channel blockers; lisinopril, losartan, amlodipine)” and “Glucose-lowering medication (insulin, sulfonylureas, SGLT2 inhibitors; glipizide, empagliflozin)”.
Issues 15/08/2026 21:49
- 1.3 — Attributed claim stated as fact: [action_3_sub] at line 484 presents “Isolates the polyphenols from the sugar load without changing the outcome” as established fact, while ER line 375 attributes it as an argument made by the powder-trial groups (“arguing it isolates the polyphenols from the sugar load without changing the outcome”).
Fixes 15/08/2026 21:49
- 1.3 — Attributed claim stated as fact: [action_3_sub] changed from “Isolates the polyphenols from the sugar load without changing the outcome” to “Argued to isolate the polyphenols from the sugar load without changing the outcome”, restoring the ER’s attributed framing.