Audit: QRS - Passionflower for Health & Longevity

Audit conducted on 20/08/2026 14:27 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 93
Passed 83
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. 🟢 Every gate item, tier item, protocol cell, marker row and qualitative item traces to a specific ER passage (ER 300–328, 348–370, 429–445).
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. 🟢 At-A-Glance keeps “unsettled” (ER 467 “remains unsettled”); no ER hedge is dropped or replaced.
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”). 🟢 Avoidance populations (ER 320–328) stay in the Contraindications gate; “Caution”/”Monitor” items stay in the Key Interactions gate.
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. 🟢 Nothing from ER Benefit-Modifying Factors (209–221) or Risk-Modifying Factors (283–295) appears in the gates or the Risks 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. 🟢 The QRS carries no PMIDs, no NCT identifiers, no author names and no brand names; every drug named is a generic listed in ER 300–318.
1.6 The QRS does not introduce new attributions. 🟢 ER attributions (EMA monograph, Campinas/Sergipe groups, San Raffaele) are dropped rather than replaced; no new source is named.

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. 🟢 Flat, measured, non-promotional register matching the ER throughout.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Tiered benefits/risks and numeric targets carry the data; the At-A-Glance states both what works and what does not.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Protocol cells describe the regimens used, they do not instruct.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No imperatives in QRS-authored content; the only imperative is the fixed template disclaimer in the footer.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No occurrence of “recommend”, “advise”, “should” or “we suggest” in populated spans.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronoun occurs anywhere in the populated content.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Retained technical terms (apnea-hypopnea index, Child-Pugh Class C, CYP3A4) are decision-gate qualifiers required verbatim by items 8.5/9.5.
2.8 Information is presented in a concise and very compact manner 🟢 Gate and tier items are stripped to the key fact; magnitudes, mechanisms and mitigations are all removed.
2.9 It DOES NOT address the reader directly 🟢 Confirmed by a full-file scan for you/your/we/our/us — no match.
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 willingness to read an ECG target, an ISI score and a chemotype-aware sourcing rule.
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. 🟢 Monitoring cadence (2 weeks, 4 weeks, quarterly, annual liver enzymes) assumes sustained 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. 🟢 Density and biomarker detail are well beyond a general-population handout.
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 Benefits tiers preserve the ER’s narrow, honest weighting and the At-A-Glance leads with the situational-dose signal, which is the one relevant to same-day functioning.
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. 🟢 “anti-aging” does not occur; the header carries the canonical “for Health & Longevity”.
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. 🟢 “dry extract”, “sedating over-the-counter medicines”, “hypersensitivity”, “psychomotor impairment” — no consumer-grade substitutions.

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 present verbatim at lines 445, 491, 536, 617, 643, 760, 562, 584, 539/543/549/554, 647–649.
3.2 All “” from the [qrs_template] are present in the the QRS. 🟢 60 named spans present, covering every variable region the checklist references; the non-variable template spans (website=”evidence_review”, website=”audit”, website=”full_review”) are also intact.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 The three website=”…” spans and the footer disclaimer are untouched template content.

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 drawn on by 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. 🟢 Protocol labels and all nine Key Interaction labels reproduce the ER bold labels verbatim (ER 300–318, 350–358).
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 No label is shortened or coined where the ER supplies one.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 Codepoint scan of the whole file returns no character above U+2100; the ER’s 🟩/🟥/🟨/⚠️ 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 condensed to the minimum the fidelity items permit: magnitudes, mechanisms, mitigations, attributions and parenthetical glosses are all stripped.

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 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. 🟢 Enclosed in an HTML comment; no metadata value is echoed on the page except the required header date and model.
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, because it 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.7.02, matching QRS.md.
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-0820-1411.
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” — 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]” 🟢 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. 🟢 Re-verified across all ten keys; no stray whitespace or unnecessary quoting.

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 &) 🟢 Line 22: “Passionflower 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., &amp; for &) 🟢 Line 417: “Passionflower for Health & Longevity”, matching ER frontmatter line 8.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 Line 421: “08/20/2026” from qrs_creation_date 2026-0820-1411.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Line 425: “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. 🟢 The ER’s “Also known as” line (ER 31) is correctly omitted; nothing beyond the template subline is present.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Compresses ER 465–469 into the four decision-relevant points: situational effect, sleep, unresolved chronic anxiety, additive sedation plus product quality.
7.2 [at_a_glance] is no longer than 60 words 🟢 55 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each clause maps to a distinct sentence in ER 465–467.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 Plain-language throughout (“a standard sedative drug”, “coordination, reaction speed and memory”); no acronym and no clinical-register term.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial name, year, n or p-value.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 “lengthens modestly” replaces the ER’s 23.1-minute figure; no effect size appears.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Sourced from the “Populations who should avoid Passionflower” list, ER 320–328.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All seven ER avoidance populations present, in ER order, none added.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Seven <li> elements, lines 565–579.
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. 🟢 Each item reduced to the condition alone; no dash-introduced trailing clause occurs in the span.
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 above 470 ms”, “(apnea-hypopnea index above 15 events per hour)”, “(Child-Pugh Class C)” and the 48-hour window are 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’s avoidance list uses no ranking notation inside parentheses.
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 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 🟢 Sourced from ER 300–318.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Nine of the ER’s ten interaction bullets appear; “Monoamine oxidase inhibitors” is correctly omitted because it is already a Contraindication.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Nine <li> elements, lines 587–607.
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 “Caution;”/”Monitor;” rationale and every “Mitigation is …” clause is stripped; no dash-introduced clause 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 five ER example-drug lists are carried through intact (benzodiazepines/Z-drugs, opioids, sedating OTC, CYP3A4 substrates, 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’s interaction bullets use no ranking notation inside parentheses.
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 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 trace to ER Therapeutic Protocol bullets at lines 350, 352 and 358.
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 parameters; the remaining ER bullets are contextual or negative findings.
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 more than three, 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 carry ER-derived content; no placeholder remains.

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 onset, sleep/daily-calm onset and minimum useful trial period — the three facts in ER line 401.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Situational anxiety (High tier) first, sleep and daily calm (Medium tier) second, then the derived trial-period floor.
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. 🟢 All nine spans populated from ER line 401.
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 a dedicated “Time to effect” bullet, 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 items map to ER benefit headings at lines 156, 164, 170, 176, 184, 190, 196 and 204.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present, lines 538, 541, 547, 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 item is the ER heading alone; every Magnitude: line is dropped.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses occur 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 carry items in the ER, so none needs hiding.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All eight items map to ER risk headings at lines 230, 238, 244, 252, 258, 264, 270 and 278.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present, lines 619, 622, 628, 635.
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 alone; the “⚠️ Conflicted” markers and all 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 occur 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 carry items in the ER, so none needs hiding.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Rows and cadence taken from ER Monitoring Protocol & Defining Success, lines 427–437.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All seven ER table rows present — QTc, potassium, red-cell magnesium, ALT, ISI, GAD-7, sleep efficiency — with targets and rationales 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. 🟢 Lines 750–754 reproduce the ER’s ongoing-monitoring schedule (2 and 4 weeks, quarterly, conditional ECG, annual liver enzymes).

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Taken from the qualitative-marker list at ER 439–445.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All five ER qualitative markers present verbatim, in ER order.

Issues 20/08/2026 14:27

Pass rate 100.00%. No issues found.

Issues 20/08/2026 14:19

  1. 12.4 / 13.4 — Conflicted flag kept in parentheses: benefits_medium (line 544) and risks_high (line 620) carry “(conflicted)”, but sections 12 and 13 require parenthetical content to be stripped from tiered descriptors — the tier already encodes evidence strength — in explicit contrast to items 8.5 and 9.5, where gate parentheticals are preserved.

Fixes 20/08/2026 14:19

  1. 12.4 / 13.4 — Conflicted flag kept in parentheses: Stripped the “(conflicted)” parenthetical from benefits_medium (“sustained reduction in generalized anxiety (conflicted)” → “sustained reduction in generalized anxiety”) and from risks_high (“Drowsiness and daytime sedation (conflicted)” → “Drowsiness and daytime sedation”), leaving the tier labels to carry the evidence-strength signal.