Audit: QRS - Candesartan for Health & Longevity

Audit conducted on 11/09/2026 05:30 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. 🟢 Every element traced to the ER: at-a-glance to ER Conclusion (424–428), protocol cells to ER 338–340, time-to-effect to ER 373/350/340, benefits to ER Expected Benefits headings, risks to ER Potential Risks & Side Effects headings, gates to ER 303–323, markers and cadence to ER 390–401, qualitative items to ER 405–410.
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. 🟢 ER “no human evidence behind it” (426) is carried as “No human longevity evidence exists” in [at_a_glance]; ageing and brain-injury claims stay in the Speculative tier, matching ER 210–218.
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”). 🟢 Pregnancy stays an absolute Contraindication (line 567), not a caution; the heart-failure benefit keeps the ER’s “where the pumping chamber is weakened” restriction (line 537) rather than being generalised.
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. 🟢 Category boundaries hold: heat/sauna/fasting appears as a Key Interaction (599–601) from ER “Other interventions” (311) and separately as a Speculative risk (631) from ER 289–291, exactly as the ER splits them. No Benefit-Modifying Factors or Risk-Modifying Factors content leaks into the gates.
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, NCT IDs, study names, author names, or brand names anywhere in the QRS; the CHARM/SCOPE/TROPHY/DIRECT programme names and Atacand/Blopress from the ER are all omitted.
1.6 The QRS does not introduce new attributions. 🟢 No attributions of any kind; the ER’s attributed phrasings (“The CHARM investigators started…”, “The Norwegian headache group at Trondheim…”) are rendered as unattributed participles in [action_2_sub] and [action_3_sub].

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. 🟢 Neutral, descriptive, evidence-first register throughout, matching the ER; benefit and risk labels reuse the ER’s own wording.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Monitoring targets and time-to-effect windows give actionable handles; “predictable and detectable” in [at_a_glance] frames the harms as manageable rather than alarming.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Protocol cells are stated as observed practice in participial form (“Titrated over four to eight weeks”, “Doubled every two weeks”, “Run for at least twelve weeks”), not as orders.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No imperatives, no “should take”, no prescriptive verbs directed at anyone; dosing is described, not instructed.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No occurrence of “recommend”, “advise”, “we suggest” or equivalent; every cell is a statement of what the evidence or practice shows.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns anywhere in the file (verified across the whole document); no vocatives.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain-language equivalents used wherever the ER offers them (“pumping chamber is weakened”, “diabetic eye disease”, “urine albumin”, “elevated blood potassium”); the technical terms that remain are decision-gate drug and condition names that cannot be replaced without losing the gate.
2.8 Information is presented in a concise and very compact manner 🟢 Gate and tier items are single clauses; benefit and risk tiers are semicolon-joined lists with no elaboration.
2.9 It DOES NOT address the reader directly 🟢 Confirmed — no direct address in any span, including the qualitative items, which stay descriptive (“Light-headedness on standing…”, “Exercise tolerance and perceived effort at a fixed workload…”).
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. 🟢 Tight optimal-range monitoring targets (potassium 4.0–4.8 mmol/L, eGFR above 90, albumin-to-creatinine under 10 mg/g) are pitched well inside conventional thresholds, as this audience requires.
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. 🟢 An eight-marker chemistry panel, morning-and-evening home pressure for a week before each review, standing pressure at 1 and 3 minutes, and a six-item symptom diary all assume high willingness to execute.
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 simplification to a single “ask your doctor” action; the sheet carries the full titration, monitoring and interaction detail.
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] closes on “No human longevity evidence exists”, which is the decisive point for a longevity-motivated reader even though it is secondary for a hypertensive patient; the heat/sauna/endurance interaction is retained for the same reason.
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”/”anti-ageing” appear nowhere; the title uses “Health & Longevity” and the speculative benefit reads “Slowed biological ageing”.
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)”; “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. 🟢 [at_a_glance] uses “oral medication” (line 434); no “pill”, “taken by mouth”, “shot” or “bad reaction” anywhere in the file.

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 byte-for-byte: “Protocol” (446), “Time to effect” (490), “Benefits” (532), “Risk & Side Effects” (611), “Monitoring” (638), “Qualitative Assessment” (767), “Contraindications” (564), “Key Interactions” (583), the four tier labels in both the benefits and risks cards, and “Marker”/”Target”/”Why” (642–644).
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All 34 template variables present; the only additions are the repeatable marker_#_* rows (8 instances) and qualitative_item_# entries (6 instances) that the template defines as repeatable.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 The non-variable spans <span website="evidence_review">, <span website="audit"> and <span website="full_review"> are untouched (423, 426, 440); a structural tag-level diff against the template shows no additions or removals beyond the repeated gate <li>, monitoring <tr> and qualitative <li> content, and the CSS block is byte-identical.

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 source ER section that feeds the QRS is empty — all four benefit tiers, all four risk tiers, the contraindication list, the interaction list, the biomarker table and the qualitative list are populated in the ER.
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 are verbatim ER bold labels: “Standard hypertension protocol”, “Heart-failure protocol”, “Migraine protocol” (ER 338–340). Interaction items carry the ER bold labels verbatim, including the parenthesised drug lists (ER 303, 305, 306, 308, 309, 310). Biomarker names are verbatim ER table entries (ER 394–401).
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Benefit and risk items reuse the ER’s #### headings word for word; the only rewording is sentence-case adjustment inside the semicolon lists. Time-to-effect labels (“Blood pressure”, “Heart-failure outcomes”, “Migraine”) name the three domains the ER’s single “Time to effect” bullet itself enumerates (ER 373), since that bullet supplies no per-domain bold labels.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 Zero emoji characters in the file; the ER’s tier emoji and its “⚠️ Conflicted” markers are all stripped. Tiers are conveyed by <strong> labels plus the .benefits and .risks CSS palettes.
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. 🟢 Content is already at the minimum the checklist mandates — every contraindication (8.2), every interaction (9.2), every biomarker (14.2) and every qualitative marker (15.2) must appear — and each is condensed to a single clause with all parentheticals and rationale stripped. The two gates sit side by side in the 2-column grid, so the 9 and 8 items share one vertical band.

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: the metadata comment opens immediately after <!doctype html> on line 1 and closes before the template’s own <!-- QRS (Quick Reference Sheet) — blank 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 --- on line 3, closing --- on line 13; the preamble text “QRS — Metadata (invisible, parsed by audit tooling)” precedes the opening delimiter, which is permitted.
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. 🟢 Entirely inside an HTML comment; none of the values (er_filename, git_user, git_issue, duration) reappear in 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. 🟢 All values trimmed and unquoted except duration: "00:06", which contains a colon and therefore requires YAML quoting.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 Line 4: er_filename: candesartan_2026-0911-0316_Opus_ER.md, matching the ER frontmatter filename exactly.
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-0911-0521, correct YYYY-MMDD-HHMM form.
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” — single word, no version, no 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 only, with no context-window or other qualifier appended.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 Line 9: qrs_filename: candesartan_2026-0911-0316_Opus_QRS.html, matching the file’s actual name 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: no stray whitespace, and duration is the only quoted value, justified by its embedded 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., &amp; for &) 🟢 Line 22: Candesartan for Health &amp; Longevity - Quick Reference Sheet, matching ER canonical_topic with the ampersand entity-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: Candesartan for Health &amp; Longevity, with no suffix and the ampersand encoded.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 Line 421: 09/11/2026, the correct MM/DD/YYYY rendering of qrs_creation_date: 2026-0911-0521.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Line 425: 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’s own subline. The ER’s “Also known as: Candesartan Cilexetil, Atacand, Blopress, Amias, TCV-116” line (ER 30) is correctly not carried over, and no badge or audit date appears.

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 ER Conclusion paragraphs (424–428) into what the drug is, what it reliably does, what the monitorable harms are, and what is unproven.
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. 🟢 “inexpensive, long-established oral medication” → ER 424; “lowers blood pressure reliably for a full day on one dose” → ER 424; “reduces death and hospital admission in heart failure where the pumping chamber is weakened” → ER 424; “reduces migraine days” → ER 424; “Falling pressure, rising potassium and reduced kidney filtration are predictable and detectable” → ER 428; “No human longevity evidence exists” → ER 426.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms and no class names. “angiotensin II type 1 receptor blocker” is rendered as “blocking the body’s main pressure-raising hormone”, “reduced ejection fraction” as “where the pumping chamber is weakened”, and “hyperkalaemia”/”declining eGFR” as “rising potassium”/”reduced kidney filtration”.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial names, years, participant counts or p-values; CHARM and the migraine trials are referred to only through their plain-language outcomes.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No numbers of any kind; the ER’s hazard ratios and confidence intervals are all omitted.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All nine items map one-to-one onto the ER’s “Populations who should avoid Candesartan” list (ER 315–323) inside that section.
8.2 [stop_items] represent the Contraindications from the ER 🟢 Complete: pregnancy, breastfeeding, prior angioedema, bilateral renal artery stenosis, aliskiren combination, severe cholestasis / Child-Pugh C, first 72 hours after stroke, severe valve stenosis / obstructive cardiomyopathy, untreated potassium above 5.5 mmol/L — nine ER entries, nine QRS items, nothing added or dropped.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Nine <li> elements inside the stop_items span (lines 567–578).
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 “People with/who are” stems and its plain-language glosses “(blocked bile flow from the liver)”, “(the most severe grade of cirrhosis)” and “(thickened heart muscle that obstructs blood leaving the heart)” are all stripped. No dash-introduced trailing clause 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). 🟢 Every decision-relevant qualifier survives: “First 72 hours after acute stroke, unless pressure exceeds emergency thresholds”, “Child-Pugh Class C”, “filtration rate below 60 mL/min/1.73 m²”, “above 5.5 mmol/L”, “in a single functioning kidney”, “with resting outflow obstruction”.
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 its contraindication list; the only “>”-like symbols are numeric thresholds already expressed in words (“below 60”, “above 5.5”).
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 identifies nine such populations, and the section is correspondingly populated rather than 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 eight items map onto the ER’s interaction bullets at 303–311.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Eight of the ER’s nine interaction bullets are carried. The omitted one — “Direct renin inhibitors (aliskiren)” (ER 304) — is an absolute contraindication and already appears in [stop_items] (line 571), so its exclusion here is exactly what this item requires.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Eight <li> elements inside the caution_items span (lines 586–601).
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 ER bullet’s caution level, mechanism, consequence and mitigation clause is stripped, leaving only the interacting agent or exposure. The ER’s generic “Other interventions” label is replaced by its actual content, which is the informative part. No dash-introduced trailing clause remains.
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 named example drugs survive: “(ramipril, lisinopril, enalapril)”, “(spironolactone, eplerenone)”, “(ibuprofen, naproxen, high-dose aspirin)”, “(hydrochlorothiazide, chlortalidone, furosemide)”, and the full supplement list “(beetroot or dietary nitrate, garlic extract, hibiscus, magnesium, high-dose omega-3, potassium citrate)”.
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 bullets use no ranking notation; all parenthetical content is plain comma-separated drug lists.
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 identifies nine interactions, and the section is correspondingly populated rather than empty.
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 come from the ER Therapeutic Protocol section, bullets at ER 338, 339 and 340.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 The three named dose protocols are selected over the section’s non-actionable bullets (competing approaches, best time of day, half-life, pharmacogenetics, sex-based differences, baseline biomarkers), and they correspond to the ER’s three strongest benefits.
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 three distinct actionable protocols, so all three sets are used and none is left unfilled.
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 carry substantive ER-derived content: labels are the ER’s bold labels verbatim; values give the dose ranges “8–16 mg → 32 mg once daily”, “4 mg → 32 mg target”, “16 mg once daily”; subs give the titration pace, the tolerated-dose rule and the twelve-week judging window.

11. Time to Effect

# Description Result Comments
11.1 The three sets of [time] items cover the three most important time-to-effect aspects from the ER 🟢 Blood pressure, heart-failure outcomes and migraine — precisely the three domains the ER’s “Time to effect” bullet enumerates (ER 373), reinforced by ER 350.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Order matches the ER’s own High-tier ordering: Blood Pressure Reduction, then Reduced Cardiovascular Death and Heart-Failure Admission, then Fewer Migraine Days (ER 140–156).
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 supplies three distinct time-to-effect aspects, 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. 🟢 “1–2 weeks / Full effect reached by four weeks” from ER 373; “Months to years / Response judged over several months” from ER 373 and 350; “8–12 weeks / Twelve weeks at 16 mg before judging response” from ER 373 and 340.
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 explicit time-to-effect information (ER 373, 350), so the section is correctly retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All thirteen items correspond to the thirteen #### benefit headings in ER 134–218, with tier assignment preserved.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present and populated (lines 534–557), matching the ER’s four benefit tiers with 4 / 6 / 1 / 2 items respectively.
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. 🟢 Every Magnitude: paragraph, mechanism sentence, funding note and confidence interval is stripped; each item is the ER heading alone. The one retained scope phrase, “where the pumping chamber is weakened”, is the ER’s own net reading (ER 148) and is load-bearing — dropping it would generalise a benefit the ER explicitly confines.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses anywhere in the benefits card; the ER’s “⚠️ Conflicted” markers on two headings are also removed.
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 benefit tiers carry items in the ER, so no span needed hiding.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All nine items correspond to the nine #### risk headings in ER 229–291, with tier assignment preserved.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present and populated (lines 613–632), with 3 / 2 / 3 / 1 items respectively, matching the ER.
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 item is the bare ER heading; the CHARM incidence figures, odds ratios, risk-factor lists and reversibility notes are all dropped.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses in the risks card; the ER’s inline glosses “(hyperkalaemia — too much potassium in the blood…)” and “(rapid deep swelling of the lips, tongue, face or airway)” and the “⚠️ Conflicted” marker on Cancer Occurrence are all removed.
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 carry items in the ER, so no span needed hiding.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Table and cadence both come from the ER Monitoring Protocol & Defining Success section (ER 388–401).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All eight ER table rows present with names, targets and rationale verbatim: home blood pressure 110–125 / 70–80 mmHg, standing pressure drop under 10 mmHg, potassium 4.0–4.8 mmol/L, creatinine within 30% of pre-treatment, eGFR above 90 mL/min/1.73 m², sodium 137–142 mmol/L, albumin-to-creatinine under 10 mg/g, haemoglobin 13.5–16.5 / 12.0–15.5 g/dL.
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 756–761 condense the ER’s cadence prose (ER 390) faithfully: baseline before first dose, chemistry at one to two weeks after starting and after each increase, three months, then six to twelve months once stable, unscheduled repeats after fluid loss or a new diuretic/anti-inflammatory, and a week of home readings before each review.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 All six items come from the ER’s “Qualitative markers worth tracking alongside the laboratory values” list (ER 403–410).
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 Six ER items, six QRS items, carried verbatim: light-headedness on standing, exercise tolerance and perceived effort, headache/migraine day count, cognitive clarity and word-finding, muscle cramps/palpitations/weakness, and sleep quality and night-time waking.

Issues 11/09/2026 05:30

Pass rate 100.00%. No issues found.