Audit: QRS - Hibiscus for Health & Longevity

Audit conducted on 03/08/2026 02:05 using AI4L + evidence-mcp / Opus 4.8

Iterations

Summary

Items Count
Total 91
Passed 86
Failed 0
N/A 5
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, timing, benefit/risk, monitoring, and at-a-glance content traces to ER content.
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. 🟢 Conflicted/speculative framing preserved (e.g., speculative tiers, “conflicted lipid effect”).
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 retain avoidance/threshold force.
1.4 The QRS does not relabel an ER fact under a different decision category. 🟢 Gates derive from ER “Key Interactions & Contraindications”; benefits/risks from their ER sections.
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. 🟢 QRS carries no citations, expert names, or NCT/brand identifiers.
1.6 The QRS does not introduce new attributions. 🟢 No 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. 🟢 Objective, data-driven tone consistent with 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 evidence, not prescriptions.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Disclaimer present; no directive advice.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Content is presented, not recommended.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person address.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain-language phrasing throughout.
2.8 Information is presented in a concise and very compact manner 🟢 Compact cards, gates, and table.
2.9 It DOES NOT address the reader directly 🟢 No “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. 🟢 Framing targets proactive adults.
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 assume willingness to act.
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 a general-population framing.
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 proactive-adult lens.
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 terminology; beverage terms are appropriate.

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, Monitoring table column headers. 🟢 All fixed headings present and unmodified.
3.2 All “…” from the [qrs_template] are present in the QRS. 🟢 Full set of named spans present.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Untouched spans 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. 🟢 No ER source section is empty; no empty-state phrasing required.
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. 🟢 Tier and marker labels match ER.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Marker names and tier labels match ER.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). 🟢 No emoji indicators; “⚠️ Conflicted” markers stripped.
4.5 The QRS is designed to render on one A4 page. 🟢 Content condensed to single-page budget.

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. 🟢 Comment opens at line 2, immediately after doctype.
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 and is not surfaced by any other element on the sheet. 🟢 Enclosed in HTML comment; not rendered.
5.4 All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless required. 🟢 Only “duration” quoted (contains colon).
5.5 The filename of the source ER is stated as “er_filename: [er_filename]”. 🟢 er_filename: hibiscus_2026-0803-0116_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.
5.7 Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]”. 🟢 qrs_creation_date: 2026-0803-0116.
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”.
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 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: [filename of this document]”. 🟢 qrs_filename: hibiscus_2026-0803-0116_Opus_QRS.html.
5.13 All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless required. 🟢 Values clean and consistent.

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. 🟢 “Hibiscus for Health & Longevity - Quick Reference Sheet”.
6.2 [header_topic] is set to the [canonical_topic], with HTML entities encoded as needed. 🟢 “Hibiscus for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]. 🟢 “08/03/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 QRS variant marker. 🟢 Only standard subline present.

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. 🟢 53 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each claim traces to the Conclusion.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge; uses plain-language terms instead. 🟢 Plain-language only; no acronyms.
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 numeric effect sizes.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section. 🟢 Populations drawn from that ER section.
8.2 [stop_items] represent the Contraindications from the ER. 🟢 Pregnancy/lactation, low BP, surgery, liver disease.
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 or content after em/en/hyphen dash. 🟢 No trailing dash clauses.
8.5 Parenthetical qualifiers from the ER bullet — time windows, severity classes, threshold values, clinical staging — ARE preserved, kept concise. 🟢 “systolic below ~110 mmHg”, “stop ≥2 weeks before” preserved.
8.6 When the ER uses ranking notation inside parens that depends on an explanatory phrase, normalize to a plain comma-separated list. 🟢 ER uses no ranking notation here; nothing to normalize.
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. 🟢 Interactions drawn from that ER section.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any already listed as Contraindications. 🟢 Drug/supplement/iron interactions; no population overlap.
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 or content after em/en/hyphen dash. 🟢 No trailing dash clauses.
9.5 Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, thresholds, staging — ARE preserved, kept concise. 🟢 Example drug lists preserved in parens.
9.6 When the ER uses ranking notation inside parens that depends on an explanatory phrase, normalize to a plain comma-separated list. 🟢 ER uses no ranking notation here; nothing to normalize.
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. 🟢 Derived from ER Therapeutic Protocol.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section. 🟢 Standard tea, standardized extract, timing.
10.3 If less than three distinct actionable implementation aspects are mentioned, the unused sets are left empty and made invisible. N/A Three distinct aspects are present.
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 cells populated.

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 two distinct aspects in the ER (BP 2–6 weeks; single serving 1–2 h) are covered; third unused.
11.2 The sets are picked and ordered by the magnitude of the related benefit. 🟢 Blood pressure (high) first, then acute single serving.
11.3 If less than three distinct time-to-effect aspects are mentioned, the unused sets are left empty and made invisible. 🟢 time_3 empty and display:none.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 Both used cells populated from ER.
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 ER provides time-to-effect information.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section. 🟢 Tiers map to ER benefit tiers.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]. 🟢 All four present.
12.3 Items are as concise as possible; no explanations, effect sizes, qualifiers, attributions, citations, study details, or mechanisms. 🟢 Bare benefit names only.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 “⚠️ Conflicted” qualifier stripped from Blood Lipids.
12.5 If no items of a specific sub-section are present the respective 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. 🟢 Tiers map to ER risk tiers.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]. 🟢 All four present.
13.3 Items are as concise as possible; no explanations, effect sizes, qualifiers, attributions, citations, study details, or mechanisms. 🟢 Bare risk names only.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 “⚠️ Conflicted” stripped from liver-enzyme item.
13.5 If no items of a specific sub-section are present the respective is set to display=none. 🟢 risks_high has no items and is set to display:none.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section. 🟢 Table derived from ER Monitoring Protocol.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed. 🟢 All 8 biomarkers present with targets.
14.3 [monitoring_cadence] is populated with the monitoring cadence/frequency derived from the ER Monitoring section. 🟢 Cadence matches ER text.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section. 🟢 Qualitative markers from ER Monitoring Protocol.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed. 🟢 Energy/lightheadedness, sleep, digestion, well-being.

Issues 03/08/2026 02:05

Pass rate 100.00%. No issues found.