Audit: QRS - Betaine for Health & Longevity

Audit conducted on 20/07/2026 04:16 using AI4L / Opus 4.8

Iterations

Summary

Items Count
Total 91
Passed 83
Failed 0
N/A 8
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 doses, biomarker targets, benefit/risk items, and cadence trace to the ER (Protocol, Monitoring, Benefits, Risks sections).
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 and “if they occur”/”where present” hedges mirror the ER.
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 detected.
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 and interactions both drawn from the ER Key Interactions & Contraindications section without cross-relabeling.
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. 🟢 The QRS carries no PMIDs, NCTs, expert names, or brand names.
1.6 The QRS does not introduce new attributions. 🟢 No attributions introduced.

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 register consistent with the 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 directives.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Footer disclaimer present; body avoids prescriptive advice.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Content is presented, not recommended.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person address.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain language throughout.
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” phrasing.
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 matches 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. 🟢 Monitoring/protocol detail consistent with this 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 written for the general population.
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. 🟢 Benefit/risk weighting reflects the target 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. 🟢 Uses “longevity”; no “anti-aging”.
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. 🟢 Formal terminology; “stomach upset” is pulled verbatim from the ER qualitative-marker list.

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”); Table column headers in Monitoring (“Marker”, “Target”, “Why”). 🟢 All fixed labels present and unmodified.
3.2 All “” from the [qrs_template] are present in the the QRS. 🟢 All expected variable spans present and populated.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 No unexpected span modifications.

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. N/A No source ER section is empty; every populated section had content.
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 match ER wording.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Labels preserved.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emojis; ER “⚠️ Conflicted” markers correctly stripped.
4.5 The QRS is designed to render on one A4 page. Any section with more ER content than the per-section budget is condensed, 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 the 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 not parsed as YAML. 🟢 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. 🟢 Enclosed in an HTML comment; not rendered.
5.4 All frontmatter values are trimmed: no leading/trailing whitespace, no surrounding quotes unless the value requires YAML quoting. 🟢 Only duration is quoted (contains a colon).
5.5 The filename of the source ER is stated as “er_filename: [er_filename]”. 🟢 er_filename: betaine_2026-0720-0143_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.7.02.
5.7 Creation date and time is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]”. 🟢 qrs_creation_date: 2026-0720-0409.
5.8 The nickname of the AI 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”.
5.10 The full name of the AI is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]”. 🟢 qrs_creator_ai_fullname: Opus 4.8.
5.11 The full name consists of the nickname and the model version number and no additional qualifier. 🟢 “Opus 4.8”.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]”. 🟢 qrs_filename: betaine_2026-0720-0143_Opus_QRS.html.
5.13 All frontmatter values are trimmed: no leading/trailing whitespace, no surrounding quotes unless required. 🟢 Values clean and consistent.

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. 🟢 “Betaine 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. 🟢 “Betaine for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]. 🟢 2026-0720 → 07/20/2026.
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 carries only title and subline; no extras.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section. 🟢 Distills the two-function framing, homocysteine benefit, mixed strength/body-composition signal, and cholesterol trade-off from the Conclusion.
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. 🟢 Each clause maps to a Conclusion passage (lines 432–434).
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge; uses plain-language terms instead. 🟢 Uses “methyl tags”, “blood marker”, “cholesterol”; 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 statistics.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section. 🟢 Sourced from the ER “Populations who should avoid or use caution” bullet (line 293).
8.2 [stop_items] represent the Contraindications from the ER. 🟢 Pregnancy/breastfeeding, high LDL/FH/ASCVD, kidney impairment, trimethylaminuria all captured.
8.3 Individual [stop_items] are formatted as <li></li>. 🟢 Four <li> items.
8.4 Items are as concise as possible. No trailing explanations, elaborations, rationale, attributions, citations, study details, or content after a dash. 🟢 No trailing clauses.
8.5 Parenthetical qualifiers from the ER bullet — time windows, severity classes, threshold values, clinical staging — ARE preserved, kept concise. 🟢 “>160 mg/dL” threshold and “(high doses)” qualifier preserved.
8.6 When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase, normalize items to a plain comma-separated list. 🟢 No ambiguous ranking notation; “>160 mg/dL” is a threshold, retained correctly.
8.7 If no [stop_items] are present the section is left empty. N/A Stop items are present.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section. 🟢 Drawn from the ER interaction bullets (lines 281–291).
9.2 [caution_items] represent the Key Interactions from the ER, excluding any already listed as Contraindications. 🟢 Six interactions carried; none overlap the contraindications.
9.3 Individual [caution_items] are formatted as <li></li>. 🟢 Six <li> items.
9.4 Items are as concise as possible. No trailing explanations, elaborations, rationale, attributions, citations, study details, or content after a dash. 🟢 Labels only; severity/consequence text dropped.
9.5 Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved, kept concise. 🟢 Example-drug lists preserved (folate/B6/B12; NR/NMN; methotrexate/trimethoprim/sulfasalazine; statins/ezetimibe).
9.6 When the ER uses ranking notation inside parens that depends on an explanatory phrase, normalize to a plain comma-separated list. 🟢 No ranking notation present; example lists rendered as plain comma-separated lists.
9.7 If no [caution_items] are present the section is left empty. N/A Caution items are present.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section. 🟢 Dose/frequency/timing sourced from the ER Therapeutic Protocol (lines 315–327).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section. 🟢 Dose, Frequency, Timing.
10.3 If less than three distinct actionable aspects are mentioned, the unused sets are left empty and invisible. N/A Three distinct aspects are present.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 All three sets populated with ER-derived content.

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. 🟢 Homocysteine, Performance/body composition, Liver effects (ER line 366).
11.2 The sets are picked and ordered by the magnitude of the related benefit. 🟢 High → Medium → Low benefit ordering.
11.3 If less than three distinct time-to-effect aspects are mentioned, the unused sets are left empty and invisible. N/A Three distinct aspects are present.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 All three sets populated.
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 provides time-to-effect information.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section. 🟢 Tiers mirror the ER Expected Benefits headings.
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, elaborations, effect sizes, qualifiers, attributions, citations, study details, or mechanistic explanations. 🟢 Bare benefit names only.
12.4 Parenthetical content — effect sizes, sample notes, mechanistic hints, example studies — is stripped, NOT preserved. 🟢 No parentheticals carried; “⚠️ Conflicted” markers removed.
12.5 If no items of a specific sub-section are present the respective span is set to display=none, not filled with empty-state phrasing. N/A All four benefit tiers contain items.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section. 🟢 Tiers mirror the ER Risks headings.
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, elaborations, effect sizes, qualifiers, attributions, citations, study details, or mechanistic explanations. 🟢 Bare risk names only.
13.4 Parenthetical content — frequencies, severity grades, sample notes, mechanistic hints, example studies — is stripped, NOT preserved. 🟢 “(Fishy, Trimethylamine)” and “(TMAO)” parentheticals stripped.
13.5 If no items of a specific sub-section are present the respective span is set to display=none, not filled with empty-state phrasing. N/A All four risk tiers contain items.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section. 🟢 Sourced from ER Monitoring Protocol biomarker table (lines 398–405).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed. 🟢 All six biomarkers (homocysteine, LDL, total cholesterol, B12 & folate, methionine, ALT) present.
14.3 [monitoring_cadence] is populated with the monitoring cadence/frequency derived from the ER Monitoring section. 🟢 Cadence matches ER line 392.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section. 🟢 Sourced from the ER qualitative markers (lines 409–412).
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed. 🟢 All four qualitative markers present.

Issues 20/07/2026 04:16

Pass rate 100.00%. No issues found.