Audit: QRS - Taurine for Health & Longevity
Audit conducted on 11/01/2026 09:23 using AI4L / Opus 5.5
Summary
| Items | Count |
|---|---|
| Total | 97 |
| Passed | 86 |
| 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. | 🟢 | Lede, Protocol, Time to effect, gates, tiers, Monitoring and Qualitative content all trace to ER text (e.g., Conclusion, Therapeutic Protocol, Practical Considerations, Monitoring table). |
| 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. | 🟢 | Hedged ER wording kept where carried: “No established target” (line 700), “Theoretical (inferred from mechanism)” block, lede “is unclear”. |
| 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”). | 🟢 | No strengthening or softening found; contraindications remain avoid-populations as in ER Key Interactions & Contraindications. |
| 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 from ER “Populations who should avoid”; interactions from Documented/Theoretical lists; no modifier factor relabeled. |
| 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. | 🟢 | No PMIDs, citations, expert names, NCT IDs or brand names appear in the QRS. |
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. | 🟢 | Measured, evidence-weighted tone matches the ER. |
| 2.2 | The tone of the QRS is expert, accessible, objective, and data-driven | 🟢 | |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | Content is presented as ER findings; footer disclaimer is template text. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | |
| 2.6 | The QRS never addresses the reader directly — it presents evidence, not guidance | 🟢 | No second-person address found. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms (MELAS, CYP2E1 substrates, GABA-acting drugs, glycemic control) are ER labels carried verbatim. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | |
| 2.9 | 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. | 🟢 | |
| 2.10 | The target audience is willing to employ lifestyle and behavioral changes as well as follow protocols that may be inconvenient, costly, or require effort. | 🟢 | |
| 2.11 | 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. | 🟢 | |
| 2.12 | 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. | 🟢 | Lede and tiers separate human-trial signals from animal-only longevity findings, matching the ER framing for this audience. |
| 2.13 | 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 “anti-aging” wording. |
| 2.14 | 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 or consumer-grade terms in the document’s own voice. |
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 column headers unchanged (lines 446, 483, 525, 545, 555, 589, 608-615, 716). |
| 3.2 | Every element carrying a data-qrs-var attribute in [qrs_template] is present in the QRS with the same name | 🟢 | Diff against template shows every data-qrs-var element present; marker_# and qualitative_item_# expanded per 14.2/15.2. |
| 3.3 | Everything outside the data-qrs-var spans — markup, text, styles, comments — is as in the template; spans that no checklist item addresses are left unchanged as well | 🟢 | Diff against template shows changes only inside data-qrs-var spans and in the metadata block values. |
4. Formatting
| # | Description | Result | Comments |
|---|---|---|---|
| 4.1 | An empty ER section never produces visible empty-state text in the QRS: the corresponding region is hidden or left empty. Phrases such as “None documented in human trials to date” or “Not formally studied” appear only where the ER uses them for a fact the QRS carries over. | 🟢 | Empty High/Medium risk tiers hidden with display:none and left empty (lines 591-596); no empty-state text. |
| 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 (“Heart and metabolic dose”, “Single versus split dosing”, “Exercise dose”) and qualitative labels match ER bold labels. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Labels match ER wording; parenthetical glosses dropped and example lists trimmed with at least one ER example kept. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji indicators. |
| 4.5 | The QRS is designed to render on one A4 page. It fails this item only for one of four things: a trailing clause after a dash, an optional gloss, an example list left untrimmed, or a repetition. Nothing else is cut to fit. | 🟢 | No trailing dash clauses, optional glosses, untrimmed example lists or repetitions found. |
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 directly follows <!doctype html> (line 2). |
| 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 — on lines 3 and 13. |
| 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. | 🟢 | |
| 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. | 🟢 | Values trimmed; only duration quoted (contains colon). |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | er_filename: taurine_2026-1101-0525_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.10.25 matches QRS.md version. |
| 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-1101-0900 |
| 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 the full name without the version number, with all remaining words joined by hyphens (e.g., Opus, Sonnet, Grok, Gemini-Flash, GPT); when the full name has no version number or is “Unknown”, the nickname equals the full name | 🟢 | |
| 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 |
| 5.11 | The full name of the AI consists of the model name (the word or words directly before the version number, leaving out the first if there is more than one, e.g., Claude Opus 5.5 → Opus 5.5), the model version number and the variant (if any) as stated in the system prompt or developer instructions of the creating model, with every word capitalized and without product, effort or pricing names (e.g., Opus X.Y, Sonnet X.Y, Grok X.Y, Gemini X.Y Flash, GPT X.Y), the model name alone when the system prompt or developer instructions name a model without a version number (e.g., Grok), or “Unknown” when neither the system prompt nor the developer instructions of the creating model name a model | 🟢 | |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | qrs_filename: taurine_2026-1101-0525_Opus_QRS.html |
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 &) |
🟢 | “Taurine for Health & Longevity - Quick Reference Sheet” (line 21). |
| 6.2 | [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &) |
🟢 | Line 423. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | 11/01/2026 (line 427). |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Opus 5.5 (line 431). |
| 6.5 | No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. | 🟢 |
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 with “Taurine, an amino acid supplement, is studied for heart, exercise and longevity benefits.” |
| 7.2 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Condenses all main points of the ER Conclusion. |
| 7.3 | [at_a_glance] is no longer than 70 words | 🟢 | 70 words (counted with wc -w). |
| 7.4 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Each fact maps to a Conclusion passage (paragraphs 1-3). |
| 7.5 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms or specialist classifications in the lede. |
| 7.6 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | |
| 7.7 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All three ER “Populations who should avoid Taurine” entries present (lines 548-550). |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | |
| 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. | 🟢 | No rationale, citations or trailing clauses. |
| 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). | 🟢 | Qualifiers “advanced … or on dialysis” and “(energy-drink form only)” preserved. |
| 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 uses no ranking notation in the contraindication bullets. |
| 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. |
🟢 | Section is populated; the ER names populations to avoid. |
| 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 empty. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | |
| 9.2 | [caution_items] represent the ER’s documented interactions — the items under its “Documented interactions:” label — excluding any that are already listed as Contraindications and any entry phrased as no interaction found | 🟢 | Edaravone, caffeine, aspirin/indomethacin listed; beta-alanine (“no interaction found”) correctly excluded. |
| 9.3 | [caution_theoretical_items] represent the ER’s theoretical interactions — the items under its “Theoretical interactions (inferred from mechanism, not studied in humans):” label | 🟢 | All nine ER theoretical interactions listed (lines 570-578). |
| 9.4 | The ER placeholder “None identified” is never an item: it means that group is empty | 🟢 | |
| 9.5 | Individual [caution_items] and [caution_theoretical_items] are formatted as <li></li>. The template’s bold “Theoretical (inferred from mechanism)” sub-heading is the only marker of the second list’s status: no item carries “(theoretical)”, “inferred from” or a mechanism clause | 🟢 | Items are <li>; none carries “(theoretical)” or a mechanism clause. |
| 9.6 | 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. | 🟢 | |
| 9.7 | 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 kept, trimmed, with ER’s own examples. |
| 9.8 | 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 uses no ranking notation in the interaction bullets. |
| 9.9 | If the ER’s theoretical group is empty, the whole Theoretical block — the caution_theoretical span with its sub-heading and list — is hidden with style="display:none", not removed: its spans stay in place, empty. |
N/A | ER’s theoretical group is not empty. |
| 9.10 | 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. |
🟢 | Section is populated; the ER names interactions. |
| 9.11 | 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, and the Theoretical block is hidden per 9.9. E.g. | N/A | Section is not empty. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Therapeutic Protocol section |
🟢 | |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from that section | 🟢 | Heart and metabolic dose, split dosing and exercise dose are the core actionable aspects of the ER Therapeutic Protocol. |
| 10.3 | If fewer than three distinct actionable implementation aspects are mentioned in the ER, the unused sets are left empty and hidden with style="display:none", not filled with placeholder text or empty-state phrasing. |
N/A | ER provides at least three actionable aspects. |
| 10.4 | All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from that 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 | 🟢 | Blood pressure, glucose and lipids, and endurance exercise from ER Practical Considerations “Time to effect”. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered as the High-tier benefits are ordered in the ER (blood pressure, glycemic control, endurance). |
| 11.3 | If fewer than three distinct time-to-effect aspects are mentioned in the ER, the unused sets are left empty and hidden with style="display:none", not filled with placeholder text or empty-state phrasing. |
N/A | ER provides three time-to-effect aspects. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | |
| 11.5 | If the ER provides no information on time to effect at all, the whole Time to effect block (its subhead and all three sets) is hidden with style="display:none", not removed: its spans stay in place, empty. |
N/A | ER provides time-to-effect information. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | |
| 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. | 🟢 | Items are ER benefit headings without qualifiers or effect sizes. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical content. |
| 12.5 | If a tier (high, medium, low, speculative) has no items, its span is hidden with style="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. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | |
| 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. | 🟢 | Items are ER risk headings without frequencies or qualifiers. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical content. |
| 13.5 | If a tier (high, medium, low, speculative) has no items, its span is hidden with style="display:none", not filled with “None documented in human trials to date” or similar empty-state phrasing. |
🟢 | Empty High and Medium tiers hidden with display:none (lines 591, 594). |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring Protocol & Defining Success section |
🟢 | |
| 14.2 | All measurable/quantifiable biomarkers from that section are listed, one table row per marker; the template’s # row is the pattern, repeated with # replaced by 1, 2, 3 … in the data-qrs-var names |
🟢 | All eight ER table biomarkers listed as marker_1 to marker_8. |
| 14.3 | [marker_#name] is the marker, [marker#target] its target value or range as given in the ER, [marker#_why] its purpose in a few words; a target the ER does not give is written “Not specified in the ER” | 🟢 | Targets match the ER Optimal Functional Range column; plasma taurine keeps the ER’s “No established target” wording. |
| 14.4 | [monitoring_cadence] is populated with the monitoring cadence/frequency derived from that section. It is not left with placeholder text or empty. | 🟢 | Cadence populated from ER monitoring paragraphs (line 710). |
| 14.5 | If the ER names no measurable biomarker, the table is hidden with style="display:none" and the single # row is left as in the template |
N/A | ER names measurable biomarkers. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring Protocol & Defining Success section |
🟢 | |
| 15.2 | All subjective/qualitative markers from that section are listed, one <li> per marker; the template’s # item is the pattern, repeated with # replaced by 1, 2, 3 … |
🟢 | All five ER qualitative markers listed as qualitative_item_1 to qualitative_item_5. |
| 15.3 | If the ER names no qualitative marker, the card’s list is hidden with style="display:none" and the single # item is left as in the template |
N/A | ER names qualitative markers. |
Issues 11/01/2026 09:23
Pass rate 100.00%. No issues found.
Issues 11/01/2026 09:18
- 1.2 / 1.3 — Safety dose qualifier dropped: The lede at line 439 says “Months-long trials show side effects no more common than placebo”, omitting the ER Conclusion’s “at commonly studied amounts” (ER line 447) and so widening a dose-bounded safety statement.
Fixes 11/01/2026 09:18
- 1.2 / 1.3 — Safety dose qualifier dropped: Added the ER’s “at commonly studied amounts” to the lede’s safety sentence (“Months-long trials at commonly studied amounts show side effects no more common than placebo”); to stay within 70 words, the opening use list became “heart, exercise and longevity benefits” and “thinking and memory benefits” became “thinking benefits”.
Issues 11/01/2026 09:14
- 7.2 — Lede omits safety uncertainties: The at_a_glance text (line 439) carries only the reassuring half of the ER Conclusion’s safety paragraph (“side effects no more common than placebo”) and drops its stated uncertainties: added lowering of blood pressure or blood sugar alongside medicines, unclear safety in advanced kidney disease, and the animal blood-cancer finding.
Fixes 11/01/2026 09:14
- 7.2 — Lede omits safety uncertainties: Rewrote at_a_glance (still 70 words) to keep the ER Conclusion’s safety caveat alongside the placebo-level side-effect finding, adding “safety with medicines or advanced kidney disease is unclear” and tightening other wording to fit.
Issues 11/01/2026 09:10
- 1.2 / 1.3 — Lede hedge strengthened: The At-A-Glance at line 439 says the most consistent human evidence “shows” small blood pressure and blood sugar improvements, where the ER Conclusion says it “points to” them.
Fixes 11/01/2026 09:10
- 1.2 / 1.3 — Lede hedge restored: Changed “evidence shows small blood pressure and blood sugar improvements” to “evidence points to …” in the At-A-Glance, matching the ER Conclusion; dropped a redundant “with” (“than with placebo” → “than placebo”) to keep the lede at 70 words.
Issues 11/01/2026 09:07
- 4.5 — Time-to-effect subs repeat values: Each Time to effect sub restates its value (lines 492/495 “within 8 weeks”, 503/506 “8 weeks or more”, 514/517 “about 1 hour”), and action_2_sub at line 467 repeats “divided doses” from action_2_value at line 464.
Fixes 11/01/2026 09:07
- 4.5 — Time-to-effect subs repeat values: Rewrote time_1_sub to “Greatest change in pooled trials”, time_2_sub to “Greater improvement in pooled trials” and time_3_sub to “After a single dose”; changed action_2_sub to “For daily use, given the short plasma half-life (about 1–2 hours)” so it no longer repeats “divided doses”.
Issues 11/01/2026 09:02
- 1.3 — Safety qualifier dropped: The At-A-Glance at line 439 states side effects were “no more common than with placebo in months-long trials” without the ER Conclusion’s “at commonly studied amounts”, broadening the safety claim (the ER lists stomatitis in 20% or more at 9–12 g daily).
Fixes 11/01/2026 09:02
- 1.3 — Safety qualifier dropped: Added “at commonly studied amounts” to the At-A-Glance safety statement; to stay within 70 words, dropped “inexpensive” and shortened the last sentence to “Longer life is shown only in animals.”