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

Audit conducted on 23/08/2026 07:45 using AI4L / Grok 4

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
1.1	Every claim, magnitude, label, recommendation, and statement in the QRS is literally supported by content in the source ER.	🟢
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.	🟢
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”).	🟢
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.	🟢
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.	🟢
1.6	The QRS does not introduce new attributions.	🟢

2. Focus, Tone & Audience

#	Description	Result
2.1	The QRS follows the tone of the ER, which is determined by the ER’s own language, phrasing, and framing.	🟢
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢
2.4	The QRS avoids language that implies medical or clinical advice	🟢
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢
2.8	Information is presented in a concise and very compact manner	🟢
2.9	It DOES NOT address the reader directly	🟢
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.	🟢
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.	🟢
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.	🟢
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.	🟢
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.	🟢
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.	🟢

3. Template Integrity

#	Description	Result
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”	🟢
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢

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 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.	🟢
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢
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.	🟢

5. Metadata

#	Description	Result
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.	🟢
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.	🟢
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.	🟢
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.	🟢
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢
5.6	Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version 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)	🟢
5.8	The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]”	🟢
5.9	The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT)	🟢
5.10	The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]”	🟢
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)	🟢
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢
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.	🟢

#	Description	Result
6.1	[page_title] is set to the [canonical_topic] of the ER followed by “ - Quick Reference Sheet” (e.g., “Intervention - Quick Reference Sheet”). The [canonical_topic] is HTML-entity-encoded as needed (e.g., “&” for “&”)	🟢
6.2	[header_topic] is set to the [canonical_topic] of the ER, with HTML entities encoded as needed (e.g., “&” for “&”)	🟢
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢
6.4	[header_subline_model] is set to [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.	🟢

7. At-A-Glance Section

#	Description	Result
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢
7.2	[at_a_glance] is no longer than 60 words	🟢
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢
8.2	[stop_items] represent the Contraindications from the ER	🟢
8.3	Individual [stop_items] are formatted as <li></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 (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact.	🟢
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).	🟢
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	ER contraindications do not use ranking notation inside parentheses.
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.	🟢
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	Contraindications section is not empty.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER Key Interactions & Contraindications section	🟢
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢
9.3	Individual [caution_items] are formatted as <li></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 (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact.	🟢
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).	🟢
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	ER interactions do not use ranking notation inside parentheses.
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.	🟢
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	Key Interactions section is not empty.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER Protocol section	🟢
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢
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	ER Protocol lists more than three actionable implementation aspects.
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section.	🟢

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	🟢
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢
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	ER provides three distinct time-to-effect aspects.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢
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 information.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢
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.	🟢
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢
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 have items.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢
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.	🟢
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢
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 have items.

14. Monitoring

#	Description	Result
14.1	The section is derived from the ER Monitoring section	🟢
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢
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.	🟢

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢

Issues 23/08/2026 07:45

Pass rate 100.00%. No issues found.

Issues 23/08/2026 07:30

14.2 — Missing monitoring biomarkers: ER Monitoring baseline prose names fasting glucose and a coronary artery calcium scan; the QRS monitoring table (lines 603–700) lists only the nine biomarker-table rows and omits those two measurable items.

Fixes 23/08/2026 07:30

14.2 — Missing monitoring biomarkers: Added fasting glucose and coronary artery calcium scan rows to the monitoring table, using ER baseline-panel wording for target and why.

Issues 23/08/2026 07:26

11.2 — Time-to-effect order: Time-to-effect cells are ordered 1 year (event curves), then years (absolute benefit), then 4–6 weeks (LDL/apoB) around lines 479–513. The years-long absolute event reduction is the largest-magnitude related benefit and should lead; the 4–6 week particle drop is a surrogate, not an Expected Benefit.
12.3 — Benefit qualifier retained: benefits_low (line 528) is “Possible lower dementia risk”. “Possible” is an evidence-strength qualifier; the Low tier already encodes that, so 12.3 requires stripping it.
13.3 — Risk frequency qualifiers: risks_high (line 577) retains “rare” and “severe” in “including rare severe muscle breakdown” and “small” in “a small rise in blood sugar”. Section 13 treats frequencies and qualifiers as redundant detail.

Fixes 23/08/2026 07:26

11.2 — Time-to-effect order: Swapped the first two time-to-effect cells so Absolute benefit / Years leads, then Event curves / About 1 year, then LDL/apoB / 4–6 weeks.
12.3 — Benefit qualifier retained: Changed benefits_low from “Possible lower dementia risk” to “Lower dementia risk”.
13.3 — Risk frequency qualifiers: Stripped “rare”, “severe”, and “small” from risks_high, leaving “Muscle symptoms, including muscle breakdown; new-onset type 2 diabetes and a rise in blood sugar; …”.

Issues 23/08/2026 07:09

1.3 — Dropped clinical qualifier: Protocol action_1_sub (QRS line 450) omits “clinical” from the ER Therapeutic Protocol phrase “after clinical atherosclerotic disease or LDL cholesterol of 190 mg/dL or higher”, which slightly broadens the high-intensity setting.
4.3 — Invented time labels: Time-to-effect labels “Vascular events” and “Absolute event benefit” (QRS lines 483 and 494) are invented; the ER Practical Considerations sentence uses “Event curves” and “absolute benefit”.

Fixes 23/08/2026 07:09

1.3 — Dropped clinical qualifier: Restored “clinical” in protocol action_1_sub, from “after atherosclerotic disease” to “after clinical atherosclerotic disease”, matching the ER Therapeutic Protocol bullet.
4.3 — Invented time labels: Replaced time-to-effect time_1_label “Vascular events” with “Event curves” and time_2_label “Absolute event benefit” with “Absolute benefit”, matching the ER Practical Considerations wording.

Issues 23/08/2026 06:57

12.3 — Qualifier in high benefits: benefits_high (QRS line 522) appends the body qualifier “uncertain at low 10-year risk” to lower all-cause mortality. The ER heading is “Lower All-Cause Mortality”; 12.3 allows only the key fact, with no qualifiers.

Fixes 23/08/2026 06:57

12.3 — Qualifier in high benefits: Removed “, uncertain at low 10-year risk” from benefits_high. The high-tier line now states only the two ER headings: fewer heart attacks, clot-type strokes, artery-opening procedures, and cardiovascular deaths; lower all-cause mortality.

Issues 23/08/2026 06:35

1.2 / 1.3 — All-cause mortality overstated: Benefits High states “lower all-cause mortality” without the ER’s cautious “⚠️ Conflicted” / “uncertain at low 10-year risk” framing, which strengthens the claim.
9.5 — St. John’s wort agents dropped: Key Interactions lists only “St. John’s wort” and omits the ER’s named agents simvastatin and atorvastatin that determine whether the interaction applies.
13.3 — Risk qualifiers and mechanism retained: Speculative risk keeps “from coenzyme Q10 depletion beyond muscle symptoms”; Medium risk keeps the qualifier “Slightly higher” instead of the key fact alone.

Fixes 23/08/2026 06:35

1.2 / 1.3 — All-cause mortality phrasing: Benefits High now reads “lower all-cause mortality, uncertain at low 10-year risk” instead of an unqualified mortality claim.
9.5 — St. John’s wort agents: Key Interactions St. John’s wort item now names simvastatin and atorvastatin as “(simvastatin, atorvastatin)”.
13.3 — Risk qualifiers stripped: Medium risk is now “Hemorrhagic stroke risk after prior stroke”; speculative risk is now “Lasting mitochondrial injury” without the CoQ10 mechanism clause.

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

Summary

1. General Rules

2. Focus, Tone & Audience

3. Template Integrity

4. Formatting

5. Metadata

6. Page Title & Header

7. At-A-Glance Section

8. Contraindications

9. Key Interactions

10. Protocol

11. Time to Effect

12. Benefits

13. Risks

14. Monitoring

15. Qualitative Assessment

Issues 23/08/2026 07:45

Issues 23/08/2026 07:30

Fixes 23/08/2026 07:30

Issues 23/08/2026 07:26

Fixes 23/08/2026 07:26

Issues 23/08/2026 07:09

Fixes 23/08/2026 07:09

Issues 23/08/2026 06:57

Fixes 23/08/2026 06:57

Issues 23/08/2026 06:35

Fixes 23/08/2026 06:35