Audit: QRS - L-Carnitine for Health & Longevity

Audit conducted on 22/09/2026 18:00 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 94
Passed 84
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. 🟢 Spot-checked every populated span against the ER: at-a-glance vs ER Conclusion/Practical Considerations, protocol vs ER lines 408-420, time-to-effect vs lines 416/443/461/487, benefits/risks vs the ER tier headings, gates vs lines 366-386, monitoring table vs lines 491-500, qualitative vs lines 504-510. All literally supported.
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 empty-state or hedged ER phrasing is reworded; the conflicted-evidence framing stays encoded by tier per 12.3/13.3.
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 claim strengthened or softened; e.g. “use carnitine only with clinical oversight” (ER line 386) becomes “clinical oversight only”.
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. 🟢 Contraindication vs interaction split follows the ER’s own bullets; no Benefit-/Risk-Modifying Factor is re-surfaced as a gate.
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. 🟢 Brand/drug names present (acenocoumarol, levothyroxine, liothyronine, Depakote, pivmecillinam) all appear in ER lines 366-372 for the same facts. No PMIDs or NCT IDs.
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. 🟢 Matches the ER’s measured, benefit-versus-TMAO-tension framing.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Expert, objective, data-anchored; targets and cadences give the reader actionable anchors.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Presents evidence and protocol ranges as observed practice, not as orders.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Gate wording mirrors the ER (“clinical oversight only”, “physician-guided use with monitoring”) without issuing clinical instruction.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Descriptive verbs throughout (“divided across meals”, “often taken with”, “is standard”).
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person address anywhere in the sheet.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain language; technical terms only where they are the marker names in the Monitoring table.
2.8 Information is presented in a concise and very compact manner 🟢 Every section reduced to labels, values and short qualifiers.
2.9 It DOES NOT address the reader directly 🟢 Confirmed - no “you”/”your” in any span.
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. 🟢 Longevity framing throughout (Plasma TMAO called the “central longevity safety marker”; functional rather than conventional targets).
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. 🟢 Presents multi-month loading protocols, split dosing, and a ten-marker panel without hedging on 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. 🟢 Optimal functional ranges (fasting glucose 70-85 mg/dL, HbA1c < 5.4%) are well beyond general-population 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. 🟢 Modest effect sizes and the TMAO safety question are both surfaced, matching the ER’s audience weighting.
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. 🟢 No occurrence of “anti-aging” anywhere in the sheet.
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)”; “oral” / “administered orally” not “taken by mouth” / “given by mouth”; “injection” not “shot”; “adverse event” not “bad reaction”). This holds on EVERY surface, including the QRS lede — the stricter plain-language bar (see 2.7) does not license lay phrasing for route of administration. Direct quotes from sources are exempt. 🟢 No colloquial route-of-administration or consumer-grade wording; “dietary supplement”, “heart attack” and “hardening of the arteries” all track the ER’s own register.

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 verified: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”, “Contraindications”, “Key Interactions”, High/Medium/Low/Speculative, Marker/Target/Why.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All 38 template variables present; the repeatable marker_#* and qualitative_item# spans are expanded to marker_1..10 and qualitative_item_1..4.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Source diff against the template shows changes confined to the data-qrs-var payloads; CSS, structure, website= spans, comments and footer are 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” N/A ER sections mapped into the QRS all carry content; no empty-state phrasing applies.
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. 🟢 ER bold labels reproduced verbatim, e.g. “Contraindicated forms:”, “Anticoagulants — warfarin and similar (e.g., acenocoumarol):”, “General L-carnitine (metabolic, weight, fatigue):”.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 No invented or abbreviated labels; benefit/risk items reuse the ER’s own sub-headings.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No 🟩/🟥/🟨 or any other emoji in the HTML source.
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 to its minimum permitted form - magnitudes, mechanisms and rationale stripped - and no content spills past the single-sheet structure of the template.

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 opens on line 2, immediately after <!doctype html>, before the template comment and <html>.
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 opens at line 3 and closes at line 13; the preamble text sits before the opening ---.
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 element on the sheet surfaces these values.
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. 🟢 All values trimmed; only duration: "00:04" is quoted, which is required because the value contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: l_carnitine_2026-0804-0344_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.9.22 matches 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) 🟢 qrs_creation_date: 2026-0922-1748 is in YYYY-MMDD-HHMM form.
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) 🟢 Single word, 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]” 🟢 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) 🟢 Nickname plus version number only, no qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename: l_carnitine_2026-0804-0344_Opus_QRS.html matches the file 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: no stray whitespace and no 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., &amp; for &) 🟢 <title>L-Carnitine for Health &amp; Longevity - Quick Reference Sheet</title> matches canonical_topic with & entity-encoded.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 L-Carnitine for Health &amp; Longevity, entity-encoded.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 09/22/2026 is qrs_creation_date 2026-0922-1748 in MM/DD/YYYY form.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Opus 5 equals 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. 🟢 Header carries only the title and the template subline; no badge, AKA line, version stamp or variant marker.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] opens by saying what the intervention is — its kind (e.g., dietary supplement, prescription medication, peptide, plant, procedure, practice) — and what it is used for, in plain language, before any verdict on the evidence 🟢 Opens “L-carnitine, a natural compound sold as a dietary supplement, helps cells turn fat into energy” - kind and purpose stated before any verdict.
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Compresses the ER Conclusion (lines 530-532) into the benefit hierarchy plus the TMAO caveat.
7.3 [at_a_glance] is no longer than 70 words 🟢 68 words.
7.4 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each clause traces to a distinct ER passage: line 465 (supplement status), line 530 (mechanism, forms, deficiency, modest gains), line 532 (TMAO byproduct).
7.5 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms; “hardening of the arteries” is used in place of atherosclerosis and “a real shortage” in place of deficiency.
7.6 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No study names, years, or sample sizes.
7.7 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No effect sizes, odds ratios, or statistics.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Both items come from the ER Key Interactions & Contraindications section (lines 384, 386).
8.2 [stop_items] represent the Contraindications from the ER 🟢 Captures exactly the two ER bullets stating avoidance or clinical-oversight-only use.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Two <li> elements inside the [stop_items] 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. 🟢 Mechanistic rationale dropped (ER’s “D-carnitine competitively inhibits the natural L-form…”); no trailing dash 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). 🟢 Threshold and staging preserved: “eGFR below 30 mL/min/1.73 m², stage 4-5 or dialysis-dependent; established atherosclerotic cardiovascular disease”.
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 uses no ranking notation inside parentheses in its contraindication bullets.
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. 🟢 Section is correctly populated - the ER names both an absolute contraindication and an oversight-only population.
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 (two contraindication items present).

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All eight items map to ER bullets at lines 366-382.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Covers every ER interaction bullet except the two already routed to Contraindications and the “Over-the-counter agents” bullet, which states no major interactions are established.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Eight <li> elements inside the [caution_items] 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. 🟢 Reduced to the key fact; no mechanism, monitoring rationale, or trailing dash 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 (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely). 🟢 Named example drugs preserved: acenocoumarol, levothyroxine/liothyronine, Depakote, pivmecillinam.
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 uses no ranking notation inside parentheses in its interaction bullets.
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. 🟢 Section is correctly populated - the ER names multiple interactions.
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 (eight interaction items present).

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 Derived from the ER Therapeutic Protocol section (lines 406-430).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 General L-carnitine, ALCAR for brain/mood, and LCLT for exercise recovery are the three aspects most relevant to the longevity audience.
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 Therapeutic Protocol lists far more than three actionable aspects; 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 action spans carry ER-derived content (labels verbatim; values 500-2,000 mg/day, 500-2,000 mg/day, 1-2 g/day; subs from lines 408-420).

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 🟢 Metabolic/fatigue, muscle carnitine loading and cognitive effects are the three aspects the ER names (line 461).
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered High/Medium (body composition, glycemic, fatigue) → Medium (exercise recovery) → Low (cognition).
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 names three distinct time-to-effect aspects; all three sets are used.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 All nine time spans populated from ER lines 416, 443, 461 and 487.
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 information (Practical Considerations, line 461).

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All tiers map to the ER Expected Benefits sub-headings.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four benefit spans present and 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. 🟢 Items are the bare ER sub-headings; magnitudes, mechanisms and population qualifiers all dropped.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content carried over; “lipoprotein(a)” is the marker name, not a parenthetical.
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 carry items in the ER.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All tiers map to the ER Potential Risks & Side Effects sub-headings.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four risk spans present and 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. 🟢 Bare sub-headings only; frequencies (“Uncommon below 2 g/day”) and mechanisms dropped.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content carried over.
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 carry 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 section (lines 483-500).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All ten ER biomarkers listed with names, optimal functional ranges and rationale verbatim.
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 captures baseline, 8-12 week recheck, 6-12 month maintenance, plus the INR and thyroid-lab exceptions (ER line 487) and the fasting note (line 485).

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Derived from the qualitative markers of success in the same ER section (lines 502-510).
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All four qualitative markers listed verbatim.

Issues 22/09/2026 18:00

Pass rate 100.00%. No issues found.

Issues 22/09/2026 17:53

  1. 4.2 — Anticoagulant label not verbatim: The Key Interactions label at QRS line 591 reads “Anticoagulants, warfarin and similar (e.g., acenocoumarol):” while the ER bold label (ER line 366) is “Anticoagulants — warfarin and similar (e.g., acenocoumarol):”; the em-dash was silently replaced with a comma.

Fixes 22/09/2026 17:53

  1. 4.2 — Anticoagulant label not verbatim: Restored the ER’s bold label in the Key Interactions gate, changing “Anticoagulants, warfarin and similar (e.g., acenocoumarol):” back to “Anticoagulants — warfarin and similar (e.g., acenocoumarol):”.