Audit: QRS - Echinacea for Health & Longevity

Audit conducted on 18/07/2026 02:27 using AI4L / Opus 4.8

Iterations

Summary

Items Count
Total 91
Passed 84
Failed 0
N/A 7
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 content traces to the ER: protocol doses (ER §Therapeutic Protocol), gates (ER §Key Interactions & Contraindications), benefits/risks tiers, monitoring markers, and qualitative items all match.
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 framing preserved (e.g., “theoretical liver stress”, “results are mixed and uncertain”).
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/softening; pregnancy retained under Contraindications consistent with ER “avoid or use caution” population.
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 and interactions both drawn from the ER §Key Interactions & Contraindications; no modifying factors misclassified.
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, NCT IDs, expert names, or brands introduced in the QRS.
1.6 The QRS does not introduce new attributions. 🟢 No new 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, objective tone consistent with the ER.
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 information without prescriptive instruction.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Content is descriptive; footer disclaimer is fixed template text.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No recommending/advising language in content spans.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person address in content.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain language throughout; technical terms only where they mirror ER labels.
2.8 Information is presented in a concise and very compact manner 🟢 Compact cells and bullets throughout.
2.9 It DOES NOT address the reader directly 🟢 No direct address in content spans.
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 the target 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 detail (split dosing, monitoring) reflects this 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 framed for the general population.
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 and tiers reflect a proactive, longevity-oriented reading.
2.14 The document’s own voice frames usage in longevity terms, not “anti-aging”. Proper names that contain “anti-aging” are quoted verbatim. 🟢 Uses “Health & Longevity”; no “anti-aging” phrasing.
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; “stomach upset” mirrors ER wording (ER §Protocol/§Risk Mitigation).

3. Template Integrity

# Description Result Comments
3.1 The following labels and headings on the QRS are fixed and not modified: card/section headings (“Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”); gate headings (“Contraindications”, “Key Interactions”); tier labels (“High”, “Medium”, “Low”, “Speculative”); Monitoring column headers (“Marker”, “Target”, “Why”). 🟢 All fixed labels/headings present and unmodified.
3.2 All “” from the [qrs_template] are present in the the QRS. 🟢 All template variable spans present, including the hidden empty-state ones.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Unaddressed spans left intact.

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 in a way that requires empty-state phrasing; absent tiers are hidden per 12.5/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. 🟢 Monitoring markers and gate items use ER-sourced labels; interaction gate labels identify the interacting agent per §9.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 No invented labels.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji indicators in content; tiers conveyed via bold labels and CSS.
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 condensed to fit a single sheet.

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. 🟢 Metadata comment is first element (lines 2-14).
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. 🟢 YAML delimited by — / — inside the comment.
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; not rendered.
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. 🟢 Values trimmed; duration “00:04” quoted (contains colon).
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: echinacea_2026-0718-0117_Opus_ER.md
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 prompt version.
5.7 Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” 🟢 qrs_creation_date: 2026-0718-0219
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. 🟢 “Opus” is a single word.
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 4.8
5.11 The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier 🟢 “Opus 4.8” = nickname + version.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename: echinacea_2026-0718-0117_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. 🟢 All values trimmed and correctly quoted.

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”. The [canonical_topic] is HTML-entity-encoded as needed. 🟢 “Echinacea for Health & Longevity - Quick Reference Sheet” with & encoded.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed. 🟢 “Echinacea for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 2026-0718 → 07/18/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 / alternate names line, source-AI attribution, audit date, or QRS variant marker. 🟢 Header contains only title and required subline; no AKA line, badge, or audit date.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Distills the ER Conclusion (line 395): immune support, modest cold benefit, tolerability, quality caveat.
7.2 [at_a_glance] is no longer than 60 words 🟢 59 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each claim maps to the Conclusion.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms or specialist terms.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial citations.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No effect sizes or statistics.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Drawn from the ER “Populations who should avoid or use caution” bullet (line 274).
8.2 [stop_items] represent the Contraindications from the ER 🟢 All six populations represented.
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, elaborations, mechanistic rationale, attributions, citations, study details, or content after em-/en-/hyphen-dash. Just the key fact. 🟢 Rationale stripped (e.g., “(rash and hypersensitivity risk)”, “— a traditional caution” removed).
8.5 Parenthetical qualifiers from the ER bullet — time windows, severity classes, threshold values, clinical staging — ARE preserved, kept as concise as possible. 🟢 Disease examples and age windows preserved (autoimmune diseases, TB/HIV, under 2 / under 12).
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. 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 Stop items are present.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Derived from the ER interaction bullets (lines 262-268).
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Immunosuppressants (a contraindication) correctly excluded.
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, elaborations, mechanistic rationale, attributions, citations, study details, or content after em-/en-/hyphen-dash. Just the key fact. 🟢 Mechanistic rationale stripped; only agent + examples retained.
9.5 Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved, kept as concise as possible. 🟢 Example drugs preserved (midazolam/simvastatin; caffeine/theophylline/clozapine; astragalus/andrographis/elderberry).
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. 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 Caution items are present.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 Doses and schedule sourced from the ER §Therapeutic Protocol (lines 296-306).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Acute treatment, seasonal prevention, dosing schedule.
10.3 If less than 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 Three distinct actionable aspects are present and used.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 All three action sets populated with ER-derived content.

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 🟢 ER supplies two aspects (acute, prevention); both captured.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Acute use ordered before prevention.
11.3 If less than 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. 🟢 Only two aspects exist; time_3 set to display:none and empty.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 Both used time sets are populated from ER §Practical Considerations (line 340).
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.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Tiers mirror the ER §Expected Benefits.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four variables handled.
12.3 Items are as concise as possible. No explanations, elaborations, effect sizes, qualifiers, attributions, citations, study details, or mechanistic explanations. Just the key fact. 🟢 Only benefit headings retained; conflicted flags and magnitudes stripped.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheticals carried through (e.g., “(Anxiety-Reducing)” dropped).
12.5 If no items of a specific sub-section are present the respective is set to “display=none”, not filled with empty-state phrasing. 🟢 ER has no High benefits; benefits_high set to display:none.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Tiers mirror the ER §Potential Risks & Side Effects.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four variables handled.
13.3 Items are as concise as possible. No explanations, elaborations, effect sizes, qualifiers, attributions, citations, study details, or mechanistic explanations. Just the key fact. 🟢 Only risk headings retained.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheticals carried through.
13.5 If no items of a specific sub-section are present the respective is set to “display=none”, not filled with empty-state phrasing. 🟢 ER has no High risks; risks_high set to display:none.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Markers and cadence sourced from the ER §Monitoring Protocol (lines 360-369).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All four biomarkers listed: WBC w/ differential, Eosinophils, ALT & AST, hs-CRP.
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. 🟢 Cadence populated from ER lines 360-362.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Sourced from the ER qualitative-marker list (lines 373-377).
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All five qualitative markers listed verbatim.

Issues 18/07/2026 02:27

Pass rate 100.00%. No issues found.