Audit: QRS - Candesartan for Health & Longevity

Audit conducted on 20/07/2026 03:19 using AI4L / Opus 4.8

Summary

Items	Count
Total	91
Passed	81
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 variable content traces to the ER (Conclusion, Protocol, Expected Benefits, Risks, Key Interactions & Contraindications, Monitoring).
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.	🟢	“Brain-aging and lifespan benefits stay unproven” mirrors the ER Conclusion’s “not been proven” / “animal and mechanism data only”.
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”).	🟢	“never in pregnancy” preserves the ER’s absolute contraindication; no softening or strengthening observed.
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/Interactions derive from the ER “Key Interactions & Contraindications”; benefits/risks from their respective sections. No category drift.
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 IDs, or brand names.
1.6	The QRS does not introduce new attributions.	🟢	No attributions introduced.

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.	🟢	Uses the ER’s register (“prescription medicine”, “angiotensin receptor blocker”).
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Balanced expert-accessible framing throughout.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Presents evidence, not directives.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	Declarative statements of evidence; no prescriptive advice in variable content.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Information-presentation voice maintained.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person address in any variable.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Plain-language throughout; technical terms only where necessary.
2.8	Information is presented in a concise and very compact manner	🟢	Compact one-page layout with condensed lists.
2.9	It DOES NOT address the reader directly	🟢	Confirmed; 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.	🟢	Framing targets a proactive, monitoring-oriented 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.	🟢	Monitoring cadence and titration content assume a committed reader.
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 general-population framed.
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.	🟢	Longevity-oriented weighting preserved.
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.	🟢	“Longevity” used; no “anti-aging” phrasing.
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 terminology used consistently.

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 headings, gate headings, tier labels, and table headers match the template verbatim.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	Full set of data-qrs-var spans present (header, at_a_glance, actions, times, benefits, risks, stop/caution items, markers 1–7, cadence, qualitative 1–5).
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Non-content template spans (website markers) left intact.

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 relevant to 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.	🟢	No mismatched bold-label mappings; monitoring/marker labels derive faithfully from the ER table.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Marker and tier labels match the ER.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No tier emojis; the ER’s “⚠️ Conflicted” markers correctly dropped.
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 to single-page budget (e.g., BP-lowering supplement list trimmed).

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 (lines 2–14) is first after the 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.	🟢	YAML delimited by opening/closing “—” (lines 3 and 13).
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; not rendered.
5.4	All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting.	🟢	Only “duration” is quoted (contains a colon); others unquoted and trimmed.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	“er_filename: candesartan_2026-0720-0216_Opus_ER.md” matches the source ER.
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” matches QRS.md version.
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-0720-0310” is well-formed.
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: 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.
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: Opus 4.8”.
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 4.8” = nickname + version, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	“qrs_filename: candesartan_2026-0720-0216_Opus_QRS.html” matches the file.
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.	🟢	Values trimmed and correctly quoted only where required.

#	Description	Result	Comments
6.1	[page_title] is set to the [canonical_topic] of the ER `frontmatter` followed by “ - Quick Reference Sheet” (e.g., “Intervention - Quick Reference Sheet”). The [canonical_topic] is HTML-entity-encoded as needed (e.g., `&` for `&`)	🟢	“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., `&` for `&`)	🟢	“Candesartan for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	“07/20/2026” derived from 2026-0720-0310.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	“Opus 4.8”.
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 contains only title and standard subline.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER `Conclusion` section	🟢	Condenses the ER Conclusion (cardiovascular strength, unproven brain/lifespan, manageable cautions).
7.2	[at_a_glance] is no longer than 60 words	🟢	58 whitespace-delimited tokens, within the 60-word limit.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause maps to the Conclusion (stroke, heart failure, kidneys, diabetes, pregnancy).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “cardiovascular” is broadly understood.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial citations.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No effect sizes or statistics.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER `Key Interactions & Contraindications` section	🟢	Stop items derive from the ER “Populations who should avoid this intervention” bullet.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All five ER contraindications present (pregnancy, bilateral renal artery stenosis, prior ARB angioedema, severe hyperkalemia, advanced kidney impairment).
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Each item is a discrete `<li>`.
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 — these trailing clauses are stripped. Just the key fact.	🟢	Trailing clauses stripped (e.g., “requires specialist supervision rather than routine use” removed).
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.	🟢	Thresholds preserved (“potassium >5.5 mmol/L”, “eGFR <30”), “all trimesters” preserved.
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 the contraindications; “>” appears only as a threshold value.
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	🟢	Caution items derive from the ER interactions bullets.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Covers ACE inhibitors/aliskiren, K-sparing diuretics, lithium, trimethoprim, NSAIDs, K supplements/salt substitutes, licorice, BP-lowering supplements, SGLT2 inhibitors; no overlap with contraindications.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Each interaction is a discrete `<li>`.
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 — these trailing clauses are stripped. Just the key fact.	🟢	Mechanistic explanations and “(caution …)” clauses stripped.
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.	🟢	Named-drug examples preserved (lisinopril/ramipril; spironolactone/eplerenone/amiloride; empagliflozin/dapagliflozin, etc.).
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	No ranking notation used in the ER interactions.
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	🟢	Derived from the ER Therapeutic Protocol / Risk Mitigation dosing content.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER `Protocol` section	🟢	Starting Dose, Target Dose, Timing — the key actionable aspects.
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 distinct actionable aspects are present and filled.
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER `Protocol` section.	🟢	All action cells populated with ER-supported dosing detail.

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 onset (~2h), full BP effect (2–4 weeks), heart & kidney benefits (months).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered from immediate BP effect through months-scale organ benefits.
11.3	If less that three distinct time-to-effect aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing.	N/A	Three distinct time-to-effect aspects are present.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All time cells populated from the ER Practical Considerations.
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.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER `Expected Benefits` section	🟢	Tiers mirror the ER Expected Benefits headings.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four tier variables 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.	🟢	Concise benefit names only.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	“(Reduced Albuminuria)” and “⚠️ Conflicted” 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 empty-state phrasing.	N/A	All four tiers have items in the ER.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER `Potential Risks & Side Effects` section	🟢	Tiers mirror the ER Risks headings.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four tier variables 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 risk names only.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	“(Teratogenicity)”, “(High Blood Potassium)”, “⚠️ Conflicted” stripped.
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 empty-state phrasing.	N/A	All four tiers have items in the ER.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER `Monitoring` section	🟢	Derived from the ER Monitoring Protocol & Defining Success table.
14.2	All measurable/quantifiable biomarkers from the `Monitoring` section are listed	🟢	All 7 ER biomarkers present (BP, potassium, creatinine/eGFR, BUN, sodium, uric acid, glucose/HbA1c).
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.	🟢	Cadence populated with the ER’s 1–2 week / 3 & 6 month / 6–12 month schedule.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER `Monitoring` section	🟢	Derived from the ER qualitative markers of success.
15.2	All subjective/qualitative biomarkers from the `Monitoring` section are listed	🟢	All 5 qualitative markers present (energy/dizziness, sleep, cognition, exercise tolerance, warning symptoms).

Issues 20/07/2026 03:19

Pass rate 100.00%. No issues found.