Audit: QRS - Sarcosine for Health & Longevity

Audit conducted on 14/08/2026 01:38 using AI4L / Opus 5

Summary

Items	Count
Total	93
Passed	85
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.	🟢	Every numeric value traced to the ER: 2 g daily, 30 mg/kg, half-life ~1 h, week 1/2/4, 12 weeks, PSA 4.0 ng/mL, eGFR 30 and 90 mL/min/1.73 m², ALT 25/20 U/L, homocysteine 9 µmol/L, free PSA 25%, 3/6/6–12-month cadence, “first three weeks”.
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.	🟢	Hedges carried verbatim: “no trial has compared timing directly” (line 472), “inference, not tested practice” (line 486), “No established target exists” (line 712).
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”).	🟢	The ER’s “⚠️ Conflicted” flags are retained as “(conflicted)” on cognition (line 553) and prostate cancer invasion (line 611); contraindications keep their absolute framing.
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 from the ER’s “Populations who should avoid Sarcosine” list; interactions from the ER’s interaction bullets; benefit and risk tiers preserved unchanged.
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 only named source is “Examine” (line 457), which the ER attaches to the same 30 mg/kg fact (ER line 320). No PMIDs, NCT IDs, or author names.
1.6	The QRS does not introduce new attributions.	🟢	No attribution appears that is not already in the ER.

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, evidence-first register; most cells are near-verbatim ER phrasing.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Presents thresholds and time-to-effect as usable reference points while stating the limits of the evidence.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Statements describe what trials did rather than instructing (“Standard in the trials”, “All published trials used once-daily dosing”).
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No prescriptive verbs in the document’s own voice; the footer disclaimer is fixed template text.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No “should”, “recommended”, or “advised” anywhere in the populated variables.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronoun anywhere in the document.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms appear only where the ER uses them and where the marker itself requires them (PSA, eGFR, ALT).
2.8	Information is presented in a concise and very compact manner	🟢	Sub-lines run one to two sentences; gate items are single clauses.
2.9	It DOES NOT address the reader directly	🟢	Confirmed; third-person throughout, e.g. “the individual’s own baseline” (line 713).
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 targets are the ER’s optimal functional ranges, not conventional laboratory cut-offs.
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 six-marker baseline panel with repeat testing at 3, 6, and 6–12 months assumes 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.	🟢	No simplification to general-population framing; assumes laboratory access and self-tracking.
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 states plainly that longevity evidence is cells and animals only and that nothing beyond six months has been observed — the decisive point for this audience.
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.	🟢	“Longevity” is used in the title and At-A-Glance; “anti-aging” does not appear.
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.	🟢	“Adverse effects”, “administration”, “renal impairment”, “lactation” — no consumer-grade substitutions.

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 verified verbatim: lines 446, 493, 543, 605, 626, 736, 570, 586, 630–632, and the four tier labels in both the Benefits and Risks cards.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	Every variable named anywhere in this checklist is present: page_title, header_topic, header_subline_date, header_subline_model, at_a_glance, action_1–3 label/value/sub, time_1–3 label/value/sub, stop_items, caution_items, benefits and risks tiers, marker_1–6 name/target/why, monitoring_cadence, qualitative_item_1–5.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The non-variable template spans `website="evidence_review"` (line 423), `website="audit"` (line 426), and `website="full_review"` (line 440) are untouched and empty as shipped.

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 the QRS is empty; every benefit tier, risk tier, gate, and monitoring row has source 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.	🟢	“Standard dose”, “Time of day”, and “Split versus single dose” match the ER’s bold labels exactly (ER lines 320, 328, 330); monitoring row labels match the ER table’s biomarker names.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	No invented labels; “eGFR” and “ALT” are the ER’s own forms from its monitoring table.
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; the ER’s 🟩/🟥/🟨 tier markers and ⚠️ flags are conveyed by the bold tier labels and CSS palettes.
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.	🟢	Six gate items, seven interaction items, four benefit and four risk lines, six monitoring rows, and five qualitative items at 8–11 pt fit the A4 budget; no section carries ER prose wholesale.

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.	🟢	Single comment at lines 2–14, immediately after `<!doctype html>` on line 1.
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; the caption text on line 2 precedes the opening delimiter.
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; none of its values are repeated in the header, body, or footer except the model name, which is a template subline variable.
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:03"` is quoted, and it contains a colon, so quoting is required.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: `er_filename: sarcosine_2026-0814-0001_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 version badge of QRS.md.
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-0814-0129`.
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” — 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]”	🟢	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 number, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 states `sarcosine_2026-0814-0001_Opus_QRS.html`, matching 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 across all nine metadata keys; no stray whitespace or unnecessary quoting.

#	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: “Sarcosine for Health & Longevity - Quick Reference Sheet”; canonical_topic matches the ER frontmatter and the ampersand is entity-encoded.
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: “Sarcosine for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “08/14/2026”, the correct reformatting of 2026-0814-0129.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “Opus 5”, matching the frontmatter.
6.5	No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker.	🟢	The header carries only the title and the fixed template subline; the ER’s “Also known as” line is not reproduced.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER `Conclusion` section	🟢	Compresses all four paragraphs of the ER Conclusion into the decision-relevant core: what it is, where it works, where evidence is absent, and what is unresolved.
7.2	[at_a_glance] is no longer than 60 words	🟢	57 words (lines 434–438).
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause maps to ER Conclusion lines 440, 442, 444, and 446 respectively.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; NMDA, GlyT1, and autophagy are all avoided in favour of “the brain’s main excitatory receptors” and “entirely cells and animals”.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	Only the generic “Trials show”; no study, year, or sample size.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No SMD, confidence interval, odds ratio, or p-value appears.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER `Key Interactions & Contraindications` section	🟢	All six items come from the ER’s “Populations who should avoid Sarcosine” list (ER lines 293–298).
8.2	[stop_items] represent the Contraindications from the ER	🟢	All six ER populations are present, none added: prostate cancer, clozapine, pregnancy and lactation, severe renal impairment, seizure or recent stroke, children and adolescents.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Six discrete `<li>` elements at lines 573–581.
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.	🟢	Every ER rationale clause is stripped: “in whom no benefit has been demonstrated”, “for which no safety data of any kind exist”, “where clearance … is reduced”, “given increased excitatory signaling”.
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).	🟢	Retained: “active, untreated, or biochemically recurrent”, “above 4.0 ng/mL pending workup”, “below 30 mL/min/1.73 m²”, “within 90 days”, “outside a supervised trial setting”.
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.	🟢	The ER uses no ranking notation here, and no bare symbol is carried through; the items read as plain prose.
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 six such populations and the section is correspondingly populated, not empty.
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	🟢	All seven items come from the ER’s interaction bullets (ER lines 277–289).
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Seven of the ER’s eight interaction bullets appear; clozapine is correctly omitted because it is already a contraindication (line 577).
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Seven discrete `<li>` elements at lines 589–595.
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.	🟢	All “Consequence:” and “Mitigation:” clauses and the ER’s “(caution, opposition)”-style classifiers are stripped; each item is a bare noun phrase.
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 retained: “(memantine, ketamine, esketamine)” and “(risperidone, olanzapine, first-generation agents)”.
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 in the ER bullets; the retained parentheses are plain comma-separated drug lists.
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 populated, not empty.
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 the ER Therapeutic Protocol bullets at lines 320, 328, and 330.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER `Protocol` section	🟢	Dose, timing, and dose splitting are the three executable decisions; the remaining ER bullets (originating protocol, competing approaches, half-life, polymorphisms, sex, age, biomarkers, comorbidity) are background rather than actions.
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 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.	🟢	“2 g daily”, “Morning”, and “Once daily” each carry an ER-derived sub-line; no placeholders remain.

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	🟢	Symptom change, obsessive-compulsive symptoms, and cognition are exactly the three onsets the ER’s “Time to effect” bullet reports (ER line 373).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Schizophrenia symptom change is the ER’s only High-tier benefit and comes first; obsessive-compulsive symptoms and cognition are both Low-tier and follow in the ER’s own order.
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	The ER supplies 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.	🟢	“Week 2”, “Week 4”, and “12 weeks” each carry an ER-sourced sub-line; the week-4 pitfall is the ER’s own “stopping too early” bullet.
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 benefits map one-to-one onto the ER’s benefit headings across the four tiers.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present at lines 545, 548, 551, and 558.
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.	🟢	Reduced to the ER’s headings alone; no SMD, confidence interval, trial count, or participant number carried over. The retained “(conflicted)” is the ER’s own ⚠️ Conflicted evidence flag, which the tier label does not encode.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	The ER’s parenthetical glosses (SMD, 95% CI, sample sizes, cited authors) are all absent.
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 tiers carry items in the ER, so none needed hiding.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER `Potential Risks & Side Effects` section	🟢	All five risks map one-to-one onto the ER’s risk headings across the four tiers.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present at lines 607, 610, 613, and 618.
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.	🟢	Reduced to the ER’s headings alone; the odds ratios, dropout figures, and cited authors are absent. The retained “(conflicted)” is the ER’s own ⚠️ Conflicted evidence flag, which the tier label does not encode.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No frequency, severity grade, sample note, or example study is carried over from the ER’s risk entries.
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 tiers carry items in the ER, so none needed hiding.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER `Monitoring` section	🟢	Rows reproduce the ER’s Monitoring Protocol table (ER lines 401–408), with the Target column taken from “Optimal Functional Range” and the Why column from “Why Measure It?”.
14.2	All measurable/quantifiable biomarkers from the `Monitoring` section are listed	🟢	All six are present: total PSA, free PSA percentage, eGFR, ALT, homocysteine, and serum sarcosine or glycine.
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 727 reproduces the ER’s cadence: baseline, 3 months, 6 months, then every 6–12 months, with prostate markers on the same schedule.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER `Monitoring` section	🟢	Taken from the ER’s “Qualitative markers, tracked weekly” list (ER lines 412–416).
15.2	All subjective/qualitative biomarkers from the `Monitoring` section are listed	🟢	All five are present and verbatim: sleep onset latency, mental clarity, mood stability, verbal fluency, and headache/nausea/overstimulation.

Issues 14/08/2026 01:38

Pass rate 100.00%. No issues found.