Audit: QRS - Cardiogen for Health & Longevity

Audit conducted on 01/09/2026 03:45 using AI4L / Opus 5

Iterations

Summary

Items	Count
Total	93
Passed	86
Failed	0
N/A	7
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 cells, gate items, tier lists, markers and cadence trace to ER lines 323-345, 290-299, 274-288, 150-176, 210-254, 408-430.
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.	🟢	“No trial supports this dose, frequency or duration”, “Unknown”, “No measured half-life has been published” carried verbatim.
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 remain absolute; every benefit stays at Speculative as in the ER.
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 come only from “Populations who should avoid Cardiogen”; interactions only from the interaction bullets; no modifying factors migrated.
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, citations or NCT ids present; named agents (warfarin, apixaban, Epitalon, Cartalax, etc.) all appear in ER lines 274-288.
1.6	The QRS does not introduce new attributions.	🟢	No attributions of any kind in the QRS.

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.	🟢	Same measured, sceptical register as the ER.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Presents thresholds and evidence tiers that let the reader decide; no hedging or moralising.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	States what is circulating and what supports it; issues no instructions.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperatives directed at a reader; the one stopping statement is carried verbatim from ER line 427.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Descriptive throughout (“Circulating protocols…”, “No trial supports…”).
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere in the file.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Jargon limited to biomarker names and decision-gate staging, where it is load-bearing; explanatory glosses used elsewhere (“cell-ageing inflammation”, “heart wall stretch”).
2.8	Information is presented in a concise and very compact manner	🟢	ER bullets reduced to single clauses; benefit and risk tiers collapsed to one semicolon-separated line each.
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.	🟢	Monitoring panel, sourcing-driven risk framing and dose detail all assume an engaged self-directed 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.	🟢	A 10-marker panel with baseline, 4-week and end-of-course draws presumes that willingness.
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.	🟢	Optimal functional ranges are used rather than conventional lab cutoffs.
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 foregrounds the supply-channel harms, the decision-relevant point for a self-sourcing reader.
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” does not appear; the page title uses “Health & Longevity”.
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.	🟢	“subcutaneously”, “myocardial infarction”, “injection-site”, “hypersensitivity” used throughout; no colloquialisms.

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 headings match the template byte-for-byte (lines 440, 477, 519, 533, 548, 568, 583, 587-589, 713).
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	Span-name diff against the template shows only the expected expansion of marker_#* into marker_1..10* and qualitative_item_# into 1..6.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The three website="…" spans and all CSS are untouched; structural diff against the template shows no other change.

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 ER section feeding a rendered QRS field is empty; the unpopulated benefit and risk tiers are governed by items 12.5 and 13.5, which mandate display:none instead of empty-state phrasing.
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.	🟢	“Standard circulating protocol”, “Intensive variant”, “Competing oral approach”, “Time to effect”, “Half-life and its consequence” all verbatim from ER lines 323, 325, 327, 333, 380.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Monitoring row labels match the ER biomarker column exactly.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji in the file; tiers rendered as bold text labels with CSS colour.
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.	🟢	Every section is condensed against its ER source rather than transcribed; no second-page markup or overflow container was introduced.

---

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 blank-template comment follows at 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 “—” at line 3, closing at line 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; no value repeated in the body.
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: "00:02" is quoted, and it contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: cardiogen_2026-0901-0205_Opus_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]”	🟢	Line 5: qrs_prompt_version: 26.7.02, matching the QRS.md version badge.
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-0901-0342.
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” is a single word with no version or 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, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the file’s own 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 or unnecessary quoting.

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., & for &)	🟢	Line 22: “Cardiogen 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 &)	🟢	Line 417: “Cardiogen for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “09/01/2026” from qrs_creation_date 2026-0901-0342.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “Opus 5”.
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 holds only the title and the template subline; the ER’s “Also known as” line was not carried over.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Line 433 condenses ER Conclusion paragraphs 1-2 (lines 452-454) into four decision-relevant sentences.
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.	🟢	Four claims map to ER lines 452 (“four-amino-acid compound…”, “small and one-sided”, “none of it involves people”) and 454 (“harms belong to the channel”).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “four-amino-acid compound”, “laboratory chemical”, “unlicensed supply channel” are plain-language.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial named or dated.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numbers of any kind.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	Drawn from “Populations who should avoid Cardiogen”, ER lines 290-299.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All eight ER bullets present, in ER order (lines 536-543).
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Eight <li> elements inside the span.
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.	🟢	Rationale clauses stripped (“given proliferative signalling and reduced p53”, “which both raises inoculation risk…”, “the preservative in bacteriostatic water”); no dash-trailing clauses remain.
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).	🟢	“within the past 5 years”, “below 50 × 10⁹/L”, “above 3.5”, “Class III-IV”, “within 90 days”, “Child-Pugh Class C”, “below 30 mL/min/1.73 m²” all retained.
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 contraindication bullets use no ranking notation; thresholds are written out as “below”/”above”.
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 names eight such populations and the section is correspondingly populated.
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	🟢	Drawn from the interaction bullets at ER lines 274-288.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All eight interaction bullets present; no overlap with the contraindication list.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Eight <li> elements inside the span.
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.	🟢	Caution/Monitor verdicts, rationale sentences and every “Mitigation:” clause stripped; only the bolded label survives.
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 eight drug/supplement example lists retained; only the inline glosses inside the cardiovascular-therapy parenthesis were trimmed for length, with metoprolol and lisinopril kept.
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 interaction parentheses are plain comma-separated example lists with no ranking notation.
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 names eight interactions and the section is correspondingly populated.
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 trace to ER Therapeutic Protocol lines 323, 325, 327.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Standard dose/interval, intensive variant and the competing oral route are the three dosing decisions; the remaining ER bullets are qualifiers rather than regimens.
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 aspects and all three sets are used.
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 populated from ER text (lines 444-473).

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	🟢	The ER contains only two time-to-effect aspects — “Time to effect” (line 380) and “Half-life and its consequence” (line 333); both are used, and course-duration/cycling detail is a protocol aspect already carried in the action cells.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Onset of any claimed effect precedes the pharmacokinetic consequence; no benefit carries a magnitude in the ER to order by.
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.	🟢	The third pcell carries style="display: none" and all three time_3 spans are empty (lines 503-513).
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	Six spans populated verbatim from ER lines 380 and 333.
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 does provide time-to-effect information, so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All seven entries are the ER’s Speculative sub-headings (lines 150-176).
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present at lines 521-526.
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.	🟢	Each entry reduced to its ER heading; no citations, fold-changes or study descriptions carried over.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	“(Patent-Only Claim)” stripped from the post-infarction entry.
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.	🟢	benefits_high, benefits_medium and benefits_low carry style="display: none" and are empty.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	Four Low and five Speculative entries match the ER sub-headings at lines 210-254.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present at lines 570-577.
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.	🟢	Every “Magnitude:” block and citation dropped; entries reduced to their ER headings.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content remains in either tier.
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.	🟢	risks_high and risks_medium carry style="display: none" and are empty.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Table and cadence taken from ER Monitoring Protocol & Defining Success (lines 408-421).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All ten ER table rows are present with matching targets and rationale.
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.	🟢	Line 707 condenses ER line 408: baseline, 4 weeks, end of course, then every 6-12 months, plus unscheduled panel after a reaction.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Taken from the ER’s “Qualitative markers worth recording alongside the panel” list (lines 425-430).
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All six ER qualitative markers present at lines 716-732.

Issues 01/09/2026 03:45

Pass rate 100.00%. No issues found.