Audit: QRS - Chamomile for Health & Longevity

Audit conducted on 18/09/2026 10:10 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.	🟢	Every benefit, risk, contraindication, interaction, protocol cell, marker row and qualitative item traces to a matching ER heading, bullet or table row.
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 ER’s ⚠️ Conflicted flags are carried as “(conflicted)”; Speculative-tier items are kept in the Speculative tier without upgrade.
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, breastfeeding, unstable INR and transplant items remain absolute contraindications, matching the ER’s avoid list.
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.	🟢	Gate content comes only from Key Interactions & Contraindications; risks only from Potential Risks & Side Effects; no modifying-factor content is repurposed.
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 IDs or brand names appear anywhere in the QRS.
1.6	The QRS does not introduce new attributions.	🟢	No attributions 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.	🟢	Neutral, evidence-first register identical to the ER.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Tiered benefit/risk lists and concrete doses, without hedging or alarmism.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Regimens are described as the trial regimens, not as instructions.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperatives; monitoring cadence is stated descriptively.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No recommending verbs used.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns in the document.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms are limited to marker names and drug classes required by the decision gates.
2.8	Information is presented in a concise and very compact manner	🟢	All list items are single clauses; mitigations, mechanisms and citations are stripped.
2.9	It DOES NOT address the reader directly	🟢	Confirmed by full-text scan for “you”/”your”.
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 self-directed implementation and biomarker tracking.
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.	🟢	Thrice-daily dosing, an eight-marker panel and repeat laboratory testing are presented without simplification.
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.	🟢	Functional ranges (HbA1c ≤5.4%, hs-CRP <0.5 mg/L) are optimisation targets, not population norms.
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 states the anxiety and sleep evidence points both ways rather than promoting the intervention.
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” appears only 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.	🟢	Routes are given as “oral extract”, “mouth rinse”, “topical oil”; drug classes are named formally (“insulin-releasing oral medications”, “calcineurin inhibitors”).

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 column headers are byte-identical to the template.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 singleton variables present exactly once; marker_#* repeated for 8 rows (24 spans) and qualitative_item# for 6 items.
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 the entire style block 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; the absent Medium risk tier is handled under 13.5.
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 labels “Standardized extract, the trial regimen”, “Tea preparation” and “Best time of day” are the ER’s bold labels verbatim; marker names match the ER biomarker table verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Time-to-effect labels are taken from the ER’s own time-to-effect clause wording (“Blood sugar and lipids”, “Sleep quality”, “Anxiety”).
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	Full-text scan returns no emoji code points.
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 heading-level facts: benefits and risks are bare descriptor lists, gate items carry no mitigations or mechanisms, and marker rows carry no context column.

---

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.
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 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, correctly, because it contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	er_filename: chamomile_2026-0918-0533_Opus_ER.md, matching the ER’s own filename field.
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.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)	🟢	qrs_creation_date: 2026-0918-1003.
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.
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]”	🟢	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)	🟢	Nickname plus version only, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	qrs_filename: chamomile_2026-0918-0533_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: no stray whitespace or unnecessary quoting on any key.

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 &)	🟢	“Chamomile 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., & for &)	🟢	“Chamomile for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	09/18/2026, matching qrs_creation_date: 2026-0918-1003.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	“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 contains only the title and the template 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 Conclusion’s first paragraph: preparations, the six best-supported outcomes, and the conflicted evidence.
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 maps to the Conclusion sentence “The strongest human findings are …” and “for anxiety and sleep the combined trial evidence points both ways”.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	“average blood sugar”, “mouth inflammation”, “gum bleeding” replace HbA1c, mucositis and gingival indices.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial identifiers present.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	Only directional wording (“modest reduction”, “lower average blood sugar”).

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All seven items come from that section’s “Populations who should avoid Chamomile” list.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All seven ER avoid-list entries are present, none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Seven <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.	🟢	ER rationales (“given the threatened-miscarriage and preterm-labour signal”, “on the basis of absent data rather than demonstrated harm”, “as a precaution rather than a documented harm”) are all stripped.
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).	🟢	“before 37 weeks’ gestation”, “INR … above the upper limit of their target”, “without therapeutic drug monitoring”, “within two weeks of elective surgery” 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 this section.
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 seven avoid populations and the section is correspondingly populated.
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 to the eleven ER interaction bullets.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	No item duplicates a contraindication; warfarin and calcineurin-inhibitor entries are contraindicated only in the narrower unstable-INR and unmonitored-transplant cases.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Eleven <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.	🟢	Every ER “Mitigation:” clause and severity verb (“caution”, “monitor”) is stripped; only the interacting class 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 examples retained throughout (warfarin/acenocoumarol/phenprocoumon; apixaban/rivaroxaban/clopidogrel/aspirin; gliclazide/repaglinide; cyclosporine/tacrolimus; arnica/calendula/feverfew).
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 names eleven interactions and the section is correspondingly 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 the ER Therapeutic Protocol bullets.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	The trial-validated extract dose, the tea regimen behind the glycemic results, and timing — the three ER bullets that carry actual trial regimens.
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 provides far 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.	🟢	“500 mg three times daily”, “3 g in 150 mL, three times daily” and “Evening, 30–60 min before bed” with ER-sourced sublines.

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	🟢	Glycemic/lipid (8 weeks), sleep quality (2–4 weeks) and anxiety (2–4 weeks) — the three aspects named in the ER Practical Considerations time-to-effect bullet.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered by pooled effect magnitude: HbA1c SMD −0.90, sleep-quality SMD −0.73, then the smaller HAM-A difference.
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 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.	🟢	Sublines paraphrase the ER clause verbatim in substance (“required the full eight weeks of dosing”, “appeared by two weeks and consolidated by four”).
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 data, so the section is retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All 21 items correspond to the ER’s benefit headings across the four tiers.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present and populated in tier order.
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 ER heading reduced to a lower-case descriptor; the only additions are the ER’s own ⚠️ Conflicted flags rendered as “(conflicted)” per 4.4.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No ER parenthetical (scales, sample sizes, mechanism glosses) survives into the benefits list.
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 contain ER items.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All ten items correspond to the ER’s risk headings.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present.
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 ER heading reduced to a descriptor; no incidence figures or case-report detail.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	ER glosses such as “(a sudden whole-body allergic reaction)” and “(liver-toxic compounds …)” are removed.
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 states no risk reaches Medium; [risks_medium] carries style="display: none" with no empty-state text.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Rows and cadence come from the ER Monitoring Protocol & Defining Success section.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All eight ER biomarker rows present with targets and rationale verbatim: HbA1c, fasting glucose, fasting insulin, lipid panel, hs-CRP, INR, ALT and AST, Compositae-specific IgE.
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.	🟢	Reproduces the ER’s ongoing-testing paragraph: symptom score at 2 and 4 weeks, INR at 1 and 2 weeks, panels at 8–12 weeks then every 6–12 months.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Taken from the ER’s “Qualitative markers worth tracking alongside the labs” list.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All six ER qualitative markers present, with trailing explanatory clauses and the citation stripped.

Issues 18/09/2026 10:10

Pass rate 100.00%. No issues found.