Audit: QRS - Glucoraphanin for Health & Longevity

Audit conducted on 11/09/2026 19:11 using AI4L + evidence-mcp / Opus 5.5

Iterations

Summary

Items Count
Total 97
Passed 87
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. 🟢 Lede, Protocol, Time to effect, gates, tiers and markers each trace to ER text (e.g., action_1 to Therapeutic Protocol “Glucoraphanin-only capsules”; time cells to Practical Considerations “Time to effect”).
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. 🟢 Gate and protocol hedges kept: “possibly lower drug levels”, “possibly faster drug clearance”, “altered metabolism of uncertain direction”, “possibly reduced treatment efficacy”; lede keeps “suggest”, “appear mild”, “remain unmeasured”.
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; lede “A few studies backed by one food company suggest small improvements” mirrors the ER Conclusion; contraindications keep the ER’s “should avoid” scope and qualifiers.
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 and risk items come from Expected Benefits / Potential Risks; modifying factors are not surfaced as cautions or side effects.
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 (Kagome, Avmacol, BroccoMax) 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-qualified tone matches the ER Conclusion.
2.2 The tone of the QRS is expert, accessible, objective, and data-driven 🟢 Expert, objective and data-anchored (doses, durations, reference ranges).
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Presents findings and trial doses, not orders.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No advice language; footer disclaimer unchanged.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Protocol cells describe trial and common-practice dosing; no “recommend”/”advise”.
2.6 The QRS never addresses the reader directly — it presents evidence, not guidance 🟢 No second-person address anywhere.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical terms are ER labels carried verbatim (CYP1A2 substrates, UGT1A1 substrates, Proton pump inhibitors) or marker names; lede glosses sulforaphane as “its active form”.
2.8 Information is presented in a concise and very compact manner 🟢 Cells and list items are short and compact.
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. 🟢 Content addresses proactive, risk-aware adults (dosing forms, monitoring panel, drug-level checks).
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. 🟢 Includes effortful elements: lab panel cadence, drug-level checks, product-form choice.
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. 🟢 Not dumbed down for the general population; retains protocol and monitoring detail.
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. 🟢 Framing follows the ER: modest, sponsor-dependent signals in Medium; indirect benefits in Low; long-term effects unmeasured.
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. 🟢 Formal terms used (“capsules”, “tablets”, “dietary supplement”, “gastrointestinal”); no lay route-of-administration phrasing.

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 (lines 446, 483, 525, 545, 556, 588, 607, 611-613, 715).
3.2 Every element carrying a data-qrs-var attribute in [qrs_template] is present in the QRS with the same name 🟢 All template data-qrs-var names present; marker_# and qualitative_item_# expanded to numbered names 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 the template shows changes only inside data-qrs-var spans, display:none on empty tier spans, and the metadata block; website spans unchanged.

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 tiers (benefits_high, risks_high, risks_medium) hidden; no empty-state phrases visible. “Not specified in the ER” used only as required by 14.3.
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 “Glucoraphanin-only capsules”, “Glucoraphanin plus myrosinase”, “Time of day” and interaction labels use the ER bold labels verbatim (example lists trimmed).
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Labels are the ER’s own words; parenthetical example lists trimmed with at least one 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 in the QRS.
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, untrimmed interaction example lists, optional glosses in labels, 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 at line 2, directly after doctype.
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.
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. 🟢 Inside an HTML comment; not surfaced elsewhere.
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 “00:02” is quoted, which contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: glucoraphanin_2026-1109-1433_Opus_ER.md (line 4).
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.11.8 matches 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) 🟢 qrs_creation_date: 2026-1109-1858 in YYYY-MMDD-HHMM.
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 (line 7).
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 🟢 “Opus” is “Opus 5.5” without 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 (line 8).
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 🟢 “Opus 5.5” follows the name + version format.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename matches the file name.

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 &) 🟢 Title “Glucoraphanin 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., &amp; for &) 🟢 header_topic “Glucoraphanin for Health & Longevity” (line 423).
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 11/09/2026 matches 2026-1109-1858.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Opus 5.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. 🟢 No extra header content.

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 “Glucoraphanin, a natural broccoli compound sold as a dietary supplement to switch on the body’s own protective enzymes” before any evidence verdict.
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Condenses the Conclusion: conversion variability, sponsor-backed liver and processing-speed signals, mild side effects, unmeasured long-term effects.
7.3 [at_a_glance] is no longer than 70 words 🟢 70 words (script count).
7.4 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each fact maps to ER Motivation, Practical Considerations (regulatory status) or Conclusion passages.
7.5 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms; “sulforaphane” is glossed as “its active form”.
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.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 From ER “Populations who should avoid Glucoraphanin” in Key Interactions & Contraindications.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All four ER populations listed (lines 548-551).
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Each item is an li element.
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. 🟢 Inferred-from rationales and glosses stripped; no trailing dash content.
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). 🟢 Applicability qualifiers kept (“for products containing mustard-seed myrosinase”, “at supplement doses”, “unless their oncology team agrees”, “untreated … and iodine deficiency”).
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 contraindications.
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 populated; ER names four populations.
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. <!-- empty: ER names no population that should avoid the intervention --> 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 🟢 From ER Key Interactions & Contraindications.
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 🟢 Six documented interactions listed; CYP3A4 (“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 four ER theoretical interactions listed (lines 574-577).
9.4 The ER placeholder “None identified” is never an item: it means that group is empty 🟢 No “None identified” item.
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 🟢 li elements; no “(theoretical)”, “inferred from” or mechanism clause in items.
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. 🟢 Consequences condensed; mitigation clauses and citations stripped; no dash clauses.
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 trimmed but kept (e.g., “(omeprazole)”, “(caffeine, clozapine)”, “(metformin, insulin)”).
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 interactions.
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 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 populated; ER identifies 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. <!-- empty: ER names no interaction that changes how the intervention is used --> N/A Section is not empty.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Therapeutic Protocol section 🟢 Derived from ER Therapeutic Protocol.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from that section 🟢 Covers glucoraphanin-only dosing, myrosinase co-formulation, and time of day / once-daily dosing.
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 names more than three actionable aspects.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from that section. 🟢 All nine action spans hold meaningful ER-derived content.

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 ER time-to-effect aspects (Practical Considerations).
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Medium-tier liver enzymes and processing speed precede the Speculative pollutant-excretion item.
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 gives 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. 🟢 All time spans filled with ER-derived content.
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 🟢 Derived from ER Expected Benefits.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four tier variables present; High hidden.
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 reduced to ER 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 in benefit items.
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. 🟢 benefits_high hidden with style=”display:none” (line 527).

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Derived from ER Potential Risks & Side Effects.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four tier variables present; High and Medium hidden.
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 headings only.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content in risk items.
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. 🟢 risks_high and risks_medium hidden with style=”display:none” (lines 590, 593).

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring Protocol & Defining Success section 🟢 Derived from ER Monitoring Protocol & Defining Success.
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 🟢 Eight rows: the five table markers plus HbA1c, free thyroxine and drug level named in that section; numbered 1-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 table; HbA1c, free thyroxine and drug level have no ER target and read “Not specified in the ER”.
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: baseline, 12 weeks, 24 weeks, every 6-12 months; TSH at 3 months in at-risk users.
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 🟢 Derived from ER Monitoring Protocol & Defining Success.
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 four ER qualitative markers listed, numbered 1-4.
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/09/2026 19:11

Pass rate 100.00%. No issues found.

Issues 11/09/2026 19:06

  1. 4.5 — Optional gloss in label: The PPI interaction label at line 559 keeps the optional gloss “acid-reducing drugs such as” inside the bold label (“Proton pump inhibitors (acid-reducing drugs such as omeprazole)”), which should be trimmed to the example drug.

Fixes 11/09/2026 19:06

  1. 4.5 — Optional gloss removed: Trimmed the PPI interaction label from “Proton pump inhibitors (acid-reducing drugs such as omeprazole)” to “Proton pump inhibitors (omeprazole)”.

Issues 11/09/2026 19:03

  1. 1.1 — LDL target overgeneralized: marker_3_target at line 644 reads “No established target; change from own baseline”, while the ER says “No established target for glucoraphanin use; track change from own baseline”.
  2. 2.7 — Unnecessary technical jargon: time_3_sub at line 517 uses “conjugates” and marker_8_why at line 702 uses “enzyme induction”, where the ER offers plainer wording (“detoxification products”, “faster drug clearance”).
  3. 4.5 — Dose repetition in Time to effect: time_1_sub (line 495, “60 mg/day …”) and time_2_sub (line 506, “30 mg/day …”) repeat the doses already given in action_1_sub at line 456.

Fixes 11/09/2026 19:03

  1. 1.1 — LDL target restored: Changed marker_3_target from “No established target; change from own baseline” to “No established target for glucoraphanin use; change from own baseline”, matching the ER.
  2. 2.7 — Jargon replaced: Changed time_3_sub to “Urinary detoxification products of benzene and acrolein” and marker_8_why to “Detects under-dosing from faster drug clearance”, using ER wording.
  3. 4.5 — Dose repetition removed: Removed the repeated doses from time_1_sub (“In adults with high-normal ALT”) and time_2_sub (“In healthy older adults”).

Issues 11/09/2026 19:00

  1. 4.5 — Time-to-effect subs repeat values: In Time to effect (lines 492-517) each sub restates its value: “24 weeks” / “Liver-enzyme differences measured at 24 weeks”, “12 weeks” / “Processing-speed changes measured at 12 weeks”, “Rapid” / “Pollutant-excretion changes appeared rapidly”.

Fixes 11/09/2026 19:00

  1. 4.5 — Time-to-effect subs repeat values: Replaced the three repeating subs with ER context that does not restate the value: “60 mg/day in adults with high-normal ALT”, “30 mg/day in healthy older adults” and “Urinary benzene and acrolein conjugates”.