Audit: QRS - D-Serine for Health & Longevity

Audit conducted on 18/09/2026 13:21 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 93
Passed 84
Failed 0
N/A 9
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, time, benefit, risk, monitoring and qualitative content traces to ER lines 239-269, 321-328, 351-371, 404, 434-450.
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 established target” (marker_5_target) is carried verbatim from ER line 440.
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 retain absolute framing; “Kidney harm appears in rats far above human exposures” matches ER line 477.
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. 🟢 stop_items and caution_items both come from ER Key Interactions & Contraindications; no modifying factors were promoted.
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, author names or NCT identifiers appear anywhere in the QRS.
1.6 The QRS does not introduce new attributions. 🟢 No attributions present.

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. 🟢 Observational, non-prescriptive register matching the ER.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Thresholds, dose ranges and monitoring targets are given without hedging or alarm.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Content is stated as what trials did and found, not as instructions.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No imperatives; monitoring cadence is presented as the trial cadence.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No recommending or advising verbs appear.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns in any variable region.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical terms retained are the ER’s own headings; the lede is jargon-free.
2.8 Information is presented in a concise and very compact manner 🟢 Sub-lines run 12-24 words; gate items are single clauses.
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. 🟢 Weight-based dosing, renal screening and plasma tracking assume a proactive 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. 🟢 Seven-marker laboratory panel and chiral plasma assay are presented without dilution.
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 simplified or generic-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. 🟢 The lede states the strongest evidence is psychiatric rather than longevity-facing, as the ER does.
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 occur; the 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)”; “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. 🟢 action_1_sub uses “administered orally”; “adverse events” used in risks_low; no colloquial route wording anywhere.

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, gate headings, tier labels and column headers are byte-identical to [qrs_template].
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All 34 fixed template spans present, plus 7 marker triplets and 5 qualitative items (60 spans total).
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Structure, CSS and the website=”…” spans are identical to the template.

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 drawn on by the QRS is empty; the empty risks High tier is governed by item 13.5.
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”, “Higher-dose approach” and “Best time of day” match the ER bold labels at lines 351, 353 and 363.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Protocol labels are ER-verbatim; time-to-effect cell labels partition the single ER “Time to effect” bullet as the template requires.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji present; the ER’s ⚠️ / ⭕️ markers were stripped.
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. 🟢 Section volumes sit within the template budget: 6 gate items, 7 interactions, 4 benefit tiers, 3 risk tiers, 7 markers, 5 qualitative items.

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, immediately after the doctype.
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. 🟢 Lines 3 and 13 delimit the block; the descriptive text on line 2 precedes it.
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 is echoed into 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: d_serine_2026-0918-0938_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: 26.9.11, 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: 2026-0918-1303.
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: 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.
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: 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 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.

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 &) 🟢 Line 22: “D-Serine 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., &amp; for &) 🟢 Line 417: “D-Serine for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 Line 421: 09/18/2026, from qrs_creation_date 2026-0918-1303.
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 carries only 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 🟢 Four sentences mirroring the four Conclusion paragraphs (ER lines 473-479).
7.2 [at_a_glance] is no longer than 60 words 🟢 56 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Receptor role, psychiatric dose dependence, older-adult spatial learning, rat kidney margin and four-month ceiling each map to a Conclusion sentence.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms; “NMDA”, “co-agonist” and “proximal tubule” were all avoided.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial names, years or sample sizes.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No numeric effect measures.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All six items come from ER lines 323-328 (“Populations who should avoid D-Serine”).
8.2 [stop_items] represent the Contraindications from the ER 🟢 All six ER populations are present, none added.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Six <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. 🟢 ER trailing clauses (“— the one exclusion applied across every regulator-monitored trial”, “— no human exposure data exist”, “; the only documented exposure…”, “, since trials show no added effect”) are all stripped.
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). 🟢 The 60 mL/min/1.73 m² threshold, CKD stage 3, the urinalysis findings and the age-18 limit are 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 uses no ranking notation in this section.
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 correctly 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 🟢 All seven items come from ER lines 305-319.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Seven of the eight ER interaction bullets are carried; clozapine is correctly omitted because it appears as a contraindication.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Seven <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. 🟢 Every ER “Severity: …; consequence …” clause is stripped; only the agent class and its examples remain.
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 seven parenthetical drug lists are retained; only the redundant “such as gentamicin” gloss inside the aminoglycoside entry was trimmed.
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 uses no ranking notation in this section.
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 correctly 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 come from ER Therapeutic Protocol lines 351-363.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Standard dose, higher-dose ceiling and timing are the three decisions a reader must make first.
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 Therapeutic Protocol carries thirteen bullets; 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 fields populated; values 30 mg/kg, 60 mg/kg and Morning all trace to ER lines 351, 353 and 363.

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/cognitive change (ER line 404), plasticity after a single dose (line 404) and the two-hour acute window (line 186).
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered High (negative symptoms), Medium (cortical plasticity), Low (acute attention and mood).
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 Three distinct aspects exist and 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 fields populated; “4–16 weeks”, “Single dose” and “2 hours” are each ER-sourced.
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 at line 404.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All nine benefits map to ER lines 152-208.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four 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. 🟢 Each entry is the ER benefit heading reduced to a clause; no magnitudes or sources carried.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses remain in any benefits 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. N/A All four benefit tiers carry at least one ER item.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All nine risks map to ER lines 233-287.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present.
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. 🟢 Entries are reduced ER headings; the 0.2% / 6.3% / 12.5% event rates and all sources are omitted.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses remain in any risks entry.
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. 🟢 ER line 235 states no risk reaches High; risks_high (line 573) is an empty span with style=”display: none”.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Derived from ER Monitoring Protocol & Defining Success, lines 428-442.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All seven ER table biomarkers are present as marker_1 through marker_7, with targets preserved.
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 679 reproduces the ER cadence of line 432, including the post-dose-increase recheck.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Derived from the qualitative marker list at ER lines 446-450.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All five ER qualitative markers are present as qualitative_item_1 through qualitative_item_5.

Issues 18/09/2026 13:21

Pass rate 100.00%. No issues found.

Issues 18/09/2026 13:14

  1. 4.5 — Content overruns one A4 page: The combined body — a 7-row Monitoring table with multi-line marker names and targets (lines 598–676), a 7-item Key Interactions gate in a half-width column (lines 555–561), and five 2-line Qualitative items (lines 687–701) — exceeds the single-page budget and would flow onto a second page.
  2. 13.3 — Risks Low item carries elaboration: Line 578 renders the third Low-tier risk as “general tolerability, where no symptomatic side-effect pattern has emerged”, appending the ER’s “Net:” explanation (ER line 267) rather than stating the ER heading’s key fact.

Fixes 18/09/2026 13:14

  1. 13.3 — Risks Low elaboration stripped: Replaced “general tolerability, where no symptomatic side-effect pattern has emerged” with the ER heading’s key fact, “headache and other symptomatic adverse events”.
  2. 4.5 — Monitoring table condensed: Shortened five marker targets and rationales (eGFR target, ALT/AST why, plasma D-Serine target and why, urinalysis why, BUN why, fasting glucose why) and tightened the cadence line to “Baseline, 4 weeks, 12 weeks, …”.
  3. 4.5 — Qualitative Assessment condensed: Trimmed the trailing rationale clauses on all five qualitative items so each fits a single rendered line without losing the marker or its ER basis.
  4. 4.5 — Protocol and At-A-Glance tightened: Reduced the At-A-Glance lede from 59 to 56 words and shortened action_1_sub, action_3_sub and time_1_sub while preserving every dose, window and qualifier.

Issues 18/09/2026 13:07

  1. 13.3 — Low-risk tolerability item not concise: Line 578’s third Low item, “no adverse event more frequent than placebo across pooled trials”, carries a study detail and states a trial result rather than the ER sub-heading’s risk, while dropping the ER’s “weak reassurance” hedge (ER lines 265–267).

Fixes 18/09/2026 13:07

  1. 13.3 — Low-risk tolerability item rewritten: Replaced the third Low risk item “no adverse event more frequent than placebo across pooled trials” with “general tolerability, where no symptomatic side-effect pattern has emerged”, removing the study detail and restoring the ER’s own net framing (ER line 267).