Audit: QRS - Naringenin for Health & Longevity
Audit conducted on 14/08/2026 09:14 using AI4L / Opus 5
Summary
| Items | Count |
|---|---|
| Total | 93 |
| Passed | 84 |
| Failed | 0 |
| N/A | 9 |
| Pass Rate | 100.00% |
- Total = Passed + Failed + N/A
- Pass Rate = Passed / (Passed + Failed) × 100
- N/A items are excluded from the pass rate calculation
1. General Rules
| # | Description | Result | Comments |
|---|---|---|---|
| 1.1 | Every claim, magnitude, label, recommendation, and statement in the QRS is literally supported by content in the source ER. | 🟢 | Every protocol cell, time-to-effect cell, gate item, tier item, biomarker row and qualitative item traces to a named ER passage; several are verbatim. |
| 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. | 🟢 | “a level no outcome trial has used”, “(conflicted)”, “the only controlled adult trial”, “No established target” 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”). | 🟢 | Contraindications remain contraindications; the conflicted insulin-sensitivity signal keeps its conflict marker in both the Benefits and Risks cards. |
| 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. | 🟢 | [stop_items] come only from “Populations who should avoid Naringenin”; [caution_items] only from the ER interaction bullets; no Benefit- or Risk-Modifying Factor is surfaced as a 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. | 🟢 | No PMIDs, author names, NCT identifiers or brand names appear anywhere in the QRS. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | The single attribution phrase, “Some longevity practitioners extrapolate to 300 mg twice daily”, is verbatim from the ER Protocol section. |
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, gap-naming register matches the ER throughout, including “the human record is thin” and “Everything beyond rests on animals, cells or worms”. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Thresholds, dose figures and biomarker targets are given plainly and without alarm, leaving the decision with the reader. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Protocol cells describe what the trial used rather than instructing; Monitoring states what is measured, not what must be done. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No imperatives; “Split dosing preferred” reproduces the ER’s own framing tied to the outcome trial. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | Cadence and monitoring text are stated as passive practice (“Baseline before starting; lipid and liver panels repeated at 8 weeks”), not as recommendations. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronoun occurs anywhere in the file. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Biomarkers are spelled out in full rather than abbreviated; At-A-Glance uses “cholesterol-carrying particles” and “fatty liver”. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Gate items are noun phrases; tier lines are semicolon-separated fragments; sub-cells run to at most two short sentences. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed by full-text scan: no “you”, “your”, “we” or “our”. |
| 2.10 | The target audience is health- and longevity-oriented adults who are risk-aware, proactive, and actively seeking to optimize health or apply the intervention under review. | 🟢 | Functional biomarker ranges, imaging-based liver fat and apolipoprotein B assume a proactive optimizer rather than a general 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. | 🟢 | Split twice-daily meal-timed dosing, imaging and concurrent drug-level checks all presuppose willingness to follow an inconvenient protocol. |
| 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 simplified or reassurance-oriented framing; the sheet leads with evidence limits and interaction risk. |
| 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. | 🟢 | The high-tier risk is the silent drug-absorption interference, which is the decisive consideration for a supplement-stacking audience, and it is placed first in the Risks card. |
| 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. | 🟢 | “anti-aging” does not occur; the sheet uses “longevity practitioners” and “brain aging”. |
| 2.15 | The document’s own voice uses formal clinical and scientific terminology, not colloquial or consumer-grade language (e.g., “oral medication” not “pill(s)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt. | 🟢 | Formal register throughout; “capsules” and “worms” in At-A-Glance are the ER’s own Conclusion wording. |
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 strings match the template byte-for-byte, including the template’s own unencoded “Risk & Side Effects” heading. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | Variable-name diff against the template returns no missing names; the extra names are the enumerated marker_# and qualitative_item_# repeats the template defines. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | A structural diff with text nodes stripped shows no change to CSS, layout, comments, footer disclaimer or the three website= spans. |
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; the only absent tier (High benefits) is handled under 12.5. |
| 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 dose”, “Best time of day” and “Single versus split dosing” are the ER Protocol bold labels verbatim; all eleven biomarker names match the ER table column verbatim. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Protocol, Monitoring and Qualitative labels are taken from the ER unchanged; the three time-to-effect labels are drawn from the ER’s own wording, which supplies no bold label for that row. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | A Unicode scan of the file returns no emoji; the ER’s “⚠️ Conflicted” marker is carried as plain text. |
| 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. | 🟢 | Condensation is applied per section — tier items collapsed to semicolon lists, gate items reduced to noun phrases, biomarker “Why” cells trimmed to a single clause — within the one-sheet template. |
5. Metadata
| # | Description | Result | Comments |
|---|---|---|---|
| 5.1 | The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content. | 🟢 | The comment opens on line 2, 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 and closing “—” on line 13, preceded only by the permitted “QRS — Metadata” caption. |
| 5.3 | The metadata is not visible in any rendered view of the QRS and is not surfaced by any other element on the sheet. | 🟢 | The block sits entirely inside the HTML comment; no metadata value is repeated in the header, footer or body. |
| 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” is quoted, and it must be because “00:03” contains a colon; all other values are bare and untrimmed of nothing. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Line 4: “er_filename: naringenin_2026-0814-0654_Opus_ER.md”, matching the ER’s own frontmatter filename. |
| 5.6 | Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” | 🟢 | Line 5: “qrs_prompt_version: 26.7.02”, matching the version badge at the top of QRS.md. |
| 5.7 | Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) | 🟢 | Line 6: “qrs_creation_date: 2026-0814-0858”, in the required format. |
| 5.8 | The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” | 🟢 | Line 7: “qrs_creator_ai_nickname: Opus”. |
| 5.9 | The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) | 🟢 | “Opus” is a single word with no version or qualifier. |
| 5.10 | The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” | 🟢 | Line 8: “qrs_creator_ai_fullname: Opus 5”. |
| 5.11 | The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier (e.g., Opus 4.6, Sonnet 3.2, Grok 4.5, Gemini 3.1, ChatGPT 5.4) | 🟢 | “Opus 5” is nickname plus version with no trailing qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9: “qrs_filename: naringenin_2026-0814-0654_Opus_QRS.html”, matching the file on disk. |
| 5.13 | All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. | 🟢 | Re-verified across all nine keys; git_user and git_issue are bare, duration is quoted only for its colon. |
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 &) |
🟢 | “Naringenin for Health & Longevity - Quick Reference Sheet” matches the ER canonical_topic with the ampersand encoded. |
| 6.2 | [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &) |
🟢 | “Naringenin for Health & Longevity”, encoded and with no suffix. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | “08/14/2026” is the correct MM/DD/YYYY rendering of qrs_creation_date 2026-0814-0858. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | “Opus 5”, identical to the frontmatter qrs_creator_ai_fullname. |
| 6.5 | No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. | 🟢 | The header holds only the title and the template subline; the ER’s “Also known as” list and creation attribution are 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 |
🟢 | Compresses all four Conclusion paragraphs — mechanism, thin human record, preclinical remainder, and the interaction concern that drives the decision. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 57 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Each of the five sentences maps to a separate Conclusion sentence, including “one small, short trial in overweight adults with fatty liver”. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms; “cholesterol-carrying particles”, “fatty liver” and “prescription drugs” are non-specialist terms. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | The single trial is referenced only as “one small, short trial”, with no name, year or sample size. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No numbers of any kind appear in the At-A-Glance text. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All six items come from that section’s “Populations who should avoid Naringenin” list. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All six ER avoid-populations are present, none added. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Six sibling <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. | 🟢 | Rationale clauses such as “on the basis of reduced litter size…” and “outside the single supervised pneumonia trial” are stripped; no dash-trailing clause remains. |
| 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). | 🟢 | “Child-Pugh Class B or C”, “creatinine above 1.4 mg/dL”, “below 30 mL/min/1.73 m²” and the narrow-therapeutic-index drug list are all retained. |
| 8.6 | When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol. | N/A | The ER uses no ranking notation inside parentheses in this section. |
| 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 six such populations and the section is correspondingly populated, not empty. |
| 8.8 | If the section is left empty, an HTML comment inside the [stop_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. | N/A | The section is not empty. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All nine items are the nine bold-labelled interaction bullets of that ER section, in ER order. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | No interaction bullet is duplicated as a contraindication; the ER itself keeps the drug-class interactions and the avoid-populations as separate lists. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Nine sibling <li> elements inside the [caution_items] span. |
| 9.4 | Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact. | 🟢 | Every “Severity — … consequence — …” tail is stripped; each item is reduced to the drug or supplement class alone. |
| 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). | 🟢 | All nine ER example-drug parentheticals are carried through intact, including the seven-drug CYP3A4 list. |
| 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 uses no ranking notation inside parentheses in this section. |
| 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 populated accordingly. |
| 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 restate ER Therapeutic Protocol bullets, largely verbatim. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Dose, timing and dosing frequency are the three executable levers; non-actionable bullets (attribution, genetics, sex, age) are correctly left out. |
| 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 more than three actionable aspects, so no set is unused. |
| 10.4 | All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. |
🟢 | All nine cells are populated; no placeholder token remains anywhere in the file. |
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 | 🟢 | Lipids/liver fat at four weeks, body mass and visceral fat at four weeks, and peak blood levels at 2.4–3.2 hours are the only timed observations in the ER. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | The two medium-tier benefits lead in ER order, with the pharmacokinetic timing 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 | Three distinct time-to-effect aspects exist, so all three sets are used. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | All nine cells are populated; the sub-cells reproduce ER wording from Practical Considerations and the medium-tier benefit entries. |
| 11.5 | If the ER does not provide any information on time to effect, the section is removed completely from the Protocol Panel |
N/A | The ER provides time-to-effect information, so the section is correctly retained. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | Every listed benefit is an ER Expected Benefits sub-heading at the matching tier. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans are present with their template tier labels intact. |
| 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. | 🟢 | Each tier is a semicolon-separated list of bare benefit names; the ER’s Magnitude paragraphs and mechanism sentences are dropped entirely. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No ER parenthetical is carried into the Benefits card; the sole parenthesis, “(conflicted)”, is the plain-text rendering of the ER’s own conflict marker required by 1.3 and 4.4. |
| 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. | 🟢 | The ER states that no benefit reaches High; [benefits_high] carries style=”display: none” and no empty-state text. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | All seven listed risks are ER sub-headings at the matching tier. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans are present and populated. |
| 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. | 🟢 | Each tier is a bare semicolon-separated list; the fexofenadine figures, the EFSA no-observed-adverse-effect level and all mechanism text are omitted. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No ER parenthetical survives; “(conflicted)” is the plain-text form of the ER’s conflict marker, retained to avoid softening the ER claim. |
| 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 risk tiers contain ER items, so no span needs hiding. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | The table and cadence come from Monitoring Protocol & Defining Success. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All eleven rows of the ER biomarker table appear, in ER order, with names, ranges and rationales carried across. |
| 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. |
🟢 | Baseline, 8 weeks, 6 months, 6–12 monthly, plus the 4-week concurrent drug level — all from the ER’s ongoing-monitoring paragraph. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Taken from the ER’s “Qualitative markers worth tracking alongside the laboratory panel” list. |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All four ER qualitative markers are present, verbatim and in ER order. |
Issues 14/08/2026 09:14
Pass rate 100.00%. No issues found.
Issues 14/08/2026 09:06
- 10.4 — Protocol subs pull from Risk Mitigation: [action_1_sub] (QRS line 458) carries the 600 mg daily cap and [action_2_sub] (QRS line 474) carries the four-hour drug-separation rule, both of which come from the ER
Risk Mitigation Strategiessection (ER lines 333, 343) rather than the ERProtocolsection that item 10.4 requires.
Fixes 14/08/2026 09:06
- 10.4 — Protocol subs pull from Risk Mitigation: Replaced the two sentences imported from the ER
Risk Mitigation Strategiessection with ERProtocolsection content — the 600 mg daily cap in [action_1_sub] became the higher exploratory 300 mg twice-daily extrapolation, and the four-hour drug-separation rule in [action_2_sub] became “splitting around meals matches the compound’s metabolic target”.