evipedia.ai ← Back to Review

Audit: QRS - Oregano Oil for Health & Longevity

Audit conducted on 08/07/2026 05:29 using AI4L / Opus 4.8

Iterations

Summary

Items Count
Total 91
Passed 82
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, benefit, risk, contraindication, interaction, monitoring, and qualitative content traces to the ER.
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. 🟢 At-a-glance preserves the ER’s “mostly in laboratory tests” / “stays unproven” hedging.
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 and hedged claims match ER strength.
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. 🟢 Each block maps to the correct ER source section.
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, NCT IDs, or brand names.
1.6 The QRS does not introduce new attributions. 🟢 No new attributions introduced.

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. 🟢 Tone mirrors the ER’s measured, evidence-graded voice.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Meets tone requirement.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Presents evidence, not directives.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Framed as distillation of an evidence review.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Information-presenting throughout.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person address in variable content.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain language used; technical terms are minimal and appropriate.
2.8 Information is presented in a concise and very compact manner 🟢 Compact one-page layout.
2.9 It DOES NOT address the reader directly 🟢 No direct reader 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 this audience.
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 a proactive 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 general-population framed.
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. 🟢 Weighting reflects the target audience.
2.14 The document’s own voice frames usage in longevity terms, not “anti-aging”. Proper names that contain “anti-aging” are quoted verbatim. 🟢 No “anti-aging” usage.
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. 🟢 Formal register used (“gastrointestinal”, “mucosal”, “hypoglycemia”).

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, and Monitoring table column headers. 🟢 “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”, “Contraindications”, “Key Interactions”, tiers, and “Marker/Target/Why” all intact.
3.2 All “…” from the [qrs_template] are present in the QRS. 🟢 All referenced variable spans present.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 No unaddressed spans altered.

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 source section is empty; all blocks carry 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. 🟢 Labels sourced faithfully.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 No invented labels.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). 🟢 No emoji indicators; color via CSS.
4.5 The QRS is designed to render on one A4 page. 🟢 Content condensed to fit one page.

5. Metadata

# Description Result Comments
5.1 The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>”. 🟢 Comment block at lines 2–14.
5.2 Inside that HTML comment the YAML block is delimited by a line “—” opening and a line “—” closing. 🟢 Delimited at lines 3 and 13.
5.3 The metadata is not visible in any rendered view of the QRS. 🟢 Enclosed in an HTML comment.
5.4 All frontmatter values are trimmed: no leading/trailing whitespace, no surrounding quotes unless YAML-required. 🟢 Only duration is quoted (contains a colon).
5.5 The filename of the source ER is stated as “er_filename: [er_filename]”. 🟢 er_filename: oregano_oil_2026-0708-0348_Opus_ER.md
5.6 Version of the QRS.md file used to create the document is stated as “qrs_prompt_version:”. 🟢 qrs_prompt_version: 26.7.02
5.7 Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]”. 🟢 qrs_creation_date: 2026-0708-0523
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname:”. 🟢 qrs_creator_ai_nickname: Opus
5.9 The nickname of the AI is just a single word model name without version. 🟢 “Opus”
5.10 The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname:”. 🟢 qrs_creator_ai_fullname: Opus 4.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”
5.12 The filename of the document is stated as “qrs_filename:”. 🟢 qrs_filename: oregano_oil_2026-0708-0348_Opus_QRS.html
5.13 All frontmatter values are trimmed: no leading/trailing whitespace, no surrounding quotes unless YAML-required. 🟢 Values clean.

6. Page Title & Header

# Description Result Comments
6.1 [page_title] is set to the [canonical_topic] followed by “ - Quick Reference Sheet”, HTML-entity-encoded as needed. 🟢 “Oregano Oil for Health & Longevity - Quick Reference Sheet”.
6.2 [header_topic] is set to the [canonical_topic], with HTML entities encoded as needed. 🟢 “Oregano Oil for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]. 🟢 2026-0708 → 07/08/2026.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname]. 🟢 “Opus 4.8”.
6.5 No additional header content appears (no badge, version stamp, AKA line, source-AI attribution, audit date, or variant marker). 🟢 Header carries only the standard subline.

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.
7.2 [at_a_glance] is no longer than 60 words. 🟢 57 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each clause traces to the Conclusion.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge. 🟢 Plain-language only.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values). 🟢 No trials cited.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results. 🟢 No statistics cited.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section. 🟢 Sourced from the “Populations who should avoid it” bullet.
8.2 [stop_items] represent the Contraindications from the ER. 🟢 Pregnancy/breastfeeding, infants/children, Lamiaceae allergy, surgery/warfarin/insulin, undiluted oil.
8.3 Individual [stop_items] are formatted as <li></li>. 🟢 Each item is an <li>.
8.4 Items are as concise as possible; no trailing explanations/mechanistic rationale; no content after an em/en/hyphen dash. 🟢 Mechanistic rationale (e.g., “theoretical uterine risk”) correctly stripped.
8.5 Parenthetical qualifiers from the ER bullet ARE preserved, kept concise. 🟢 “(Lamiaceae)” and “(without medical supervision)” preserved.
8.6 When the ER uses ranking notation inside parens, normalize items to a plain comma-separated list. N/A The ER contraindication bullet uses no ranking notation.
8.7 If no [stop_items] are present the section is left empty. N/A Contraindications are present.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section. 🟢 Sourced from the ER interaction bullets.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any already listed as Contraindications. 🟢 CYP drugs, NSAIDs/aspirin, iron, glucose-lowering supps, blood-thinning supps, antibiotics/antifungals/probiotics.
9.3 Individual [caution_items] are formatted as <li></li>. 🟢 Each item is an <li>.
9.4 Items are as concise as possible; no trailing explanations; no content after an em/en/hyphen dash. 🟢 No trailing dash clauses.
9.5 Parenthetical qualifiers (example drug lists, etc.) ARE preserved, kept concise. 🟢 Example drug lists preserved in parens.
9.6 When the ER uses ranking notation inside parens, normalize items to a plain comma-separated list. N/A The ER interaction bullets use no ranking notation.
9.7 If no [caution_items] are present the section is left empty. N/A Key interactions are present.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section. 🟢 Sourced from Therapeutic Protocol.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects. 🟢 Dose, Frequency, Duration.
10.3 If less than three distinct actionable aspects are mentioned, the unused sets are left empty and made invisible. N/A Three actionable aspects are present.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content. 🟢 All cells populated from the ER (150–600 mg/day, 2–3× daily, 2–6 weeks).

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. 🟢 Gut response, antioxidant support, cold-symptom relief.
11.2 The sets are picked and ordered by the magnitude of the related benefit. 🟢 Gut (medium), antioxidant (medium), cold-symptom (low) — descending.
11.3 If less than three distinct time-to-effect aspects are mentioned, the unused sets are left empty and made invisible. N/A Three time-to-effect aspects are present.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content. 🟢 All cells populated from the ER.
11.5 If the ER does not provide any information on time to effect, the section is removed completely. N/A The ER provides time-to-effect information.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section. 🟢 Sourced from Expected Benefits.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]. 🟢 All four tiers populated.
12.3 Items are as concise as possible; no explanations, effect sizes, qualifiers, or citations. 🟢 Bare descriptors only.
12.4 Parenthetical content is stripped, NOT preserved. 🟢 No parentheticals present.
12.5 If no items of a specific sub-section are present the respective SPAN is set to display=none. N/A All four tiers contain items.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section. 🟢 Sourced from Potential Risks & Side Effects.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]. 🟢 All four tiers populated.
13.3 Items are as concise as possible; no explanations, effect sizes, qualifiers, or citations. 🟢 Bare descriptors only.
13.4 Parenthetical content is stripped, NOT preserved. 🟢 No parentheticals present.
13.5 If no items of a specific sub-section are present the respective SPAN is set to display=none. N/A All four tiers contain items.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section. 🟢 Sourced from Monitoring Protocol & Defining Success.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed. 🟢 ALT, Fasting glucose, HbA1c, Ferritin, hs-CRP — all five present.
14.3 [monitoring_cadence] is populated with the monitoring cadence/frequency derived from the ER. 🟢 Baseline for at-risk users; recheck ~4–6 weeks; every 6–12 months if recurrent.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section. 🟢 Sourced from the ER qualitative markers list.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed. 🟢 All five qualitative markers present.

Issues 08/07/2026 05:29

Pass rate 100.00%. No issues found.