Audit: QRS - Beta-Alanine for Health & Longevity
Audit conducted on 22/09/2026 16:38 using AI4L / Opus 5
Summary
| Items | Count |
|---|---|
| Total | 94 |
| Passed | 83 |
| Failed | 0 |
| N/A | 11 |
| 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. | 🟢 | Verified span by span against the ER: protocol (ER 277–285), time to effect (ER 314), benefits (ER 147–187), risks (ER 206–230), gates (ER 244–260), monitoring table (ER 336–343), qualitative markers (ER 347–352). |
| 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. | 🟢 | Cautious framing preserved: “theoretical additive effect” (marker_3_why), “if it exists” (marker_4_why), “no established clinical target” (marker_8_target), “absence of any confirmatory trial” (qualitative_item_6). |
| 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”). | 🟢 | Contraindication thresholds carried at ER strength (ALT >3× upper reference limit, eGFR <30, Child-Pugh C); no gate softened to “caution”. |
| 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. | 🟢 | Benefit-modifying and risk-modifying factors from ER lines 192–199 and 235–239 are not surfaced in the gates; gates draw only from ER 244–260. |
| 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. | 🟢 | QRS carries no PMIDs, study citations, expert names, NCT identifiers, or brand names. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions present; ER attributions (Derave/Ghent, ISSN, CarnoSyn/NAI) are all omitted. |
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. | 🟢 | Matches the ER’s measured, plain, non-promotional register. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Expert and data-driven (thresholds, ranges, tiers) while remaining readable. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Presents tiers, gates and ranges; no prescriptive instruction to a patient. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | Fixed template disclaimer only; body text describes what trials used rather than directing care. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | Descriptive throughout; no “recommend”, “advise”, or “should” in the document’s own voice. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person address anywhere in the rendered body. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Plain language used throughout; retained technical terms (paresthesia, aquagenic pruritus) are the ER’s own section headings, whose glosses 12.4/13.4 require stripping. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Fits comfortably within the one-page budget; gate and tier items are single clauses. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed: no “you”/”your” in the rendered text. |
| 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. | 🟢 | Framing assumes a proactive reader who will load, split doses and run a laboratory panel. |
| 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. | 🟢 | Protocol panel presents a 4-to-12-week loading course with split dosing and a maintenance phase. |
| 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. | 🟢 | Monitoring card assumes functional-range laboratory testing, not general-population screening. |
| 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. | 🟢 | Benefit tiers carry the ER’s narrow scope (exercise capacity high; cognition confined to older adults with below-normal scores). |
| 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. | 🟢 | No occurrence of “anti-aging” in the document. |
| 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)”; “oral” / “administered orally” not “taken by mouth” / “given by mouth”; “injection” not “shot”; “adverse event” not “bad reaction”). This holds on EVERY surface, including the QRS lede — the stricter plain-language bar (see 2.7) does not license lay phrasing for route of administration. Direct quotes from sources are exempt. | 🟢 | No colloquial route-of-administration or adverse-event phrasing; “dietary supplement”, “doses”, “with food” are formal register. |
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 verbatim: Protocol (line 446), Time to effect (488), Benefits (532), Risk & Side Effects (596), Monitoring (613), Qualitative Assessment (747), Contraindications (555), Key Interactions (570), Marker/Target/Why (617–619), tier labels High/Medium/Low/Speculative. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All 34 template variable names present; marker_#* and qualitative_item# expanded to 8 and 6 concrete rows respectively. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | Diff against [qrs_template] shows head, styles, website= spans and footer byte-identical; only variable regions differ. |
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 required empty-state carry-over; absent risk tiers are governed by 13.5, which mandates display:none rather than 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 verbatim from ER bold labels: “Standard loading regimen”, “Maintenance regimen”, “Single versus split dosing” (ER 277, 279, 284). |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | No invented or paraphrased labels; Monitoring “Why” cells reproduce the ER’s “Why Measure It?” column verbatim. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji present in the body; ER tier emoji and the ⚠️/⭕️ benefit markers are stripped. |
| 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. | 🟢 | Content volume is within the single-A4 budget; ER bullets are condensed rather than carried in full. |
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. | 🟢 | Metadata comment opens on line 2, directly after <!doctype html>. |
| 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. | 🟢 | YAML delimited by “—” at lines 3 and 13; the preamble text sits before 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 and not echoed anywhere on the sheet. |
| 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 is quoted, which its colon requires. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | er_filename: beta_alanine_2026-0914-0003_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]” | 🟢 | qrs_prompt_version: 26.9.22, 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) | 🟢 | qrs_creation_date: 2026-0922-1610. |
| 5.8 | The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” | 🟢 | 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) | 🟢 | Single word, no version. |
| 5.10 | The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” | 🟢 | 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) | 🟢 | Nickname plus version number, no qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | qrs_filename matches 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; 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 &) |
🟢 | “Beta-Alanine for Health & Longevity - Quick Reference Sheet”, with & entity-encoded. |
| 6.2 | [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &) |
🟢 | “Beta-Alanine for Health & Longevity”, matching ER canonical_topic. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | 09/22/2026, matching qrs_creation_date 2026-0922. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | “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 carries only title and the template subline; the ER “Also known as” line is correctly absent. |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] opens by saying what the intervention is — its kind (e.g., dietary supplement, prescription medication, peptide, plant, procedure, practice) — and what it is used for, in plain language, before any verdict on the evidence | 🟢 | Opens “Beta-alanine is a dietary supplement, an amino acid the body does not use to build proteins, taken to raise stores of carnosine”, naming kind and purpose before any verdict. |
| 7.2 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Condenses ER Conclusion lines 368–372: mechanism, best-supported effect, tolerability. |
| 7.3 | [at_a_glance] is no longer than 70 words | 🟢 | 70 words, at the limit. |
| 7.4 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Each clause traces to a distinct ER Conclusion passage (368, 370, 372) plus ER 318 for “dietary supplement”. |
| 7.5 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms; “buffers acid” rendered as “soaks up acid” and carnosine explained inline. |
| 7.6 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial names, years, sample sizes or p-values. |
| 7.7 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No effect sizes or statistics; “more than a hundred human studies” is the ER’s own count, not a result. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Drawn from ER “Populations who should avoid Beta-Alanine” (ER 254–260). |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All five ER populations represented, none added. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Five <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. | 🟢 | Trailing em-dash clauses stripped from all five items (e.g., “— no clinical evidence…”, “— amino-acid handling is altered and untested at these stages”). |
| 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). | 🟢 | Parentheticals preserved and trimmed: “(Child-Pugh Class C)”, “(eGFR under 30 mL/min/1.73 m²)”; thresholds intact. |
| 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 | ER Key Interactions & Contraindications 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. |
N/A | Section is not left empty; ER names five populations that should avoid beta-alanine. |
| 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 | Section is not left empty. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Drawn from ER “Key Interactions & Contraindications” bullets (ER 244–252). |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | All nine ER interactions present; no overlap with the contraindication list. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Nine <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. | 🟢 | Reduced to “agent: verdict” form; mechanistic rationale and mitigation sentences dropped. |
| 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). | 🟢 | Example drug lists preserved: metformin/glipizide/insulin glargine/semaglutide; methotrexate/isotretinoin/high-dose acetaminophen/alcohol; cetirizine/loratadine. |
| 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 | ER Key Interactions & Contraindications uses 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. |
N/A | Section is not left empty; ER names nine interactions. |
| 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 | Section is not left empty. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Protocol section |
🟢 | Drawn from ER Therapeutic Protocol (ER 277–290). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Loading, maintenance and split dosing are the three load-bearing implementation decisions in the ER protocol. |
| 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 | ER Therapeutic Protocol provides 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 action fields carry ER-derived content; action_3_sub adds the ER “Best time of day” dosing-with-food fact (ER 285), also within the Protocol section. |
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 | 🟢 | Covers the three aspects named in ER Practical Considerations line 314: performance, cognition, carnosine loading. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered High-intensity exercise capacity (High tier) → Cognitive function (Medium tier) → Muscle carnosine loading, reversing the ER’s narrative order to follow benefit magnitude. |
| 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 | ER names three distinct time-to-effect aspects; 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 time fields populated from ER line 314. |
| 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 | ER provides time-to-effect information (Practical Considerations, line 314). |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | Drawn from ER Expected Benefits (ER 147–187). |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four tier variables present and populated. |
| 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. | 🟢 | Reduced to the ER benefit headings; magnitudes and supporting prose omitted. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | ER heading markers “⚠️ Conflicted” and “⭕️ Not Central to Health & Longevity” stripped. |
| 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 benefit tiers have items in the ER; no sub-section is absent. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | Drawn from ER Potential Risks & Side Effects (ER 206–230). |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four tier variables present. |
| 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. | 🟢 | Reduced to the ER risk headings; odds ratios and credible intervals omitted. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | Paresthesia and taurine/histidine glosses stripped. |
| 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. | 🟢 | ER records no Medium and no Low risk (ER 220–225); both spans carry style=”display: none” and no empty-state text. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Drawn from ER Monitoring Protocol & Defining Success (ER 334–343). |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All eight ER biomarkers listed with matching targets: ALT, AST, fasting glucose, HbA1c, fasting insulin, eGFR, hs-CRP, muscle carnosine. |
| 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. |
🟢 | Populated with the ER cadence from line 332, including the 4-and-12-week glucose review under glucose-lowering medication. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Drawn from ER Monitoring Protocol & Defining Success qualitative list (ER 347–352). |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All six ER qualitative markers listed in ER order. |
Issues 22/09/2026 16:38
Pass rate 100.00%. No issues found.
Issues 22/09/2026 16:31
- 13.3 / 13.4 — Added parenthetical gloss in risks: [risks_high] at line 600 reads “Paresthesia (skin tingling); small increase in alanine aminotransferase”; the parenthetical gloss is an explanation absent from the ER heading and must be stripped under the Risks section’s no-parentheses rule.
Fixes 22/09/2026 16:31
- 13.3 / 13.4 — Stripped parenthetical gloss in risks: Changed [risks_high] from “Paresthesia (skin tingling); small increase in alanine aminotransferase” to “Paresthesia; small increase in alanine aminotransferase”, removing the added parenthetical explanation.
Issues 22/09/2026 16:26
- 9.2 — Two ER interactions omitted: The Key Interactions gate lists 7 of the 9 interaction bullets in the ER’s
Key Interactions & Contraindicationssection; “Antihistamines (cetirizine, loratadine): no interaction, but no benefit either” (ER line 249) and “L-histidine co-supplementation: no interaction of consequence” (ER line 252) are missing, although comparable no-concern bullets (sodium bicarbonate, creatine monohydrate) were carried over.
Fixes 22/09/2026 16:26
- 9.2 — Missing interactions added: Added the two omitted ER interaction bullets to the Key Interactions gate — “Antihistamines (cetirizine, loratadine): no interaction, no benefit either” and “L-histidine co-supplementation: no interaction of consequence” — bringing the gate to all 9 ER interaction items.
Issues 22/09/2026 16:21
- 9.2 — Creatine interaction omitted: The ER’s “Creatine monohydrate: no safety concern; additive” interaction (ER line 246) is absent from the Key Interactions gate, even though the parallel “Sodium bicarbonate: no safety concern, additive by design” bullet was carried over.
Fixes 22/09/2026 16:21
- 9.2 — Creatine interaction added: Added
<li>Creatine monohydrate: no safety concern, additive</li>to the Key Interactions gate, alongside the existing sodium bicarbonate item, restoring the ER interaction bullet at ER line 246.
Issues 22/09/2026 16:15
- 1.3 — Side-effect claim overstated: At-A-Glance (lines 437-438) asserts “Temporary skin tingling is the only side effect” without the ER Conclusion’s scoping clause “across more than a hundred human studies”, and the categorical form contradicts the sheet’s own High-tier risk entry for a small ALT increase (line 597).
Fixes 22/09/2026 16:15
- 1.3 — Side-effect claim overstated: Restored the ER Conclusion’s scoping clause in At-A-Glance, changing “Temporary skin tingling is the only side effect.” to “Across more than a hundred human studies, temporary skin tingling was the only side effect.” (70 words, within the 70-word budget).