Audit: QRS - Lemon Balm for Health & Longevity

Audit conducted on 19/08/2026 15:32 using AI4L / Opus 5

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.	🟢	Every span traced to source: at-a-glance to ER `Conclusion`, protocol cells to ER `Therapeutic Protocol`, time cells to `Practical Considerations` and `Relief of Benign Heart Palpitations`, benefit/risk tiers to ER headings, gates to `Key Interactions & Contraindications`, table to the ER biomarker table.
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.	🟢	“The signal lemon balm may theoretically blunt”, “Screens the theoretical additive hypoglycemia risk”, “No established target exists” and “Nothing here is settled in either direction” all carried over unchanged.
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”).	🟢	Avoid-list entries stay in the Contraindications gate and interaction entries stay in the Key Interactions gate; no tier was promoted or demoted relative to the ER.
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.	🟢	No content from ER `Benefit-Modifying Factors` or `Risk-Modifying Factors` appears in the gates or the risk card.
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 PMIDs, author names, NCT numbers or brand names appear anywhere in the QRS; the drug names in the gates are all present in the corresponding ER bullets.
1.6	The QRS does not introduce new attributions.	🟢	No attributions of any kind 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, hedged register of the ER carried through, including the ER’s own “Nothing here is settled in either direction”.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Thresholds, ranges and cadence give the reader actionable material without exhortation.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	All statements descriptive (“Evening dosing is standard”, “Baseline panel before starting”), none imperative.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No prescriptive verbs; the only advisory text is the fixed template disclaimer in the footer.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Constructions are declarative or passive throughout (“is standard”, “logged weekly”, “rechecked at 12 weeks”).
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronoun occurs anywhere in the document body.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms are limited to biomarker names, each carrying the ER’s own parenthetical short form (TSH, free T4, HbA1c, hs-CRP, ALT).
2.8	Information is presented in a concise and very compact manner	🟢	Gate items are noun phrases, benefit/risk tiers are semicolon-separated lists, all rationale and citation text stripped.
2.9	It DOES NOT address the reader directly	🟢	Confirmed: no “you”/”your” in the rendered 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.	🟢	Functional-range targets, an 11-marker panel and a titration-relevant time-to-effect row all address the optimizing 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.	🟢	Nightly sleep logs, weekly home blood-pressure logging and repeat thyroid panels are presented without hedging on effort.
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 assumes access to laboratory testing and willingness to run a structured monitoring schedule.
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 at-a-glance foregrounds the alertness trade-off, which is the decisive point for an already-optimized, cognitively demanding reader.
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 one related phrase is “relevant to aging”, taken from the ER heading.
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.	🟢	Clinical register throughout; the plain-language phrasings “blood fats” and “upper blood pressure” occur only inside the at-a-glance, where item 7.4 requires plain-language substitution, and are the ER `Conclusion`’s own wording.

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 heads, tier labels and column headers are byte-identical to the template.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 named template variables present; the repeatable `marker_#_*` and `qualitative_item_#` rows are expanded to marker_1–11 and qualitative_item_1–6.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The three `website=` spans (evidence_review, audit, full_review) and the entire CSS block, head and footer 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 relied on by the QRS is empty; the ER supplies content for every mapped section.
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”, “Best time of day” and “European regulatory dosing” are the ER’s bold labels verbatim; monitoring rows reuse the ER table’s biomarker names verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Protocol, marker and qualitative labels are ER wording; the three time-to-effect labels are the only derived labels and are required because the ER packs all durations into one “Time to effect” bullet.
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 “⚠️ Conflicted” markers on three benefit headings 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.	🟢	Every section is condensed to the floor its own checklist item allows: rationale clauses, glosses, em-dash trailers, effect sizes and citations are all stripped, and sub-texts are one to two clauses.

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: the metadata comment immediately follows `<!doctype html>` on 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 `---` on line 3, closing `---` on line 13; the preceding title line is permitted.
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 and not duplicated anywhere in `<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.	🟢	All values trimmed; the only quoted value, `duration: "00:03"`, contains a colon and requires quoting.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: `er_filename: lemon_balm_2026-0825-1220_Opus_ER.md`, matching the source ER.
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-0819-1511`, in the required 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” is a single word carrying 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]”	🟢	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” is nickname plus version number with no context-window or other qualifier appended.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9: `qrs_filename: lemon_balm_2026-0825-1220_Opus_QRS.html`, matching the file on disk.
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; only the colon-bearing `duration` value is quoted.

#	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: “Lemon Balm for Health & Longevity - Quick Reference Sheet”, matching the 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: “Lemon Balm for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “08/19/2026”, the correct reformatting of `2026-0819-1511`.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “Opus 5”, matching the frontmatter value.
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 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	🟢	Compresses all three ER `Conclusion` paragraphs into the evidence base, the replicated outcomes, the governing trade-off and the overall verdict.
7.2	[at_a_glance] is no longer than 60 words	🟢	58 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Sentence 1 from `Conclusion` ¶1 opening, sentence 2 from ¶1, sentence 3 from ¶2 opening, sentence 4 from ¶3 closing.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “blood fats” and “upper blood pressure” stand in for blood lipids and systolic blood pressure, and “mint-family herb” for Lamiaceae.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No author names, years, enrolment figures or p-values.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No SMDs, confidence intervals or numeric results; magnitudes are given qualitatively as “modestly lower”.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER `Key Interactions & Contraindications` section	🟢	All six items come from the “Populations who should avoid Lemon Balm” list in that ER section.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All six ER avoid-list bullets are represented, one to one, with none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Lines 569–579: six 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.	🟢	Rationale clauses stripped from all six (“on European Medicines Agency advice…”, “because of additive sedation…”, “where added sedation may worsen…”), and the em-dash trailer “— commercial driving, aviation, heavy machinery” removed from the vigilance item.
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).	🟢	“above 4.0 mIU/L”, “under 12 years”, “within two weeks”, “moderate-to-severe”, “(more than 15 events per hour)” and “within six hours of dosing” all preserved; only the plain-language glosses were trimmed.
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 this section; the one threshold is already written out as “more than 15 events per hour”.
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 does identify such 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 eleven items map one to one onto the eleven interaction bullets of that ER section.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All eleven ER interaction bullets present; none duplicates a Contraindications entry.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Lines 587–606: eleven 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.	🟢	The “Caution.”/”Monitor.” verdicts and every mechanism and management sentence (“Additive sedation and impaired coordination”, “Administration is separated by four hours…”) are stripped; each item is a bare noun phrase plus examples.
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 (diazepam/zolpidem/phenobarbital; lisinopril/losartan/amlodipine; metformin/glipizide/insulin; oxybutynin/amitriptyline; and the supplement and non-drug lists in full).
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 this section.
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 identifies eleven such interactions and the section is correctly populated.
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 come from bullets of the ER `Therapeutic Protocol` section.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER `Protocol` section	🟢	Dose and form, timing, and the regulatory tea/tincture alternative are the three bullets that determine what a reader actually takes and when.
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 contains thirteen bullets, so 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 spans populated; values carry the ER’s dose figures (300–600 mg; Evening; 1.5–4.5 g) and subs carry the ER’s frequency and vehicle detail.

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	🟢	The acute calming/sleep onset and the 8–12 week cardio-metabolic window from `Practical Considerations`, plus the 14-day palpitation window from `Expected Benefits`.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered Medium (anxiety/sleep, the largest pooled effect at SMD −0.98), Medium (lipids and systolic pressure), then Low (palpitations).
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 time-to-effect aspects are available in the ER, so 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 spans populated; values “1–3 hours”, “8–12 weeks” and “14 days” match the ER’s “one to three hours”, “8 to 12 weeks” and “Fourteen days”.
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, so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER `Expected Benefits` section	🟢	All fifteen listed benefits are the ER’s own `Expected Benefits` sub-headings.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present at lines 538, 539, 545 and 553.
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 bare ER heading; no SMDs, confidence intervals, p-values or mechanism text carried over.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses in any benefit entry; the ER’s “⚠️ Conflicted” heading markers were also removed.
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.	🟢	The ER has no High-tier benefits and line 538 sets `benefits_high` to `style="display: none"` with no empty-state text.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER `Potential Risks & Side Effects` section	🟢	All ten listed risks are the ER’s own `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 618, 619, 622 and 629.
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 entry is the bare ER heading; the dose figures, in-vitro concentrations and case-report detail from the ER bodies are absent.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses in any risk entry.
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.	🟢	The ER has no High-tier risks and line 618 sets `risks_high` to `style="display: none"` with no empty-state text.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER `Monitoring` section	🟢	Marker names, targets and reasons are taken from the biomarker table of the ER `Monitoring Protocol & Defining Success` section.
14.2	All measurable/quantifiable biomarkers from the `Monitoring` section are listed	🟢	All eleven ER table rows present, in ER order, from Thyrotropin through Serum rosmarinic acid; targets match verbatim including “10–26 U/L (men), 10–19 U/L (women)” and the entity-encoded “<1.0 mg/L”.
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.	🟢	Lines 794–799 carry the baseline panel, the 12-week and 6–12 month lipid/glucose/inflammation intervals, the thyrotropin schedule and the home blood-pressure logging frequency.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER `Monitoring` section	🟢	All six items come from the qualitative-marker bullet list at the end of the ER `Monitoring Protocol & Defining Success` section.
15.2	All subjective/qualitative biomarkers from the `Monitoring` section are listed	🟢	All six ER bullets present, in ER order; only the attributions “the instrument used in the crossover trial” and “given the documented alertness decrement” were trimmed.

Issues 19/08/2026 15:32

Pass rate 100.00%. No issues found.

Issues 19/08/2026 15:24

11.1 — Third time-to-effect set unused: Only two of the three [time] sets are populated (lines 496-517) while the third is blanked and hidden at line 518, even though the ER reports further time-to-effect data for listed benefits, such as the fourteen-day palpitation result at ER line 193.

Fixes 19/08/2026 15:24

11.1 — Third time-to-effect set populated: Filled the blank third [time] set with the ER’s fourteen-day palpitation result (label “Reduced palpitation episodes”, value “14 days”, sub “Of freeze-dried aqueous leaf extract in the single trial that measured it.”) and removed the style="display: none" from that cell.

Issues 19/08/2026 15:17

11.1 / 11.3 — Duplicate time-to-effect set: time_2 and time_3 (QRS lines 507–532) both read “8–12 weeks” and both derive from the single ER sentence at line 449, so the third set is not a distinct aspect; time_3_sub additionally negates its own cell by stating “the pooled cardio-metabolic meta-analysis found no glucose effect”.

Fixes 19/08/2026 15:17

11.1 / 11.3 — Duplicate time-to-effect set removed: Merged the redundant glucose cell into time_2, whose label now reads “Lipid, blood pressure and glucose changes” (from “Lipid and blood pressure changes”), matching the ER sentence the value derives from. The third set was emptied and its .pcell made invisible with style="display: none", with all three time_3_* spans retained.