Audit: QRS - Candesartan for Health & Longevity of the ER frontmatter

Audit conducted on 23/07/2026 06:18 using AI4L / Grok 4

Iterations

Summary

Items Count
Total 91
Passed 83
Failed 0
N/A 8
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 doses, benefits, risks, gates, monitoring rows, and at-a-glance facts map to ER Protocol, Expected Benefits, Risks, Key Interactions & Contraindications, Monitoring, Conclusion.
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. 🟢 At-a-glance and speculative tiers retain ER caution (“early and small”, “not a general longevity drug without those indications”, long-term unknowns).
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 remains absolute stop; stroke stays outside the “strong evidence” clause via “plus”; speculative longevity not upgraded.
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. 🟢 Benefits/risks/gates drawn from matching ER sections only.
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, expert names, or brand names (e.g., Atacand) in the QRS body.
1.6 The QRS does not introduce new attributions. 🟢 No new study or expert attributions.

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. 🟢 Matches ER’s evidence-weighted, cautious longevity framing.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Dense facts with plain-language at-a-glance.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Presents protocol facts without doctorly commands.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Footer disclaimer; body presents ER-derived facts.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No recommend/advise/should-direct address in filled variables.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No “you/your/reader” in content spans.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 At-a-glance uses plain terms; technical labels retained where ER labels or gate qualifiers require them.
2.8 Information is presented in a concise and very compact manner 🟢 Semicolon-tier lists, short gate bullets, compact protocol cells.
2.9 It DOES NOT address the reader directly 🟢 No direct address.
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. 🟢 Longevity framing and speculative tier match that 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. 🟢 Full monitoring and titration detail retained for engaged users.
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. 🟢 Not dumbed down to casual consumer copy.
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. 🟢 Notes not a general longevity drug without HTN/HF/migraine indications.
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. 🟢 Uses “longevity” / “healthspan”; no “anti-aging” voice.
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. 🟢 Clinical terms (hyperkalemia, angioedema, eGFR) where appropriate; no colloquial drug slang.

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 labels present and unmodified.
3.2 All “” from the [qrs_template] are present in the the QRS. 🟢 All template variables present; marker_# / qualitative_item_# expanded to numbered instances (1–6 markers, 1–4 qualitative).
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 No evidence of unsolicited span edits outside filled content variables.

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 applicable QRS-mapped ER section 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. 🟢 Protocol actions use ER bold labels (Standard hypertension dosing; Migraine prophylaxis protocol; Sex and age); monitoring markers match ER table.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Labels track ER wording.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji tier indicators in the QRS.
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 condensed into single-sheet structure with print A4 CSS.

5. Metadata

# Description Result Comments
5.1 The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content. 🟢 Metadata comment immediately follows doctype.
5.2 Inside that HTML comment the YAML block is delimited by a line “—” opening and a line “—” closing. Text before the opening “—” is permitted but is not parsed as YAML. 🟢 Opening/closing — present.
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. 🟢 HTML comment only.
5.4 All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. 🟢 Values trimmed; duration quoted for colon in “00:01”.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: candesartan_2026-0723-0422_Grok_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]” 🟢 qrs_prompt_version: 26.7.02
5.7 Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) 🟢 qrs_creation_date: 2026-0723-0607
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢 qrs_creator_ai_nickname: Grok
5.9 The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) 🟢 Single word “Grok”.
5.10 The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” 🟢 qrs_creator_ai_fullname: Grok 4
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) 🟢 “Grok 4” = nickname + version.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename: candesartan_2026-0723-0422_Grok_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. 🟢 Same cleanliness as 5.4.

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 &) 🟢 “Candesartan for Health & 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 &) 🟢 “Candesartan for Health & Longevity”
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 2026-0723-0607 → 07/23/2026
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Grok 4
6.5 No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. 🟢 Only template subline structure; no AKA/badge/audit stamp.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Condenses Conclusion: BP/HF/migraine evidence, stroke, exploratory brain work, risks, not general longevity drug.
7.2 [at_a_glance] is no longer than 60 words 🟢 55 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each clause maps to Conclusion / benefits / risks.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 Plain phrasing (blood-pressure drug, high blood potassium, kidney stress); no specialist acronyms.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial names or stats.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No effect sizes/RRs.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 From ER populations-who-should-avoid list.
8.2 [stop_items] represent the Contraindications from the ER 🟢 Pregnancy; bilateral renal-artery stenosis; ARB/ACE angioedema; severe volume depletion; aliskiren in diabetes; advanced CKD with specialist caveat.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Six <li> items.
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. 🟢 No trailing dash clauses; elaborations stripped.
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). 🟢 eGFR <30 threshold retained for advanced CKD.
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. 🟢 No bare ranking symbols requiring normalization.
8.7 If no [stop_items] are present the section is left empty N/A Stop items are present.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 From ER interaction bullets.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Seven interaction lines; aliskiren-in-diabetes absolute remains under stop; dual RAS ACE/aliskiren caution retained under interactions.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Seven <li> items.
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. 🟢 Mechanistic tails stripped; key agents retained.
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). 🟢 Example ACE inhibitors, K-sparing agents, NSAIDs, supplement list 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. 🟢 No bare ranking symbols.
9.7 If no [caution_items] are present the section is left empty N/A Caution items are present.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 From ER Therapeutic Protocol.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Standard hypertension dosing; migraine prophylaxis protocol; sex and age (lower elderly starts).
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 Three actionable aspects used.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 All three action triples filled from ER dosing 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 🟢 BP; heart-failure outcomes; migraine prevention (CEDAR 1-year exploratory omitted as lower priority).
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered BP → HF outcomes → migraine (all high-tier benefits; BP primary).
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 time aspects used.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 Hours–days / ~4 weeks; months–years; 8–12 weeks at target dose.
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 ER Practical Considerations provides time-to-effect data.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All tiers from Expected Benefits.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans 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. 🟢 Semicolon-separated key facts only.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 e.g., “(Prehypertension)”, DIRECT conflict note, non-hypertensive MCI parenthetical stripped.
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 sub-sections have items.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All tiers from Potential Risks & Side Effects.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans 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. 🟢 Concise tier lists.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 Frequencies/mechanisms stripped; “(On Standing)” dropped from dizziness item.
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 sub-sections have items.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 From Monitoring Protocol & Defining Success.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All six table biomarkers: home/ambulatory SBP & DBP, serum K⁺, creatinine/eGFR, serum sodium, weight (HF).
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. 🟢 Matches ER 1–2 weeks / ~4 weeks / 3–6 months cadence and NSAID/illness recheck.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 From ER qualitative markers list.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All four: orthostatic/falls; migraine diary; HF exercise/edema; energy/cognition exploratory.

Issues 23/07/2026 06:18

Pass rate 100.00%. No issues found.

Issues 23/07/2026 06:12

  1. 2.15 — Colloquial protocol phrasing: Protocol action_3_value uses “Start low, go slow” rather than formal clinical terminology.
  2. 4.2 / 4.3 — Non-verbatim labels: Protocol labels abbreviated/invented (“Hypertension dose”, “Migraine prophylaxis”, “Titration”) versus ER bold labels; monitoring marker “Weight (heart failure)” versus ER “Weight (HF)”.
  3. 12.3 / 12.4 — Benefits elaborations/parentheticals: benefits_high keeps “(cardiovascular death and hospitalization)”; benefits_low keeps the non-hypertensive MCI population qualifier.

Fixes 23/07/2026 06:13

  1. 2.15 — Colloquial protocol phrasing: Replaced action_3_value “Start low, go slow” with formal wording “Lower starts in elderly” (and aligned action_3 to ER Sex and age protocol bullet).
  2. 4.2 / 4.3 — Non-verbatim labels: Set action_1_label to “Standard hypertension dosing”, action_2_label to “Migraine prophylaxis protocol”, action_3_label to “Sex and age”; set marker_6_name to “Weight (HF)”.
  3. 12.3 / 12.4 — Benefits elaborations/parentheticals: Stripped “(cardiovascular death and hospitalization)” from benefits_high and the non-hypertensive MCI population qualifier from benefits_low.