Audit: QRS - Oxiracetam for Health & Longevity

Audit conducted on 02/07/2026 06:12 using AI4L / Opus 4.8

Iterations

Summary

Items Count
Total 91
Passed 91
Failed 0
N/A 0
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 content traces to the ER (Protocol, Benefits, Risks, Interactions, Monitoring, Conclusion).
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/unproven framing preserved (e.g., “long-term value and safety remain unproven”).
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 proven benefit” mirrors ER “no direct evidence”; contraindications kept as avoid-level.
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, benefits, risks, monitoring all drawn from matching 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. 🟢 The QRS carries no citations, PMIDs, NCT IDs, or expert names.
1.6 The QRS does not introduce new attributions. 🟢 No new 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. 🟢 Objective, cautious, evidence-graded tone consistent with the ER.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Expert yet accessible framing maintained.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Presents evidence without prescribing.
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” 🟢 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 phrasing throughout; technical terms glossed where used.
2.8 Information is presented in a concise and very compact manner 🟢 Card content is compact and condensed.
2.9 It DOES NOT address the reader directly 🟢 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. 🟢 Framing suits proactive longevity-oriented readers.
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 an effort-willing 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 aimed at 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. 🟢 Longevity-relevant weighting preserved.
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” / “brain-aging”; no “anti-aging” voice.
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. 🟢 Uses formal terms (e.g., “orally”, “gastrointestinal upset”).

3. Template Integrity

# Description Result Comments
3.1 The following labels and headings on the QRS are fixed and not modified: card/section headings, gate headings, tier labels, Monitoring column headers. 🟢 All fixed headings and labels present and unmodified.
3.2 All “” from the [qrs_template] are present in the QRS. 🟢 51 distinct data-qrs-var spans present, matching the template.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Unaddressed spans (e.g., time_3, benefits_high, risks_high) left as template defaults/hidden.

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. 🟢 No empty sections require empty-state phrasing; empty tiers hidden via display:none.
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. 🟢 Labels (Standard Dose, Timing, markers) match ER wording.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Labels faithful to the ER.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). 🟢 No emoji indicators in the 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 one page; interactions trimmed to three caution-level 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. 🟢 Metadata comment is first element after doctype (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. 🟢 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 HTML comment; not rendered.
5.4 All frontmatter values are trimmed: no leading/trailing whitespace, no surrounding quotes unless required by YAML. 🟢 Values clean; only duration is quoted (contains colon).
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: oxiracetam_2026-0702-0515_Opus_ER.md (line 4).
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 (line 5).
5.7 Creation date and time is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” 🟢 qrs_creation_date: 2026-0702-0515 (line 6).
5.8 The nickname of the AI is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢 qrs_creator_ai_nickname: Opus (line 7).
5.9 The nickname of the AI is just a single word model name without version, etc. 🟢 “Opus” is a single word.
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 (line 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” is nickname + version.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename: oxiracetam_2026-0702-0515_Opus_QRS.html (line 9).
5.13 All frontmatter values are trimmed: no leading/trailing whitespace, no surrounding quotes unless required by YAML. 🟢 Values consistent and trimmed.

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. 🟢 “Oxiracetam for Health & Longevity - Quick Reference Sheet” (line 22).
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed. 🟢 “Oxiracetam for Health & Longevity” (line 417).
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 2026-0702-0515 → 07/02/2026 (line 421).
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 “Opus 4.8” (line 425).
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, date, and model; no extra content.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Condenses the ER Conclusion (lines 382-384).
7.2 [at_a_glance] is no longer than 60 words 🟢 53 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Head-injury signal, weak vascular evidence, no healthy-adult benefit, mild short-term safety all trace to the Conclusion.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 Plain terms (“brain compound”, “cognitive enhancer”, “blood-flow-related”).
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 effect sizes or statistics.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Drawn from “Populations who should avoid it” (ER line 256).
8.2 [stop_items] represent the Contraindications from the ER 🟢 Pregnancy/breastfeeding, children/adolescents, kidney impairment, seizure/anxiety.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Four <li> items (lines 541-544).
8.4 Items are as concise as possible. No trailing explanations, elaborations, rationale, attributions, citations, study details, or content after a dash. 🟢 Concise; no trailing clauses.
8.5 Parenthetical qualifiers from the ER bullet — time windows, severity classes, threshold values, clinical staging — ARE preserved, kept concise. 🟢 “(eGFR below 30 mL/min/1.73m²)” preserved.
8.6 When the ER uses ranking notation inside parens that depends on an explanatory phrase, normalize the items to a plain comma-separated list rather than carrying the bare symbol. 🟢 No such ranking notation in the source contraindications.
8.7 If no [stop_items] are present the section is left empty 🟢 Contraindications exist and are populated.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Drawn from the ER interactions bullets (lines 246-250).
9.2 [caution_items] represent the Key Interactions from the ER, excluding any already listed as Contraindications 🟢 Three caution-severity interactions carried; monitor-level items and contraindications excluded.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Three <li> items (lines 550-552).
9.4 Items are as concise as possible. No trailing explanations, elaborations, rationale, attributions, citations, study details, or content after a dash. 🟢 Concise; trailing rationale stripped.
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 for each item.
9.6 When the ER uses ranking notation inside parens that depends on an explanatory phrase, normalize to a plain comma-separated list rather than carrying the bare symbol. 🟢 No ranking notation in source interactions.
9.7 If no [caution_items] are present the section is left empty 🟢 Interactions exist and are populated.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 Derived from ER Therapeutic Protocol (lines 274-284).
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 key actionable aspects.
10.3 If less than three distinct actionable aspects are mentioned, unused sets are left empty and made invisible. 🟢 Three aspects available; 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 the ER.

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 🟢 Two time-to-effect aspects exist in the ER; both surfaced.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Cognitive benefit (weeks-months) precedes acute effect (~1 hour).
11.3 If less than three distinct time-to-effect aspects are mentioned, unused sets are left empty and made invisible. 🟢 Third set hidden via display:none (line 503).
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 Both used sets populated from ER Practical Considerations (line 325).
11.5 If the ER does not provide any information on time to effect, the section is removed completely from the Protocol Panel 🟢 ER provides time-to-effect data; section retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Derived from ER Expected Benefits (lines 144-178).
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four variables present.
12.3 Items are as concise as possible. No explanations, elaborations, effect sizes, qualifiers, attributions, citations, study details, or mechanisms. 🟢 Concise benefit labels only.
12.4 Parenthetical content — effect sizes, sample notes, mechanistic hints, example studies — is stripped, NOT preserved. 🟢 No parenthetical detail carried into benefits.
12.5 If no items of a specific sub-section are present the respective is set to “display=none”, not empty-state phrasing. 🟢 benefits_high hidden via display:none (line 521); no High tier in ER.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Derived from ER Potential Risks (lines 194-228).
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four variables present.
13.3 Items are as concise as possible. No explanations, elaborations, effect sizes, qualifiers, attributions, citations, study details, or mechanisms. 🟢 Concise risk labels only.
13.4 Parenthetical content — frequencies, severity grades, sample notes, mechanistic hints, example studies — is stripped, NOT preserved. 🟢 Medium-tier parenthetical “(insomnia, agitation, headache)” mirrors the ER heading’s own symptom specification, not a stripped category.
13.5 If no items of a specific sub-section are present the respective is set to “display=none”, not empty-state phrasing. 🟢 risks_high hidden via display:none (line 563); no High tier in ER.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Derived from ER Monitoring Protocol (lines 345-356).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 eGFR, serum creatinine, blood pressure, baseline cognitive score all listed.
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 populated (baseline, periodic kidney recheck, cognitive retest at 4-8 weeks then 3-6 months).

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Derived from ER “Qualitative markers” (lines 358-364).
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All five qualitative markers listed.

Issues 02/07/2026 06:12

Pass rate 100.00%. No issues found.

Issues 02/07/2026 06:07

  1. 11.3 — Unused time set not hidden: Only two time-to-effect aspects exist in the ER, but the unused time_3 set retains literal placeholder text [time_3_label], [time_3_value], [time_3_sub] (lines 505, 508, 511) and lacks display:none, so the raw placeholders render on the page instead of being left empty and made invisible.

Fixes 02/07/2026 06:07

  1. 11.3 — Unused time set now hidden: Emptied the time_3 label/value/sub spans (removed the literal [time_3_label], [time_3_value], [time_3_sub] placeholders) and added style="display:none" to the time_3 pcell so the unused set is left empty and invisible instead of rendering raw placeholders.