Audit: QRS - Lavender Oil for Health & Longevity

Audit conducted on 27/08/2026 10:40 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.	🟢	Spot-checked every populated span. Protocol cells trace to ER lines 343/347/351; time cells to ER 355/398; benefits and risks reproduce ER sub-headings verbatim; gates trace to ER 301–321; monitoring rows and cadence to ER 430–439; qualitative items to ER 443–448.
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 cautious ER phrasing is contradicted; the ER’s “No risk sits at Medium” is handled by hiding the Medium risk span per item 13.5.
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”).	🟢	Pregnancy/lactation and pre-pubertal children remain in Contraindications, not Key Interactions. At-a-Glance drops the ER’s “reliably” rather than adding emphasis.
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.	🟢	All gate items come from the ER Key Interactions & Contraindications section; no Benefit- or Risk-Modifying Factor is promoted into a gate.
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 only brand name is “Silexan”, used for the same 80 mg dosing fact at ER line 343. No PMIDs, NCT identifiers or author names appear.
1.6	The QRS does not introduce new attributions.	🟢	No investigator, institution or sponsor is named anywhere in the QRS.

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.	🟢	Measured, evidence-first register carried over from the ER, including its explicit funding caveat.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	At-a-Glance names both the tested benefit and the weak links; tiered benefit/risk lists let the reader weigh the evidence.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Protocol cells state what the trials used (“Trials dosed once daily in the morning”) rather than instructing.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperative or prescriptive constructions in authored content.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No occurrence of “recommend”, “advise” or “guidance” in authored content.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns in any populated span.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms appear only where the ER itself uses them (Child-Pugh Class C, CYP3A4) and only inside the gate lists where they are load-bearing.
2.8	Information is presented in a concise and very compact manner	🟢	Gate and tier items are single clauses; monitoring “Why” cells are one clause each.
2.9	It DOES NOT address the reader directly	🟢	Confirmed — no direct address in authored content.
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.	🟢	Content assumes willingness to verify chromatographic authenticity, track symptom scores and review interactions.
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.	🟢	Monitoring cadence and six-marker panel presuppose that willingness.
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 simplification toward casual consumer use; the oral/inhalation route distinction is preserved.
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.	🟢	At-a-Glance foregrounds the sponsorship and authenticity problems, which are the decision-relevant weaknesses for this audience.
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.	🟢	The string “anti-aging” does not occur; the header 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)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt.	🟢	“standardized capsule”, “inhalation”, “allergic contact dermatitis” used throughout; the few plain phrases in At-a-Glance (“lifts low mood”, “weak links”) are carried verbatim from the ER Conclusion.

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”	🟢	A structural diff against [qrs_template] shows every fixed heading, gate heading, tier label and table header byte-identical to the template.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 38 template variable names are present; marker_#_* and qualitative_item_# are correctly expanded to marker_1..6_* and qualitative_item_1..6.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Diff shows changes confined to metadata, page_title, the tier lists, the gate lists, and the repeated marker/qualitative rows — all checklist-addressed. CSS, header structure and footer are untouched.

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 non-tiered source section is empty. The only empty ER sub-section is the Medium risk tier (ER line 249), which item 13.5 explicitly directs to be hidden rather than filled with empty-state phrasing.
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 oral protocol”, “Competing approach — inhalation” and “Best time of day” reproduce the ER Protocol bold labels verbatim (ER 343/347/351).
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Protocol labels are verbatim; monitoring row labels reproduce the ER biomarker table names exactly.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji code point occurs anywhere in the rendered body; the ER’s “⚠️ Conflicted” markers 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.	🟢	Content stays within the template’s per-section budget: three protocol cells, three time cells, four benefit tiers, three risk tiers, six monitoring rows and six qualitative items, all single-clause.

---

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; it is the first element after the doctype at line 1.
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 preamble text at line 2 precedes the opening delimiter.
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; none of its values are echoed by a visible 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.	🟢	Only duration: "00:02" is quoted, and it contains a colon requiring it.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: lavender_oil_2026-0827-0854_Opus_ER.md, matching the 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]”	🟢	Line 5: qrs_prompt_version: 26.7.02, 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: qrs_creation_date: 2026-0827-1035, correct format.
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: qrs_creator_ai_nickname: 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)	🟢	“Opus” — 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: qrs_creator_ai_fullname: 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 actual file basename lavender_oil_2026-0827-0854_Opus_QRS.html.
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 unnecessary 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., & for &)	🟢	Line 22: “Lavender Oil for Health & Longevity - Quick Reference Sheet”, matching ER canonical_topic with the ampersand encoded.
6.2	[header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &)	🟢	Line 417: “Lavender Oil for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “08/27/2026”, correctly derived from 2026-0827-1035.
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.	🟢	The header block is structurally identical to the template; the ER’s “Also known as” line was correctly 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	🟢	Every clause maps to ER Conclusion lines 470–474: standardized form, anxiety/mood/sleep, non-sedating, inhalation, sponsorship and authenticity.
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.	🟢	Each clause traced to a distinct ER Conclusion sentence (lines 470, 472, 474).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “calming rather than sedating”, “dependence”, “withdrawal” are everyday terms.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial name, year or sample size appears.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numeric result of any kind.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All five items map one-to-one to the ER “Populations who should avoid Lavender Oil” bullets (ER 317–321).
8.2	[stop_items] represent the Contraindications from the ER	🟢	Five ER avoid-population bullets, five <li> items, no omissions or additions.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Lines 542–546, five discrete <li> elements inside the 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.	🟢	Trailing rationales stripped throughout, e.g. “on the basis of absent human safety data”, “given the twelve reported breast-development cases”, “all of which were exclusion criteria in every trial”, “since linalool is cleared by the liver”.
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).	🟢	“(oral preparations)”, “(sustained topical or fragrance exposure)”, “(Child-Pugh Class C)” and “moderate-to-severe” 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 five avoid-populations, and the section is correctly populated rather than left empty.
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 map one-to-one to the ER interaction bullets (ER 301–313).
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Seven ER interaction bullets, seven <li> items; no overlap with the five contraindications.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Lines 554–560, seven discrete <li> elements inside the 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.	🟢	All “Caution, …” rationales, crossover-trial details and PMID citations stripped; the ER’s category prefixes (“Supplement interactions —”, “Other intervention interactions —”) are correctly dropped in favour of the substantive term.
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).	🟢	Every ER example-drug list is retained verbatim, including “(tacrolimus, ciclosporin, some statins)” and “(magnesium, potassium, beetroot nitrate, garlic extract)”.
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 seven interactions, and the section is correctly populated rather than left empty.
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 derive from ER Therapeutic Protocol bullets at lines 343, 347 and 351.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose/form, competing route, and timing — the three decision-relevant aspects; the remaining ER bullets are attributional or covered by Time to Effect.
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, so no set is unused.
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section.	🟢	All nine spans populated; “80 mg once daily”, “2–4 drops, 15–30 min” and “Morning” all trace to the ER Protocol bullets.

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	🟢	Oral anxiety (week 2), oral sleep (week 6), inhaled acute anxiety (minutes) — the three onset windows the ER states at lines 355 and 398.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Anxiety and sleep are the first two High-tier benefits in ER order; the inhalation onset follows as the route-specific case.
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 three distinct time-to-effect aspects, so no set is unused.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All nine spans populated and traceable; “A fair trial of the oral route is six to ten weeks” mirrors ER line 355.
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 explicit time-to-effect data, so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All ten items reproduce ER Expected Benefits sub-headings across the four tiers.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present and populated at 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 item is the bare ER benefit heading; no Magnitude figures, confidence intervals or sponsor caveats carried over.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear 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 ER benefit tiers contain items, so no benefit span needed hiding.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All seven items reproduce ER Potential Risks & Side Effects sub-headings.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present at lines 572–581.
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.	🟢	Each item is the bare ER risk heading; the 2.8% patch-test figure, risk ratio 1.06 and case counts are all omitted.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear 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.	🟢	Line 575: <span data-qrs-var="risks_medium" style="display: none"></span>, correctly matching the ER’s “No risk sits at Medium” (ER line 249).

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	All six rows and the cadence derive from the ER Monitoring Protocol & Defining Success section (ER 430–439).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All six ER table biomarkers present: alanine aminotransferase, aspartate aminotransferase, seated office blood pressure, resting heart rate, total testosterone (men), estradiol (men), with targets reproduced exactly.
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 667 condenses ER line 430: two/six/ten-week symptom scores, weekly blood pressure for a month, conditional liver enzymes, six-to-twelve-month review.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	All six items come from the ER qualitative marker list at lines 443–448.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	Six ER qualitative markers, six <li> items, in ER order; only the trailing clause “which improved alongside anxiety in the trials” was trimmed for concision.

Issues 27/08/2026 10:40

Pass rate 100.00%. No issues found.