Audit: QRS - Passionflower for Health & Longevity

Audit conducted on 22/09/2026 19:04 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 94
Passed 84
Failed 0
N/A 10
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 doses (200–800 mg, 260–500 mg, 250–400 mg), windows (30–90 min, 1–2 weeks, 12 months) and biomarker ranges trace verbatim to ER lines 351–353, 359, 402, 428–438.
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 report is uncontrolled” (time_3_sub) and “benefit for long-standing anxiety is unsettled” (at_a_glance) mirror ER lines 189 and 468.
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 stays in Contraindications; “Sleep gains are modest” matches ER “lengthened measured sleep modestly” (line 466).
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. 🟢 Benefits, Risks, Contraindications and Interactions each draw from their matching ER section only.
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, author names or brands appear anywhere in the QRS.
1.6 The QRS does not introduce new attributions. 🟢 “the regimen used in the surgical and dental trials” is the ER’s own attribution (line 353); the Campinas/Sergipe naming was dropped rather than added to.

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 Conclusion is carried through.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Numeric targets and dose ranges alongside plain-language framing.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Items are stated as facts and ranges, not instructions.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Contraindications and interactions are listed as populations and agents, not as directives.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No “recommend”, “advise” or “should” constructions in the sheet’s own voice.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns or imperatives.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical terms appear only where the ER itself uses them (CYP3A4, QTc) and outside the lede.
2.8 Information is presented in a concise and very compact manner 🟢 Tiers collapsed to single semicolon-separated lines; gate items are bare noun phrases.
2.9 It DOES NOT address the reader directly 🟢 Confirmed across all populated 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. 🟢 Monitoring targets and self-test framing assume an 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. 🟢 Electrocardiogram, red-cell magnesium and 14-night sleep-efficiency tracking are retained.
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 down to a general-population “just try it” 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. 🟢 Product-quality failure and sedative stacking are surfaced prominently, matching ER lines 468–470.
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 in the QRS.
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. Direct quotes from sources are exempt. 🟢 “capsules, liquid extract and tea” are formal dosage forms carried from ER line 39; no “pill”, “shot” or “by mouth” phrasing.

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 byte-identical to [qrs_template] (QRS lines 440, 477, 519, 539, 553, 574, 593, 597–599, 690).
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All 38 template variable names present; marker_#/qualitative_item_# expanded to 7 and 5 numbered instances.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 The three website= spans (evidence_review, audit, full_review) and all CSS 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 that feeds the QRS is empty.
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 European dry-extract protocol”, “Situational single-dose protocol”, “Best time of day” and all nine interaction labels are verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Biomarker names, tier labels and interaction labels all match the ER wording.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji characters in the file; the ER’s 🟩/🟥/🟨 and ⚠️ 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. 🟢 Every section is at its mandated minimum: tiers collapsed to one line each, gate items reduced to bare facts, protocol subs trimmed of monograph and attribution text.

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. 🟢 QRS lines 2–14, immediately after the doctype 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 “—” 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. 🟢 Fully enclosed in the 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:02" is quoted, correctly so because the value contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 Line 4: er_filename: passionflower_2026-0825-1300_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]” 🟢 Line 5: qrs_prompt_version: 26.9.22, matching the QRS.md 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-0922-1857.
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 with 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” — 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 file on disk exactly.
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. 🟢 No stray whitespace or unnecessary quoting on any of the nine keys.

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., &amp; for &) 🟢 “Passionflower for Health & Longevity - Quick Reference Sheet” (line 22), ampersand correctly encoded.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 “Passionflower for Health & Longevity” (line 417).
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 2026-0922-1857 → “09/22/2026” (line 421).
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 “Opus 5” (line 425).
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 block (lines 415–428) is identical to the template apart from the three variables.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] opens by saying what the intervention is — its kind (e.g., dietary supplement, prescription medication, peptide, plant, procedure, practice) — and what it is used for, in plain language, before any verdict on the evidence 🟢 Opens “Passionflower is a dried plant preparation, sold as capsules, liquid extract and tea for nervous tension and poor sleep.”
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Covers the single-dose use case, sleep magnitude, the unresolved anxiety question, sedative stacking and product quality — the five beats of ER lines 466–470.
7.3 [at_a_glance] is no longer than 70 words 🟢 65 words.
7.4 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Kind/use from ER line 39; remaining four claims from ER Conclusion lines 466–468.
7.5 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms; “calming”, “sedates”, “dried plant preparation” are lay-register.
7.6 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial names, years, n or p-values.
7.7 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 Magnitude is given qualitatively (“modest”) only.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All seven items map to the ER “Populations who should avoid Passionflower” list (ER lines 323–329).
8.2 [stop_items] represent the Contraindications from the ER 🟢 7 of 7 ER avoid-list populations present, none added.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 QRS lines 542–548, each a discrete <li>.
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. 🟢 Leading “People with…” / “Anyone…” scaffolding stripped; no dashes introduce trailing clauses.
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). 🟢 QTc 470 ms, AHI above 15 events per hour, Child-Pugh Class C, “moderate-to-severe”, and the 48-hour window 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 inside parentheses in its avoid list.
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 such populations and the section is correctly 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 nine items map to ER lines 301–319.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 9 of the ER’s 10 interaction bullets present; monoamine oxidase inhibitors correctly excluded because they sit in Contraindications.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 QRS lines 556–564, each a discrete <li>.
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 mechanism sentence and every “Mitigation is…” clause from the ER is stripped; only label plus drug list 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). 🟢 All named example drugs retained for benzodiazepines/Z-drugs, opioids, sedating OTC medicines, CYP3A4 substrates and sedative supplements.
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 inside parentheses in its interaction list.
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 ten 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 map to ER “Therapeutic Protocol” bullets (lines 351, 353, 359).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Daily dose range, situational single dose and timing are the three executable aspects; the remaining ER bullets are comparative or non-actionable.
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 three or more actionable aspects and 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 200–800 mg, 260–500 mg and “Evening” all trace to the ER.

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 🟢 Situational anxiety and sleep/daily calm from ER line 402; sustained sedative dose reduction from ER lines 187–189.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 High (situational anxiety) → Medium (sleep and daily calm) → Low (benzodiazepine tapering), matching the ER benefit tiers.
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 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. 🟢 All nine spans populated; “30–90 minutes”, “1–2 weeks” and “12 months” all appear in the 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 The ER provides time-to-effect information (line 402), so the section is correctly retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All eight benefit subheadings from ER lines 157–207 are represented.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present and populated (QRS 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. 🟢 Only the ER subheadings survive; every Magnitude line and mechanistic paragraph is dropped.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses appear in any benefits span.
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 tiers have ER content, so no span needed hiding.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All eight risk subheadings from ER lines 231–281 are represented.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present and populated (QRS lines 576–587).
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. 🟢 Only the ER subheadings survive; the ⚠️ Conflicted markers and Magnitude lines are dropped.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses appear in any risks span.
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. N/A All four tiers have ER content, so no span needed hiding.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Rows map to the ER “Monitoring Protocol & Defining Success” table (lines 430–438).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All 7 ER biomarkers present with ER target ranges and “Why Measure It?” text carried verbatim.
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. 🟢 QRS line 684 reproduces the ER cadence sentence (line 428) in full.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Items map to the ER “Qualitative markers worth tracking” list (lines 442–446).
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All 5 ER qualitative markers present and verbatim (QRS lines 693–706).

Issues 22/09/2026 19:04

Pass rate 100.00%. No issues found.