Audit: QRS - Cordiart for Health & Longevity
Audit conducted on 28/06/2026 04:15 using AI4L / Opus 4.8
Summary
| Items | Count |
|---|---|
| Total | 91 |
| Passed | 87 |
| Failed | 0 |
| N/A | 4 |
| 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 QRS content traces to ER (Conclusion, Protocol, Benefits, Risks, Interactions, 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. | 🟢 | Cautious framing preserved (e.g., “inconsistent”, “theoretical” bleeding risk in Speculative tier). |
| 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”). | 🟢 | No strengthening/softening; tiers and qualifiers match 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/Interactions drawn from ER “Key Interactions & Contraindications”; benefits/risks from their own ER sections. |
| 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, NCTs, study/expert names introduced; only drug/supplement names that appear in the 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. | 🟢 | Objective, data-driven tone consistent with ER. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Met. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Presents evidence, not prescriptions. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No directive medical advice; disclaimer present. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | Information-presenting phrasing throughout. |
| 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 used; technical terms minimal and contextual. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Compact cells and lists. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | No second-person 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 fits risk-aware optimizers. |
| 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. | 🟢 | Protocol/monitoring detail assumes engaged audience. |
| 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 framing. |
| 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. | 🟢 | Weighting reflects optimization audience. |
| 2.14 | The document’s own voice frames usage in longevity terms, not “anti-aging”. Proper names that contain “anti-aging” are quoted verbatim. | 🟢 | No “anti-aging” wording; “healthy aging” / longevity framing used. |
| 2.15 | The document’s own voice uses formal clinical and scientific terminology, not colloquial or consumer-grade language. Direct quotes from sources are exempt. | 🟢 | Plain terms (“blood fats”, “blood sugar”) appear only in the deliberately plain-language At-A-Glance; elsewhere terminology is appropriate. |
3. Template Integrity
| # | Description | Result | Comments |
|---|---|---|---|
| 3.1 | The following labels and headings on the QRS are fixed and not modified: card/section headings (“Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”); gate headings (“Contraindications”, “Key Interactions”); tier labels (“High”, “Medium”, “Low”, “Speculative”); Monitoring column headers (“Marker”, “Target”, “Why”). | 🟢 | All fixed headings/labels intact. |
| 3.2 | All “…” from the [qrs_template] are present in the QRS. | 🟢 | Full set of data-qrs-var spans present, including hidden ones. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | Unaddressed spans untouched. |
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” | 🟢 | Empty benefit/risk tiers use display:none, not phantom text; no mis-stated empty states. |
| 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/monitoring labels align with ER. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Labels faithful. |
| 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 body. |
| 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 one 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. | 🟢 | Metadata comment is first element (lines 2-14). |
| 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 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. | 🟢 | 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; only duration quoted (contains colon). |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | er_filename: cordiart_2026-0628-0221_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]” | 🟢 | qrs_prompt_version: 26.5.18 |
| 5.7 | Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” | 🟢 | qrs_creation_date: 2026-0628-0221 |
| 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. | 🟢 | “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 |
| 5.11 | The full name of the AI consists of the nickname and the model version number and no additional qualifier | 🟢 | “Opus 4.8” — nickname + version. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | qrs_filename: cordiart_2026-0628-0221_Opus_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. | 🟢 | Confirmed clean. |
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”. The [canonical_topic] is HTML-entity-encoded as needed. | 🟢 | “Cordiart 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. | 🟢 | “Cordiart for Health & Longevity”. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | “06/28/2026” from 2026-0628. |
| 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 clean. |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Distills Conclusion (line 418): lipids/inflammation signal, inconsistent BP/glucose/vessel, reassuring safety, surrogate-marker caveat. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | Exactly 60 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Each clause maps to a Conclusion passage. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | “blood fats”, “blood sugar”, “vessel widening” — plain language; no acronyms. |
| 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 numeric effect sizes. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Drawn from ER line 290 “Populations who should avoid or use caution”. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | Three contraindication populations carried. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Each is an <li>. |
| 8.4 | Items are as concise as possible. No trailing explanations, elaborations, mechanistic rationale, attributions, citations, study details. No content after an em-dash, en-dash, or hyphen-dash. Just the key fact. | 🟢 | Concise; no trailing-dash clauses. |
| 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. | 🟢 | “(insufficient safety data)” and “within roughly 2 weeks” preserved. |
| 8.6 | When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase, normalize to a plain comma-separated list. | 🟢 | No ranking notation present; items are plain lists. |
| 8.7 | If no [stop_items] are present the section is left empty | N/A | Contraindications exist; condition not met. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Drawn from ER lines 278-288. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | Six interaction bullets carried; the “populations to avoid” bullet correctly excluded (it is in Contraindications). |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Each is an <li>. |
| 9.4 | Items are as concise as possible. No trailing explanations, elaborations, mechanistic rationale, attributions, citations, study details. No content after an em-dash, en-dash, or hyphen-dash. Just the key fact. | 🟢 | Trailing “caution/monitor/mitigation” clauses stripped; just drug classes + examples. |
| 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 drug lists preserved (warfarin/apixaban/etc.; lisinopril/amlodipine; omega-3/garlic/Ginkgo/etc.). |
| 9.6 | When the ER uses ranking notation inside parens (e.g., “>” for severity ordering), normalize to a plain comma-separated list. | 🟢 | No ranking notation; plain comma lists. |
| 9.7 | If no [caution_items] are present the section is left empty | N/A | Interactions exist; condition not met. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Protocol section |
🟢 | Derived from ER Therapeutic Protocol (lines 308-329). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Standard dose, form selection (2S micronized), best time of day. |
| 10.3 | If less than three distinct actionable implementation aspects are mentioned, unused sets are left empty and made invisible. | N/A | Three aspects exist; all three sets 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 cells populated from ER Protocol. |
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 | 🟢 | ER provides two distinct time-to-effect aspects (lipids 12+ weeks; vascular/inflammation ~3 weeks); both used, third correctly hidden. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Both relate to Medium-tier benefits; ordering acceptable. |
| 11.3 | If less than three distinct time-to-effect aspects are mentioned, unused sets are left empty and made invisible, not filled with placeholder text. | 🟢 | Third set is empty with display:none. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | Both used sets derived from ER line 357. |
| 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 provides time-to-effect data; condition not met. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | Derived from ER Expected Benefits (lines 155-204). |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four present (high hidden). |
| 12.3 | Items are as concise as possible. No explanations, elaborations, effect sizes, qualifiers, attributions, citations, study details, mechanistic explanations. Just the key fact. | 🟢 | Concise heading-level facts only. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheticals; “Conflicted” marker dropped appropriately. |
| 12.5 | If no items of a specific sub-section are present the respective is set to “display=none”, not filled with empty-state phrasing. | 🟢 | benefits_high set to display:none (no High benefits in ER). |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | Derived from ER lines 224-256. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four present (high/medium hidden). |
| 13.3 | Items are as concise as possible. No explanations, elaborations, effect sizes, qualifiers, attributions, citations, study details, mechanistic explanations. Just the key fact. | 🟢 | Concise heading-level facts only. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheticals carried. |
| 13.5 | If no items of a specific sub-section are present the respective is set to “display=none”, not filled with empty-state phrasing. | 🟢 | risks_high and risks_medium set to display:none (no such ER tiers). |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Derived from ER Monitoring Protocol & Defining Success (lines 377-396). |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All six ER table biomarkers listed (LDL, triglycerides, total cholesterol, hs-CRP, fasting glucose, BP). |
| 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. |
🟢 | “Baseline, then at roughly 12 weeks, then every 6–12 months.” per ER line 381. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Derived from ER qualitative markers (lines 394-396). |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All three qualitative markers listed verbatim. |
Issues 28/06/2026 04:15
Pass rate 100.00%. No issues found.
Issues 28/06/2026 04:09
- 11.1 / 11.3 — Duration of Use is not a time-to-effect aspect: The ER (Practical Considerations, line 357) provides only two time-to-effect aspects — lipids (~12 weeks) and vascular/inflammation markers (~3 weeks). The third Time-to-Effect slot is filled with “Duration of Use / Ongoing”, a duration/discontinuation concept rather than a time-to-effect aspect; per 11.3 the unused third set should be left empty and made invisible.
Fixes 28/06/2026 04:09
- 11.1 / 11.3 — Empty third time-to-effect slot: Cleared the third Time-to-Effect set (time_3_label “Duration of Use”, time_3_value “Ongoing”, time_3_sub) and set its
.pcelltodisplay:none, since the ER provides only two genuine time-to-effect aspects (lipids and vascular/inflammation markers).
Issues 28/06/2026 04:05
- 7.4 — Technical term in At-A-Glance: The At-A-Glance phrase “the flavonoid hesperidin” (line 433) uses “flavonoid”, a chemical-classification term a non-specialist would not use unprompted or define precisely; a plain-language descriptor is required.
Fixes 28/06/2026 04:05
- 7.4 — Plain-language At-A-Glance term: Replaced “of the flavonoid hesperidin” with “of hesperidin, a natural plant compound from oranges” so the summary no longer relies on the chemical-classification term “flavonoid” (kept within the 60-word limit).
Issues 28/06/2026 04:02
- 12.3 / 12.4 — Qualifier not stripped in benefits: benefits_low (line 528) retains the parenthetical qualifier “(conflicted)” on “Improved endothelial function”; per 12.3 (“no qualifiers”) and 12.4 (“Parenthetical content … is stripped, NOT preserved”) it must be removed, leaving just the benefit name.
Fixes 28/06/2026 04:02
- 12.3 / 12.4 — Qualifier stripped from benefits: Removed the parenthetical qualifier “(conflicted)” from “Improved endothelial function” in benefits_low, leaving just the benefit name.