Audit: QRS - Slippery Elm for Health & Longevity
Audit conducted on 21/08/2026 05:33 using AI4L / Opus 5
Summary
| Items | Count |
|---|---|
| Total | 93 |
| Passed | 85 |
| Failed | 0 |
| N/A | 8 |
| 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 protocol value, tier item, gate item, marker row and cadence string traces to ER text; spot-checked against ER lines 231-248, 266-292, 304, 324, 352-367. |
| 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. | 🟢 | “weaker evidence, without comparison groups” mirrors ER “had no comparison group”; “No established target range” carried verbatim into marker_6_target. |
| 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 remains an absolute contraindication; the sore-throat claim uses the ER’s own “fast, real” wording; no caution is upgraded or downgraded. |
| 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. | 🟢 | Benefit- and Risk-Modifying Factors are not surfaced anywhere; gates draw only from Key Interactions & Contraindications. |
| 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 identifiers or brand names appear anywhere in the QRS. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions of any kind are 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. | 🟢 | Matches the ER’s sober, attribution-sceptical register. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Expert, objective and data-driven while still giving a clear, actionable decision frame. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Descriptive throughout; no imperative clinical instruction. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | Passive, descriptive constructions (“Whisked into…”, “Symptoms reassessed at 4 weeks”) rather than directives. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | Presents values and findings; no “recommended”, “advised” or “should” phrasing. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns present anywhere in the file. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Plain language throughout; the few technical terms retained (achalasia, ileus, hs-CRP) are ER-sourced biomarker or gate terms that cannot be replaced without losing the decision content. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | All cells are short, stripped phrases; gate items carry only the key fact plus its drug list. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed - no direct address. |
| 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 is pitched at readers deciding whether and how to apply the intervention. |
| 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. | 🟢 | Split three-times-daily dosing, two-hour medicine separation and a six-marker panel all assume a willing, effortful 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 written for a general readership; assumes lab access and protocol adherence. |
| 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 explicitly states “it is not a longevity intervention”, which is exactly the audience-specific signal. |
| 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 appear; the only such framing is “longevity intervention”. |
| 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. | 🟢 | “oral medicines”, “oral antidiabetic and lipid-lowering medicines”, “adverse”; no consumer-grade substitutes. |
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 table column headers match the template byte-for-byte. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | Diff against the template shows every template span present; the only additions are the repeated marker_#* and qualitative_item# instantiations the template defines. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | The three non-audited spans (website=”evidence_review”, website=”audit”, website=”full_review”) are untouched. |
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 ER section mapped into the QRS is empty, so no empty-state phrasing is 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. | 🟢 | All six gate labels and all three protocol labels reproduce the ER’s bold labels verbatim (ER lines 231-241, 268-272). |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Marker names and gate labels are ER strings; no invented or abbreviated label. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji characters present in the file. |
| 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 stays inside its template slot: three protocol cells, three time cells, four benefit and four risk tiers, one gate row, one monitoring table, one qualitative list. Content is condensed, not extended. |
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. | 🟢 | The metadata comment opens at line 2, immediately after <!doctype html>. |
| 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 — at lines 3 and 13 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 and not duplicated on the sheet. |
| 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. | 🟢 | All values trimmed; only duration 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: slippery_elm_2026-0825-0346_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 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-0821-0524 in YYYY-MMDD-HHMM form. |
| 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 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]” | 🟢 | 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 number only; no additional qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | qrs_filename matches 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. | 🟢 | Confirmed - 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., & for &) |
🟢 | |
| 6.2 | [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &) |
🟢 | header_topic is the canonical_topic with & encoding. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | 08/21/2026, derived from qrs_creation_date 2026-0821-0524. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | header_subline_model is “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 carries only the template’s date, ER link, AI4L link and model name. |
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 into a decision-shaped summary: what it does, how good the evidence is, what it is not, and the one real cost. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 53 words, within the 60-word cap. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Each clause maps to a distinct ER Conclusion passage (ER lines 385, 389) plus the mechanism statement at ER line 101. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms; “demulcent”, “mucilage” and “viscous fiber” are all avoided in favour of “gel”. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial names, years, sample sizes or p-values. |
| 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 |
🟢 | All four items come from the ER’s “Populations who should avoid Slippery Elm” list (ER lines 245-248). |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All four ER avoidance populations are represented, none added. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Four <li> elements inside the stop_items 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. | 🟢 | Rationale clauses stripped: “given the historical use of bark preparations to induce abortion…” reduced to “Pregnancy, at any stage”. |
| 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). | 🟢 | “lumen under about 10 mm” threshold and the “within 30 days” surgical window both preserved; only the redundant “on endoscopy” method note was trimmed. |
| 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 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 section is populated, and the ER does name populations that should avoid the intervention. |
| 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 six items come from the ER’s bulleted interaction list (ER lines 231-241). |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | All six ER interaction bullets present; none duplicates a contraindication. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Six <li> elements inside the caution_items 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. | 🟢 | Status words and mechanistic trailing sentences stripped; e.g. “…may be under-absorbed if swallowed with the gel, risking loss of effect” removed. |
| 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). | 🟢 | Every named example drug list is preserved intact: levothyroxine/warfarin/digoxin/lithium/phenytoin, glipizide/glibenclamide, ibuprofen/naproxen, vitamins A/D/E/K. |
| 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 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 section is populated, and the ER does name interactions that change how the intervention is used. |
| 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 actions derive from the ER Therapeutic Protocol section (ER lines 268-272). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | The powder, lozenge and tea protocols are the ER’s three delivery-format protocols and its only dose-bearing bullets. |
| 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 distinct actionable protocols, so no set is unused. |
| 10.4 | All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. |
🟢 | All nine action fields carry ER-derived content; subs add the ER’s timing and split-dosing notes (ER lines 278, 282). |
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 | 🟢 | Throat relief, gut symptom change and the planned reassessment window are the ER’s three time-anchored effect statements (ER lines 304, 324). |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered by benefit magnitude: throat relief (Medium tier) first, gut symptoms (Low tier) second, then the general reassessment point. |
| 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 aspects exist in the ER, so no set is unused. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | All nine time fields carry ER-derived content. |
| 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 does provide time-to-effect information, so the section is retained. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | Tiers and items match the ER Expected Benefits headings exactly. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four benefit spans present and correctly named. |
| 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’s benefit headings are carried; no magnitudes, p-values or study notes. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | The ER’s benefit headings contain no parenthetical content, and none was introduced. |
| 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. | 🟢 | The ER has no High-tier benefit, and benefits_high carries style=”display: none” with no empty-state text. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | Tiers and items match the ER Potential Risks & Side Effects headings exactly. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four risk spans present and correctly named. |
| 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’s risk headings are carried; the “Magnitude:” paragraphs are omitted. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical content carried through. |
| 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 has no High-tier risk, and risks_high 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 |
🟢 | The table reproduces the ER Monitoring Protocol & Defining Success biomarker table (ER lines 352-359). |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All six ER biomarkers listed: ferritin, hs-CRP, fecal calprotectin, TSH, serum 25-hydroxyvitamin D, urinary lactulose-to-mannitol ratio. |
| 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 reproduces ER line 350: 4 weeks, 6-8 weeks, 3 months, then every 6-12 months. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Drawn from the ER’s qualitative-marker list (ER lines 363-367). |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All five ER qualitative markers listed; only the trailing em-dash clause on the fifth was stripped. |
Issues 21/08/2026 05:33
Pass rate 100.00%. No issues found.