Audit: QRS - Inulin-Type Fructans for Health & Longevity

Audit conducted on 15/08/2026 21:42 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 93
Passed 81
Failed 0
N/A 12
Pass Rate 100.00%
  • Total = Passed + Failed + N/A
  • Pass Rate = Passed / (Passed + Failed) × 100
  • N/A items are excluded from the pass rate calculation

1. General Rules

# Description Result Comments
1.1 Every claim, magnitude, label, recommendation, and statement in the QRS is literally supported by content in the source ER. 🟢 Protocol cells trace to ER lines 348/358/362; time-to-effect to ER 405/381/350; benefits and risks to the ER tier headings; monitoring rows and cadence to ER 433–447; qualitative items verbatim from ER 451–455.
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. 🟢 No mapped ER section carries empty-state or hedged placeholder phrasing; cautious ER scoping (“in prediabetes and type 2 diabetes”, “normal or sluggish bowels”) is carried through.
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 and interaction severities (“Caution”, “Monitor”) match the ER verbatim; benefit and risk scope qualifiers that remain are the ER’s own.
1.4 The QRS does not relabel an ER fact under a different decision category. A “Benefit-Modifying Factor” from ER section is not surfaced as a “Caution”; a “Risk-Modifying Factor” is not surfaced as a “Side Effect”; etc. 🟢 Contraindications come only from the ER “Populations who should avoid” list; Key Interactions 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. 🟢 The QRS contains no PMIDs, citations, expert names, NCT identifiers, or brand names at all.
1.6 The QRS does not introduce new attributions. 🟢 No attributions of any kind 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, non-promotional register matching the ER; British spellings (“favourably”, “Tumour”, “hydrolysed”) carried through from the ER.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Quantified doses, windows, and biomarker targets sit alongside plain-language framing in At-A-Glance.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Content is stated descriptively (“Protocols place the dose with the largest meal” rendered as “With the largest meal”), never as an instruction to a patient.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No imperative or prescriptive constructions; the only clinician reference is the fixed template disclaimer in the footer.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No occurrence of “recommend”, “advise”, or “should” anywhere in the document body.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns (“you”, “your”) occur anywhere in the file.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical terms retained are load-bearing decision qualifiers or ER biomarker names (Rome IV, Child-Pugh, HbA1c); “low-density lipoprotein cholesterol” and “C-reactive protein” are spelled out in the Benefits card.
2.8 Information is presented in a concise and very compact manner 🟢 Tier lines are semicolon-separated fragments; gate items are stripped to the key fact plus qualifier.
2.9 It DOES NOT address the reader directly 🟢 Confirmed: no direct address anywhere in the document.
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 targets, titration-relevant dosing detail, and explicit decision gates address an optimizing reader.
2.11 The target audience is willing to employ lifestyle and behavioral changes as well as follow protocols that may be inconvenient, costly, or require effort. 🟢 Split dosing above 5 g, daily stool-form self-recording, and a nine-marker panel all assume effort tolerance.
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 consumer framing; functional ranges rather than conventional reference ranges are used throughout.
2.13 Framing, takeaways, and risk/benefit weighting throughout the document reflect this audience, including where an intervention’s signal for the average person differs from its signal for this audience. 🟢 At-A-Glance states the effect is confined to those already impaired (“hardly at all in others”), and the Benefits tiering preserves the ER’s small-effect weighting.
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. 🟢 The string “anti-aging” does not occur; the title uses “for Health & Longevity”.
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 terms used throughout (“flatulence”, “osmotic diarrhea”, “distension”, “bone resorption markers”); the plain word “gas” appears only in the At-A-Glance summary, where item 7.4 mandates plain language, and mirrors the ER Conclusion.

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 present unmodified: lines 446, 491, 539, 644, 672, 819 (headings), 572 and 593 (gates), 676–678 (table headers); tier labels appear in both the Benefits and Risks cards.
3.2 All “” from the [qrs_template] are present in the the QRS. 🟢 66 named variable spans present, covering page_title, header, at_a_glance, action_1–3, time_1–3, benefits_, stop_items, caution_items, risks_, marker_1–9, monitoring_cadence, and qualitative_item_1–5.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 The three non-variable spans — website=”evidence_review” (line 423), website=”audit” (426), website=”full_review” (440) — are untouched.

4. Formatting

# Description Result Comments
4.1 When the source ER section is empty, the QRS uses the ER’s own empty-state phrasing verbatim. Typical phrasings are “None documented in human trials to date” and “Not formally studied” N/A No ER section mapped into the QRS is empty; every source section (Protocol, Expected Benefits, Potential Risks & Side Effects, Key Interactions & Contraindications, Monitoring) is populated.
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. 🟢 All ten Key Interaction labels reproduce the ER bold labels verbatim including parenthetical drug lists and the Bifidobacterium / Lactobacillus italics; action labels “Standard dose”, “Best time of day”, “Single versus split dosing” match ER 348/358/362.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 No label deviates from the ER wording; the Time-to-Effect labels are taken from the ER’s own phrases in Practical Considerations (line 405).
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji characters occur anywhere in the file; the ER’s 🟩/🟥/🟨 tier markers were dropped and tiering is carried by bold labels plus CSS colour.
4.5 The QRS is designed to render on one A4 page. Any section that has more content in the ER than fits the per-section budget is condensed by the LLM, not extended onto a second page. 🟢 Every section is condensed to its minimum consistent with the mandatory-coverage items (9.2, 12.2, 13.2, 14.2, 15.2): gate items reduced to fact-plus-qualifier, tier lines to bare descriptors, and the A4 print rules and small-screen fallbacks in the stylesheet are intact.

5. Metadata

# Description Result Comments
5.1 The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content. 🟢 Lines 2–14: a single comment opening immediately after the doctype on line 1, before the template comment on line 16.
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 “—” at line 3, closing “—” at line 13; the preceding “QRS — Metadata” caption 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; none of its values are echoed into any rendered element.
5.4 All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. 🟢 Only duration: "00:03" is quoted, correctly, because it 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: inulin_type_fructans_2026-0825-1843_Opus_ER.md, matching the ER’s own filename frontmatter field.
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-0815-2132, correct 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: inulin_type_fructans_2026-0825-1843_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 eleven keys; no stray whitespace and no 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., &amp; for &) 🟢 Line 22: “Inulin-Type Fructans for Health & Longevity - Quick Reference Sheet”, matching 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., &amp; for &) 🟢 Line 417: “Inulin-Type Fructans for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 Line 421: “08/15/2026”, the correct reformatting of qrs_creation_date 2026-0815-2132.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Line 425: “Opus 5”, matching the frontmatter value.
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 alternate_names list (Inulin, Oligofructose, FOS, …) is correctly absent.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Five clauses map one-to-one onto the four Conclusion paragraphs (ER 477–481), ending on the intake-limiting constraint.
7.2 [at_a_glance] is no longer than 60 words 🟢 58 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Sentence 1 → ER 477; sentence 2 → ER 477; sentence 3 → ER 479; sentence 4 → ER 479; sentence 5 → ER 481.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms; the vocabulary is entirely lay (“plant fibers”, “gut bacteria”, “stool frequency”, “sluggish bowels”, “blood sugar”, “waistline”, “gas”).
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial name, year, sample size, or p-value appears.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 Magnitude is conveyed qualitatively (“modestly”, “favourably but slightly”); no numeric estimates or confidence intervals.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All five items come from the “Populations who should avoid Inulin-Type Fructans” list at ER 320–326.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All five ER avoid-list entries are present, in ER order, with none added or dropped.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Lines 575–588: 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. 🟢 Every ER trailing clause is stripped: “— absolute contraindication; fructose liberated…”, “— absolute contraindication”, “— defer until remission”, “— avoid pending human data…”, “— avoid unless a supervised reintroduction…”.
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). 🟢 “(Crohn’s Disease Activity Index above 220, or Mayo score 7 or higher in ulcerative colitis)” and “(Child-Pugh Class B or C, or persistently elevated conjugated bilirubin)” are preserved verbatim, as is “by Rome IV criteria”.
8.6 When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol. N/A The ER uses no ranking symbols in these parentheticals; thresholds are already written out in words (“above 220”, “7 or higher”, “Class B or C”).
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 The section is not empty — the ER names five avoid populations and all five are carried.
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, so no absence comment is required.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All ten items come from the interaction bullets at ER 300–318.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All ten ER interaction bullets are present in ER order; none duplicates a contraindication.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Lines 596–634: ten <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. 🟢 Each item is reduced to the ER’s bold label plus its severity word (“Caution” / “Monitor”); all mechanistic and mitigation sentences are dropped. The only em-dash retained sits inside the ER’s own bold label (“Other fermentable fibers — galactooligosaccharides, resistant starch, partially hydrolysed guar gum”), which items 4.2 and 9.5 require to be kept.
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). 🟢 “(omeprazole, esomeprazole)”, “(amoxicillin, azithromycin, ciprofloxacin)”, and the prescription / over-the-counter / supplement / other-intervention class markers are all preserved.
9.6 When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol. N/A The ER’s interaction parentheticals contain only class markers and example drug names — no ranking notation.
9.7 The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no interaction, additive effect, or exposure that changes how the intervention is used. N/A The section is not empty — ten interactions are identified and all ten are carried.
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, so no absence comment is required.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 All three action sets come from the ER “Therapeutic Protocol” bullets at lines 348, 358, and 362.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Dose (“Standard dose”), timing (“Best time of day”), and dose splitting (“Single versus split dosing”) are the three directly executable bullets; the remaining ER bullets are competing approaches, kinetics, or response-modifier discussion.
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 Protocol section 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 spans (lines 450–486) carry substantive ER-derived content; none is empty or a placeholder.

11. Time to Effect

# Description Result Comments
11.1 The three sets of [time] items cover the three most important time-to-effect aspects from the ER 🟢 Bifidobacterial shift, bowel-frequency change, and glycemic improvement are the first three of the four windows the ER lists at line 405; the fourth (body composition) is folded into time_3_sub.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Order follows the ER benefit tiering: bifidobacterial expansion and bowel regularity are High-tier benefits, glycemic control is Medium-tier.
11.3 If less that three distinct time-to-effect aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing. N/A The ER lists four distinct time-to-effect aspects, so no set is unused.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 Values 1–2 weeks / 2–4 weeks / 6 weeks or more come from ER 405; the subs come from ER 381 (reversal), ER 240 and 405 (gas attenuation), and ER 350 and 405 (10 g dose, body composition window).
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 an explicit “Time to effect” bullet (line 405), so the section is correctly retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All nine descriptors map to the ER benefit sub-headings at lines 152–216.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present at lines 541, 546, 554, 560, each tier 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. 🟢 Each entry is the bare ER heading with hedging qualifiers removed (“Modest Reduction…” → “reduction in body weight…”; “Small Reductions…” → “reductions in…”); no Magnitude figures, PMIDs, or mechanism text carried over.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses appear in any of the four benefit spans; the ER’s “⚠️ Conflicted” markers and Magnitude lines are all dropped.
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 ER benefit tiers contain items, so no span needs hiding.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All seven descriptors map to the ER risk sub-headings at lines 238–278.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present at lines 646, 649, 655, 661, each tier 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 entry is the bare ER heading; the fermentation, FODMAP, IgE, and rodent-model explanations are all omitted.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses appear in any of the four risk spans; the ER “⚠️ Conflicted” markers and Magnitude lines are dropped.
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 ER risk tiers contain items, so no span needs hiding.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Rows and cadence come from the ER “Monitoring Protocol & Defining Success” section at lines 433–447.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All nine ER biomarker rows are present in ER order — fasting glucose, HbA1c, fasting insulin, triglycerides, LDL-C and ApoB, hs-CRP, red blood cell magnesium, 25-hydroxyvitamin D, Bristol Stool Form Scale type — with targets and “Why” text matching the ER.
14.3 [monitoring_cadence] is populated with the monitoring cadence/frequency derived from the ER Monitoring section. It is not left with placeholder text or empty. 🟢 Lines 808–813 carry baseline, 12-week, 6–12-month, annual mineral/vitamin D, and 4-week stool-form cadences, all traceable to ER 433–435 and 447.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 All five items come from the “Qualitative markers worth tracking alongside laboratory values” list at ER 449–455.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All five ER qualitative markers are present verbatim and in ER order at lines 822–848.

Issues 15/08/2026 21:42

Pass rate 100.00%. No issues found.

Issues 15/08/2026 21:39

  1. 2.5 — Imperative protocol cell value: [action_3_value] at line 480 reads “Split above 5 g”, an imperative instruction rather than presented information, breaking parallel with the descriptive cells “5–10 g daily” and “With the largest meal”.

Fixes 15/08/2026 21:39

  1. 2.5 — Imperative protocol cell value: Changed [action_3_value] from “Split above 5 g” to “Two doses above 5 g”, replacing the imperative instruction with a descriptive noun phrase that matches the ER’s “above 5 g, splitting into two doses”.