Audit: QRS - Alirocumab for Health & Longevity

Audit conducted on 30/06/2026 04:31 using AI4L / Opus 4.8

Summary

Items	Count
Total	91
Passed	91
Failed	0
N/A	0
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 content traces to the ER (protocol, benefits, risks, monitoring, gates).
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.	🟢	Speculative tiers preserve cautious framing (“Unknown very-long-term effects”).
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 and benefits preserve ER strength.
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 derive from Key Interactions & Contraindications; risks from Risks section.
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/expert names introduced; drug names (inclisiran, statins) are from ER.
1.6	The QRS does not introduce new attributions.	🟢	No attributions added.

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 tone.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Maintained throughout.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Presents information, not prescriptions.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	Footer disclaimer present; no directive advice.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Information-presenting voice.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No direct address.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Plain language with brief glosses where needed.
2.8	Information is presented in a concise and very compact manner	🟢	Compact cards and lists.
2.9	It DOES NOT address the reader directly	🟢	No “you” usage.
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 reflects 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.	🟢	Cost/self-injection burden acknowledged without dilution.
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.	🟢	Audience-appropriate.
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 flags lower-risk uncertainty.
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”; no “anti-aging”.
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.	🟢	Uses “injection”, “self-injection”, clinical terms.

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/labels intact.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All template spans present (marker_# and qualitative_item_# expanded to numbered instances).
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	No unaddressed spans modified.

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”	🟢	No empty source sections; all tiers populated from 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.	🟢	Tier labels (High/Medium/Low/Speculative) match.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Labels faithful to ER.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji indicators in 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 to fit single page.

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.	🟢	Comment at lines 2-13, first element.
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.	🟢	Delimited by — at lines 3 and 12.
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.	🟢	Inside 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.	🟢	Values trimmed, no needless quotes.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	er_filename: alirocumab_2026-0630-0333_Opus_ER.md (line 4).
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.5.18 (line 5).
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-0630-0333 (line 6).
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 (line 7).
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.
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 (line 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.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	qrs_filename: alirocumab_2026-0630-0333_Opus_QRS.html (line 9).
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.	🟢	All values clean.

#	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 `&`)	🟢	“Alirocumab for Health & Longevity - Quick Reference Sheet” (line 21).
6.2	[header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., `&` for `&`)	🟢	“Alirocumab for Health & Longevity” (line 416).
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	06/30/2026 (line 420).
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	“Opus 4.8” (line 424).
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 subline.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER `Conclusion` section	🟢	Distills ER Conclusion (lines 420-422).
7.2	[at_a_glance] is no longer than 60 words	🟢	The at_a_glance text (line 432) is 48 words, within the 60-word limit.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Cost, self-injection, low long-term data, CV benefit all in ER Conclusion.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	Uses “harmful cholesterol”, “heart attacks, strokes”; no jargon.
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 statistics cited.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER `Key Interactions & Contraindications` section	🟢	Derived from ER lines 274-288.
8.2	[stop_items] represent the Contraindications from the ER	🟢	Hypersensitivity, pregnancy/breastfeeding, HoFH with no LDLR function (ER line 288).
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Three <li> items (lines 541-543).
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.	🟢	“(unlikely to respond)” rationale dropped; items concise.
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.	🟢	“(severe allergic reaction or vasculitis)” severity qualifier 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.	🟢	No ranking notation present; not applicable, no symbols carried through.
8.7	If no [stop_items] are present the section is left empty	🟢	Items present; section populated.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER `Key Interactions & Contraindications` section	🟢	Derived from ER lines 274-288.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Statins/ezetimibe, additive supplements, other PCSK9 therapies; no contraindication overlap.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Three <li> items (lines 551-553).
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.	🟢	Concise; no trailing clauses.
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.	🟢	Example drugs preserved (atorvastatin, rosuvastatin; plant sterols/stanols, soluble fiber, red yeast rice, berberine; inclisiran).
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 ranking notation present; no symbols carried through.
9.7	If no [caution_items] are present the section is left empty	🟢	Items present; section populated.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER `Protocol` section	🟢	Derived from ER Therapeutic Protocol (lines 304-326).
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER `Protocol` section	🟢	Starting dose, up-titration, background therapy.
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.	🟢	All three sets have genuine content; not applicable.
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER `Protocol` section.	🟢	All cells meaningful and ER-derived.

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	🟢	LDL begins, near-maximal LDL, CV benefit (ER line 355).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered LDL lowering → near-maximal → CV benefit, consistent with chronology and benefit magnitude.
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.	🟢	Three distinct aspects; not applicable.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All cells meaningful and ER-derived.
11.5	If the ER does not provide any information on time to effect, the section is removed completely from the `Protocol Panel`	🟢	ER provides time-to-effect; section retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER `Expected Benefits` section	🟢	Derived from ER lines 154-198.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four 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 key facts only.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheticals carried through.
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.	🟢	All sub-sections have ER content; not applicable.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER `Potential Risks & Side Effects` section	🟢	Derived from ER lines 214-258.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four 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; “⚠️ Conflicted” qualifiers stripped.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheticals carried through.
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.	🟢	All sub-sections have ER content; not applicable.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER `Monitoring` section	🟢	Derived from ER Monitoring Protocol (lines 379-389).
14.2	All measurable/quantifiable biomarkers from the `Monitoring` section are listed	🟢	LDL-C, apoB, Lp(a), non-HDL, fasting glucose/HbA1c — all five ER biomarkers present.
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.	🟢	“Lipid recheck ~4–8 weeks … then every 6–12 months once stable” (line 651).

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER `Monitoring` section	🟢	Derived from ER qualitative markers (lines 391-396).
15.2	All subjective/qualitative biomarkers from the `Monitoring` section are listed	🟢	All four ER qualitative markers present (lines 660-669).

Issues 30/06/2026 04:31

Pass rate 100.00%. No issues found.