Audit: QRS - Oleamide for Health & Longevity

Audit conducted on 22/09/2026 07:50 using AI4L / Opus 5

Iterations

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. 🟢 Protocol, time-to-effect, gate, benefit, risk, marker and cadence content all trace to ER text (ER 320–344, 374, 262–300, 124–180, 196–246, 398–423).
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 human half-life exists” (line 511) and “No established target exists; track change from the individual’s own baseline instead” (line 720) mirror ER 330 and ER 414.
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 carry the ER’s avoid-list at full strength; conflicted/animal-only framing retained (“if at all”, “in animals”).
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] come only from ER “Populations who should avoid Oleamide”; [caution_items] only from the ER interaction bullets; no modifying factors surfaced as gates.
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, citations, expert names, NCT IDs or brand names at all.
1.6 The QRS does not introduce new attributions. 🟢 No attributions present beyond the ER-derived facts.

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. 🟢 Sober, evidence-limited framing matching the ER’s own register.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Thresholds and targets given with plain-language explanation; no alarmism or salesmanship.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Descriptive throughout (“protocols stay at 25 mg”, “a single bedtime dose is standard”).
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No directives to the reader; monitoring cadence is stated as practice, not prescription.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No “recommended”, “should”, or “advised” in the document’s own voice.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns anywhere in the sheet.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical terms appear only where they are load-bearing decision thresholds carried from the ER.
2.8 Information is presented in a concise and very compact manner 🟢 All gate, benefit and risk entries are bare noun phrases with no explanation.
2.9 It DOES NOT address the reader directly 🟢 Confirmed; no direct address 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. 🟢 Optimal functional ranges and an 11-marker panel assume a proactive, self-tracking 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. 🟢 Standing blood pressure checks, morning core temperature and repeat blood work are retained.
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. 🟢 Content depth and tracking demands exceed general-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 evidence ceiling (one human trial, rest animal/laboratory) so weighting is explicit.
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” used in the title; “anti-aging” appears nowhere.
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. 🟢 Route stated as “100 mg orally” (line 447); no “pill”, “taken by mouth”, “shot” or similar 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 match the template byte for byte.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 Diff of span names against the template shows only the expected expansion of marker_#* into marker_1–11 and qualitative_item# into 1–6.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 The website=”evidence_review”, website=”audit” and website=”full_review” spans and all fixed markup are unchanged.

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 source ER section is empty; the empty benefit/risk tiers are governed by items 12.5 and 13.5 instead.
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 regimen”, “Best time of day”, “Dosing with dietary fat” and “Half-life” are the ER’s own bold labels; marker names are the ER table’s row labels.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 No label is shortened or renamed relative to the ER.
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 ⚠️ conflict markers were dropped as required.
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 bare phrases; no section carries explanatory prose beyond the per-cell budget.

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 and before the template comment on line 16.
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 “—” line 3, closing “—” line 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; no metadata value is repeated in the rendered 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:03” 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: oleamide_2026-0922-0451_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-0922-0740.
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” carries no qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 Line 9 matches the file’s own name.
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; no stray whitespace or 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 &) 🟢 Line 22: “Oleamide 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: “Oleamide for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 Line 421: 09/22/2026, from qrs_creation_date 2026-0922-0740.
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 block is identical in structure to the template; the ER’s alternate-names 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 🟢 Line 433 condenses ER 447–451: origin, single trial, evidence ceiling, and the three decision-relevant liabilities.
7.2 [at_a_glance] is no longer than 60 words 🟢 59 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each clause maps to a distinct sentence in ER 447–449.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms; “fat-derived molecule”, “animal or laboratory work” used in place of technical register.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 Refers only to “the one human trial” with no identifying detail.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No numbers of any kind in the lede.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Drawn from the “Populations who should avoid Oleamide” list, ER 284–300.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All eight ER avoid-list entries present, in ER order (lines 542–549).
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Eight discrete <li> elements.
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. 🟢 The ER’s pregnancy rationale and milk-transfer citation are stripped; explanatory glosses on AHI and eGFR removed.
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). 🟢 AHI 15 or more, Child-Pugh B or C, eGFR below 30 mL/min/1.73 m², systolic below 100 mmHg 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 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. 🟢 The ER names eight such populations and the section is populated accordingly.
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 🟢 Drawn from the interaction bullets, ER 264–282.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All ten ER interaction bullets present in ER order (lines 557–566); no population from the avoid-list duplicated here.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Ten discrete <li> elements.
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. 🟢 Caution/Monitor tags, mechanism, Consequence and Mitigation clauses and the Mendelson & Basile and Leggett citations are all stripped.
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 drug and supplement lists retained for all six bullets that carry them.
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 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. 🟢 The ER names ten interactions and the section is populated accordingly.
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 ER “Therapeutic Protocol”, ER 320–344.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Dose, timing and the fat-vehicle requirement are the three decisions the ER protocol turns on.
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. 🟢 Lines 444–473; the age carve-out in action_1_sub matches ER 340 and the vehicle note matches ER 334.

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 🟢 Memory onset (ER 136), sleep-onset latency (ER 374) and functional duration (ER 330).
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Memory (Medium tier) first, sleep (Low tier) second, then the half-life framing.
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 in the ER 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. 🟢 Lines 483–512; “Same night, if at all” and the 30–60 minute resolution are verbatim ER facts.
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.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Tier assignments match ER 128–180 exactly.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present, lines 521–532.
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’s own benefit heading reduced to a phrase; all eight speculative headings carried without commentary.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 The MCI Screen magnitude and the Sasaki attribution are 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. 🟢 benefits_high hidden with style=”display: none” (line 521), matching the ER’s “No benefit reaches High”.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Tier assignments match ER 200–246.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present, lines 578–589.
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. 🟢 All nine speculative risk headings reduced to bare phrases; no ED50, species detail or citation retained.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 The ED50 and NLRP3/IL-1β parentheticals from the ER are not 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. 🟢 risks_high, risks_medium and risks_low all hidden (lines 578, 581, 584), matching the ER’s empty High/Medium/Low tiers.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Rows mirror the ER biomarker table, ER 402–414.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All eleven ER biomarkers present in ER order with targets and rationale intact.
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 730 condenses ER 400: one week, four weeks, three months, then blood work every six to twelve months.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Drawn from the ER’s qualitative marker list, ER 418–423.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All six ER qualitative markers present (lines 739–755), trailing rationale clauses trimmed.

Issues 22/09/2026 07:50

Pass rate 100.00%. No issues found.

Issues 22/09/2026 07:45

  1. 4.2 / 4.3 — Time cell label paraphrased: The third Time-to-effect cell is labelled “Duration of effect” (QRS line 505), but the ER bullet its content is taken from is labelled “Half-life:” (ER line 330), so the label is a paraphrase rather than the ER’s verbatim label.

Fixes 22/09/2026 07:45

  1. 4.2 / 4.3 — Time cell label paraphrased: Changed the third Time-to-effect cell label from “Duration of effect” to the ER’s verbatim bullet label “Half-life” (QRS line 505).