Audit: QRS - Black Currant Oil for Health & Longevity

Audit conducted on 17/08/2026 06:09 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 93
Passed 83
Failed 0
N/A 10
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. 🟢 Verified item by item against the ER: protocol cells vs ER lines 348/350/356/360, time cells vs ER 358/403, benefit and risk items vs ER section headings, gate items vs ER 304-326, monitoring table vs ER 431-438, cadence vs ER 429, qualitative items vs ER 442-446.
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. 🟢 Cautious ER phrasing retained, e.g. “No established target” (ER line 433) in [marker_1_target] and “Clinical payoff stays uncertain” from the ER Conclusion (line 474) in [at_a_glance].
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 or softening detected; contraindication severity qualifiers (“below 50 × 10⁹/L”, “within 2 weeks”, “Uncontrolled seizure disorder”) carried across intact.
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 only from the ER “Populations who should avoid Black Currant Oil” list; Key Interactions come only from the ER interaction bullets. No Benefit- or Risk-Modifying Factor was surfaced as a gate item.
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 PubMed IDs, author names, NCT identifiers or brand names appear anywhere in the QRS.
1.6 The QRS does not introduce new attributions. 🟢 No attributions of any kind are 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. 🟢 Matches the ER’s measured, sceptical register (“evidence base is thin, old and small”, ER line 470).
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Expert and data-driven throughout, with concrete doses, windows and biomarker targets.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Presents protocols and trial-derived figures rather than instructing.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Phrasing is descriptive (“protocols split the dose”, “the international normalised ratio is checked”), not advisory.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Content is stated as observation, e.g. [action_2_sub] “No circadian rationale exists; absorption depends on bile flow and co-ingested fat.”
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 carried from the ER are necessary for fidelity; no gratuitous jargon added.
2.8 Information is presented in a concise and very compact manner 🟢 Every cell is condensed to one or two clauses.
2.9 It DOES NOT address the reader directly 🟢 No direct address; [marker_5_target] uses “the individual’s prescribed therapeutic window”.
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. 🟢 Biomarker targets, genotype-relevant ratios and dose-escalation detail address a proactive, risk-aware 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. 🟢 Retains the 10,000 mg-of-oil inflammatory dose and the split-dosing regimen without softening the burden.
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. 🟢 Assumes willingness to run fatty acid panels and international normalised ratio checks.
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. 🟢 Weighs the intervention explicitly against marine omega-3 fats as a “narrow addition”, mirroring ER line 474.
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 appear; ageing is framed via longevity relevance.
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. 🟢 Uses “gastrointestinal upset”, “adverse”, “hypersensitivity”, “antihypertensives” rather than consumer-grade equivalents.

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 fixed headings, gate headings, tier labels and Monitoring column headers are byte-identical to the template.
3.2 All “” from the [qrs_template] are present in the the QRS. 🟢 Diffed against [qrs_template]: all 34 named spans present, plus the repeatable marker_#* and qualitative_item# spans instantiated as marker_1..6 and qualitative_item_1..5.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 The three website=”…” spans (evidence_review, audit, full_review), the style block, the override stylesheet link and the footer disclaimer are unchanged from 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 source ER section is empty; every ER section drawn on (Expected Benefits, Potential Risks & Side Effects, Key Interactions & Contraindications, Therapeutic Protocol, Monitoring Protocol & Defining Success) is populated, so no empty-state phrasing is required.
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 cell labels reuse the ER bold labels verbatim: “Standard oral dose” (ER 348), “Timing” (ER 356), “Single versus split dosing” (ER 360). Gate items reuse the ER bold interaction labels.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Monitoring row labels are verbatim ER biomarker names; tier labels are template-fixed. Time-to-effect cell labels are unavoidably derived because the ER carries a single “Time to effect” bullet with no per-aspect labels.
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 🟩/🟥/🟨 tier markers and ⚠️ Conflicted flags were correctly dropped.
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 budgets respected: benefit and risk tiers are single lines, gates 5 and 8 short items, monitoring 6 rows, qualitative 5 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. 🟢 HTML comment opens at line 2, immediately after “<!doctype html>” on line 1, and precedes the template comment and <html>.
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 preceding “QRS — Metadata” text sits outside the block.
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. 🟢 Contained entirely within the HTML comment; no metadata value is echoed by any rendered element.
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. 🟢 All values trimmed; only “00:03” is quoted, correctly, because it contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 “er_filename: black_currant_oil_2026-0825-0449_Opus_ER.md” matches the source ER on disk.
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” matches 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) 🟢 “qrs_creation_date: 2026-0817-0602” conforms to YYYY-MMDD-HHMM.
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢 “qrs_creator_ai_nickname: Opus” present.
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” is a single word with 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]” 🟢 “qrs_creator_ai_fullname: Opus 5” present.
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” is nickname plus version number with no additional qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 “qrs_filename: black_currant_oil_2026-0825-0449_Opus_QRS.html” matches the actual filename.
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: no stray whitespace and no unnecessary quoting on any of the nine frontmatter values.

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 &) 🟢 Black Currant Oil for Health & Longevity - Quick Reference Sheet matches canonical_topic (ER frontmatter line 8) with “&” entity-encoded.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 [header_topic] is “Black Currant Oil for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 “08/17/2026” is qrs_creation_date 2026-0817 reformatted as MM/DD/YYYY.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 [header_subline_model] is “Opus 5”, matching qrs_creator_ai_fullname.
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 title and the template subline; no badge, alternate-names line or audit stamp.

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 468-474) into composition, the replicating biochemical finding, the class-inference caveat, the risk profile and the residual uncertainty.
7.2 [at_a_glance] is no longer than 60 words 🟢 58 words, verified by word count.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each clause maps to a distinct Conclusion passage: composition (line 468), biochemical replication (470), class inference (470), mild digestive risks (472), uncertain payoff (474).
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 Uses plain-language substitutes throughout — “an uncommon omega-6 fat” for gamma-linolenic acid, “one inflammatory signalling molecule” for prostaglandin E2, “blood chemistry” for the fatty acid panel. No acronyms.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial name, year, sample size or p-value appears.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No effect size, relative risk or statistical result appears.

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 Black Currant Oil” list inside the ER Key Interactions & Contraindications section (ER lines 320-326).
8.2 [stop_items] represent the Contraindications from the ER 🟢 All five ER avoid-populations are represented, one to one.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Each of the five items is a discrete <li> 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. 🟢 No rationale, citation or post-dash clause on any item; the ER gloss “(an inherited clotting-protein deficiency)” was correctly dropped.
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). 🟢 Threshold and time-window qualifiers preserved: “below 50 × 10⁹/L”, “within 2 weeks, including dental extraction”, “Uncontrolled seizure disorder”, and the haemophilia / von Willebrand parenthetical.
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 Key Interactions & Contraindications section uses no ranking notation inside parentheses.
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 section is populated, and the ER does name populations that should avoid the oil, so the constraint holds.
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 Contraindications section is not empty; it carries five items.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Drawn from the eight interaction bullets of the ER Key Interactions & Contraindications section (ER lines 304-318).
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All eight ER interaction bullets are represented; none duplicates a Contraindication item.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Each of the eight items is a discrete <li> 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. 🟢 Mechanistic rationale (“additive platelet inhibition”, “sesamin inhibits delta-5 desaturase”) and mitigation clauses stripped; no post-dash content remains.
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 drug lists preserved for all six bullets that carry them, including the six-supplement list pulled forward from the ER body text of the “Other blood-pressure-lowering and platelet-inhibiting supplements” bullet.
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 Key Interactions & Contraindications section uses no ranking notation inside parentheses.
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 section is populated, and the ER does name interactions that change how the oil is used, so the constraint holds.
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 Key Interactions section is not empty; it carries eight items.

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 section (ER lines 348, 350, 356, 360).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Dose, timing and single-versus-split dosing are the three execution-critical aspects; the remaining ER bullets are competing approaches, pharmacokinetics and modifier discussion.
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 section supplies more than three actionable implementation 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. 🟢 All nine label/value/sub fields carry ER-derived content; none is placeholder.

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 🟢 Blood fatty acid shift, joint symptoms and dry eye symptoms are three of the four aspects in the ER “Time to effect” bullet (ER line 403); the Low-tier immune response readout is the one omitted.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered High-tier benefit (dihomo-γ-linolenic acid enrichment) first, then the two Medium-tier benefits, with the Low-tier immune aspect dropped.
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 four 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. 🟢 All nine label/value/sub fields carry ER-derived content, with sub-cells drawn from ER lines 358 and 403.
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 (Practical Considerations, ER line 403), so the section is retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All four tiers trace to the ER Expected Benefits headings.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four benefit spans are 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. 🟢 Items are the ER benefit headings alone; no magnitude, mechanism or trial detail carried over.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content survives in any benefit item.
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 items in the ER; no sub-section span needed hiding.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All four tiers trace to the ER Potential Risks & Side Effects headings.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four risk spans are present and populated.
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. 🟢 Items are the ER risk headings alone; the “⚠️ Conflicted” flag, frequencies and relative risks are stripped.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content survives in any risk item.
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 risk tiers carry items in the ER; no sub-section span needed hiding.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 The six-row table reproduces the ER Monitoring Protocol & Defining Success biomarker table (ER lines 431-438).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All six ER biomarkers are listed with targets and rationales matching the ER text.
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. 🟢 [monitoring_cadence] reproduces the ER cadence paragraph (ER line 429), including the 12-week repeat, the 6-12 month interval and the anticoagulant international normalised ratio schedule.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 The five items reproduce the “Qualitative markers to track alongside the labs” list in the ER Monitoring Protocol & Defining Success section.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All five ER qualitative markers are listed verbatim (ER lines 442-446).

Issues 17/08/2026 06:09

Pass rate 100.00%. No issues found.