Audit: QRS - Andrographis for Health & Longevity

Audit conducted on 05/09/2026 02:51 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 93
Passed 83
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. 🟢 All protocol values, tier contents, gate items, biomarker targets and cadence text trace to Therapeutic Protocol, Expected Benefits, Potential Risks & Side Effects, Key Interactions & Contraindications and Monitoring Protocol & Defining Success.
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 ER empty-state or hedged phrasing is carried into the QRS in altered form.
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 absolute (“Pregnancy at any stage, and breastfeeding”); interactions remain interactions.
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. 🟢 Gates come only from Key Interactions & Contraindications; no modifying-factor content appears anywhere in the QRS.
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 carries no PMIDs, NCT IDs, author names or brand names; the drug names in the interaction gate are generic names taken verbatim from the ER bullets.
1.6 The QRS does not introduce new attributions. 🟢 No sponsor, manufacturer or investigator is named.

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. 🟢 Flat, declarative, evidence-first register matching the ER.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Numeric protocol and biomarker targets paired with plain-language framing.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Content is stated as observed practice and trial parameters, not orders.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No imperative verbs directed at a reader in any populated span.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Cadence span uses the ER’s own “warrants” framing rather than “should”.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns in any populated span.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Retained technical terms (Child-Pugh, UGT2B7, CYP substrates) are decision-gate qualifiers required by items 8.5 / 9.5.
2.8 Information is presented in a concise and very compact manner 🟢 Gate items and tier lines are reduced to key facts; no trailing rationale.
2.9 It DOES NOT address the reader directly 🟢 Confirmed across header, at-a-glance, protocol, gates, cards and cadence.
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 and label-quality warning are aimed at this audience.
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, baseline labs and symptom logging are presented without simplification.
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. 🟢 Nine-marker panel and qualitative tracking exceed general-population expectations.
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 leads with the narrow supported use and the product-quality problem.
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 in the QRS.
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. 🟢 “Gastrointestinal upset”, “hypersensitivity reactions”, “transient liver-enzyme elevation”; the plainer wording in at-a-glance is required by item 7.4 and is taken from 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 fixed strings match [qrs_template] exactly (lines 445, 491, 533, 564, 581, 604, 632, 636–638, 661).
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 page_title, header_topic, header_subline_date, header_subline_model, at_a_glance, action_1–3 (label/value/sub), time_1–3 (label/value/sub), benefits_, stop_items, caution_items, risks_, marker_#name/target/why, monitoring_cadence, qualitative_item# all present.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 The three non-variable spans website="evidence_review", website="audit" and website="full_review" are byte-identical to the template.

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.
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 acute respiratory dose”, “Standard inflammatory-condition dose”, “Single versus split dosing” are verbatim ER Therapeutic Protocol labels; monitoring row labels are verbatim ER biomarker names.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 No invented label; time-to-effect labels are the ER’s own outcome names (“Respiratory symptoms”, “Joint pain”, “Fatigue”).
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji characters anywhere in the file; tiering is conveyed by bold labels and card colours.
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 rather than transcribed: 11 interaction bullets trimmed to two example drugs each, four Medium benefits collapsed into one line, cadence paragraph reduced to three sentences.

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, immediately after <!doctype html> 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 --- line 3, closing --- line 13; the title text sits on line 2 before the opener.
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; no metadata value is echoed into the 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: "00:02" is quoted, correctly, because it contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 Line 4: er_filename: andrographis_2026-0905-0013_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]” 🟢 Line 5: qrs_prompt_version: 26.7.02, matching the QRS.md version badge.
5.7 Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) 🟢 Line 6: qrs_creation_date: 2026-0905-0223.
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” = nickname plus version, no qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 Line 9 matches the file on disk: andrographis_2026-0905-0013_Opus_QRS.html.
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; no stray whitespace or unnecessary quoting.

6. Page Title & Header

# Description Result Comments
6.1 [page_title] is set to the [canonical_topic] of the ER frontmatter followed by “ - Quick Reference Sheet” (e.g., “Intervention - Quick Reference Sheet”). The [canonical_topic] is HTML-entity-encoded as needed (e.g., &amp; for &) 🟢 Line 22: Andrographis for Health &amp; Longevity - Quick Reference Sheet.
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: Andrographis for Health &amp; Longevity, matching ER frontmatter canonical_topic.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 Line 421: 09/05/2026, the correct reformatting of 2026-0905.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Line 425: Opus 5.
6.5 No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. 🟢 Header holds only the title and the template’s fixed subline; the ER’s “Also known as” line was 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 🟢 Each clause maps to the ER Conclusion (lines 471–475): mechanism, the supported respiratory use, the thinning evidence, the tolerability limits and label quality.
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. 🟢 “quiets inflammatory signalling” (ER 471), “within the first day or two” (471), “the picture thins” (471), “Stomach upset and skin reactions… taste disturbance drives people to stop” (473), “retail products routinely below label” (475).
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronym appears; “stomach upset”, “skin reactions”, “below label” are lay terms.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial, author, year or sample size named.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No SMD, CI, p-value or percentage present.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Sourced from the “Populations who should avoid Andrographis” list, ER lines 320–328.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All seven ER populations are present, in ER order.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Seven <li> elements, lines 567–576.
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. 🟢 The ER’s rationale clauses (“rodent antifertility and abortifacient signals…”, “given the rodent testicular…”, “trials in children used fixed combinations…”) are all stripped; no em-dash remains in any item.
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 B or C, or transaminases above 3× the upper limit of normal” and “within 14 days of planned surgery” retained; only the lay gloss “(blocked bile flow)” was dropped.
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 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 seven such populations and the section is correspondingly populated.
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 🟢 Sourced from the eleven interaction bullets, ER lines 298–318.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All eleven ER interaction bullets map 1:1 to the eleven <li> items; none duplicates a contraindicated population.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Eleven <li> elements, lines 584–594.
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 “Caution./Monitor.” verdict, mechanism and mitigation sentence is stripped; the ER’s “Other interventions — “ prefix is removed from the vaccination/surgery item.
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). 🟢 Each item keeps a trimmed example-drug parenthesis (e.g. “(ciclosporin, tacrolimus)”, “(theophylline, statins)”); none is dropped entirely.
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 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 eleven interactions and the section is correspondingly populated.
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 trace to ER Therapeutic Protocol lines 348, 350, 360, 362.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Acute respiratory dose, inflammatory-condition dose and split-versus-single dosing are the three executable decisions; the remaining bullets are attribution, history or “none validated”.
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; all three sets are used.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 Nine populated spans, lines 449–486; values (“200 mg standardized extract daily”, “300–600 mg daily”, “Split”) and subs all match the ER text.

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 🟢 Respiratory symptoms, joint pain and fatigue, all from the ER “Time to effect” bullet (line 402).
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Respiratory (High tier) first, then joint pain and MS fatigue in the ER’s own Medium-tier order; the lower-ranked triglyceride timing is the one omitted.
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 names four time-to-effect aspects; all three sets are used.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 “Days 3–5 / Separation appears by day 3, clearest by day 5”, “28 days / Knee pain, stiffness and physical-function scores”, “Months / Multiple sclerosis fatigue scores at 12 months” all trace to ER lines 156, 170, 402.
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 retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Every entry corresponds to an ER Expected Benefits heading, ER lines 146–214.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present and populated, lines 535–557.
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. 🟢 Headings condensed to noun phrases (“triglyceride lowering”, “cholestatic liver protection”); no Magnitude: content carried across.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses appear in any benefits span.
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 tiers contain items, so no span needed hiding.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Every entry corresponds to an ER risk heading, ER lines 238–280.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present and populated, lines 606–626.
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. 🟢 Pooled incidence figures, the 4.04% ADR rate and the three attributed deaths 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 risks span.
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 tiers contain items, so no span needed hiding.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Rows mirror the ER biomarker table, ER lines 434–442.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All nine present with verbatim optimal ranges: ALT, AST, total bilirubin, hs-CRP, fasting triglycerides, CBC with differential, eGFR, fasting glucose, seated blood pressure.
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. 🟢 Line 755 condenses ER lines 428–430: baseline, no follow-up for a 5–7 day course, liver panel at 8–12 weeks then 6-monthly, lipids and inflammatory markers at 8–12 weeks then annually.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Sourced from the ER qualitative-marker list, ER lines 446–451.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All six present and in ER order: recovery days, morning stiffness, fatigue scale, taste, stool frequency and form, skin changes.

Issues 05/09/2026 02:51

Pass rate 100.00%. No issues found.

Issues 05/09/2026 02:45

  1. 1.3 / 7.3 — Taste disturbance framing softened: [at_a_glance] (QRS lines 434–437) states “Stomach upset, skin reactions and taste disturbance are common though mild”; the ER Conclusion applies “common though mild” only to stomach upset and skin reactions and separately says “taste disturbance drives people to stop”, while the ER Risks section notes it was reported “without publishing an incidence figure”.

Fixes 05/09/2026 02:45

  1. 1.3 / 7.3 — Taste disturbance framing restored: Rewrote the closing clause of [at_a_glance] from “Stomach upset, skin reactions and taste disturbance are common though mild” to “Stomach upset and skin reactions are common though mild, taste disturbance drives people to stop”, matching the ER Conclusion’s own framing. Word count remains within the 60-word limit.

Issues 05/09/2026 02:39

  1. 1.1 — Narrow-index label not ER wording: Key Interactions item 5 (line 588) reads “Narrow-index drugs cleared by UGT2B7”, but the ER bullet (line 306) says “Narrow-therapeutic-index drugs cleared by UGT2B7”; “narrow-index” is neither the ER’s wording nor an actual clinical term.

Fixes 05/09/2026 02:39

  1. 1.1 — Narrow-therapeutic-index label restored: Key Interactions item 5 changed from “Narrow-index drugs cleared by UGT2B7” to “Narrow-therapeutic-index drugs cleared by UGT2B7”, matching the ER bullet verbatim.

Issues 05/09/2026 02:29

  1. 4.5 — Sections not condensed to page budget: The Monitoring “Why” cells, the six Qualitative Assessment bullets, [monitoring_cadence] and the protocol subs are carried across near-verbatim from the ER rather than condensed, and gate items run 86–122 characters (e.g. “Autoimmune disease being actively managed on immunosuppressants without prescriber oversight”), pushing the sheet past the A4 print box.

Fixes 05/09/2026 02:29

  1. 4.5 — At-a-glance condensed: Tightened the lead paragraph from 57 to 53 words (325 characters), dropping “the body’s”, “the first”, “measurably” and “quickly” while keeping every ER-supported fact.
  2. 4.5 — Protocol subs shortened: [action_1_sub], [action_2_sub] and [action_3_sub] cut from 114/155/152 to 102/138/102 characters, e.g. “Extract standardized to 30% andrographolides” → “30%-andrographolide extract”.
  3. 4.5 — Time-to-effect subs shortened: [time_1_sub] and [time_3_sub] trimmed to a single line each (“Separation appears by day 3, clearest by day 5”; “Multiple sclerosis fatigue scores at 12 months”).
  4. 4.5 — Benefit tiers condensed: Medium, Low and Speculative reduced from 192/149/180 to 141/137/146 characters by stripping redundant framing (“clinical response in active”, “protection of lung tissue against”) while keeping every ER benefit.
  5. 4.5 — Gate items trimmed to key fact: Contraindication 3, 4 and 6 shortened (e.g. “Child-Pugh Class B or C, or transaminases above three times the upper limit of normal” → “Child-Pugh B or C, or transaminases above 3× the upper limit of normal”), and the 11 Key Interactions had their example drug lists trimmed to two representatives each, with every drug class and its parenthetical retained.
  6. 4.5 — Monitoring and Qualitative condensed: All nine “Why” cells cut to 28–45 characters (all marker names and target ranges left ER-verbatim), [monitoring_cadence] reduced from 259 to 230 characters, and Qualitative items 1 and 5 shortened; all 9 markers and all 6 qualitative markers retained.