Audit: QRS - Slippery Elm for Health & Longevity
Audit conducted on 11/12/2026 18:23 using AI4L + evidence-mcp / Unknown
Summary
| Items | Count |
|---|---|
| Total | 97 |
| Passed | 87 |
| 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 claims, magnitudes, labels, and statements match the source ER. |
| 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 ER phrasing (‘weak’, ‘no human data on oral use’, ‘no human data’, ‘indirect evidence’, ‘uncontrolled’, ‘No established target’, ‘in vitro’) is preserved. |
| 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 ER claims are strengthened or softened. |
| 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. | 🟢 | All items remain in their exact ER decision categories. |
| 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 unattested citations, IDs, expert names, or brand names appear; Bristol Stool Chart matches ER line 327. |
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. | 🟢 | Follows the ER’s objective, cautious framing. |
| 2.2 | The tone of the QRS is expert, accessible, objective, and data-driven | 🟢 | Expert, accessible, objective, and data-driven tone throughout. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Reads as an objective reference distillation rather than prescriptive advice. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No medical or clinical advice phrasing used. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | Presents protocol and study findings descriptively without recommending or advising. |
| 2.6 | The QRS never addresses the reader directly — it presents evidence, not guidance | 🟢 | Never addresses the reader directly. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Plain language used where written in QRS voice; technical terms appear only in required verbatim ER labels. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Very compact, scannable presentation. |
| 2.9 | 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. | 🟢 | Tailored to proactive, risk-aware health- and longevity-oriented adults. |
| 2.10 | The target audience is willing to employ lifestyle and behavioral changes as well as follow protocols that may be inconvenient, costly, or require effort. | 🟢 | Surfaces multi-dose slurry preparation, ≥2-hour spacing buffers, and multi-marker lab tracking. |
| 2.11 | 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. | 🟢 | Does not dilute protocol specifics for general-population convenience. |
| 2.12 | 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. | 🟢 | Highlights weak/indirect human evidence and stack-absorption trade-offs relevant to longevity regimens. |
| 2.13 | 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. | 🟢 | Uses ‘longevity’ framing (no ‘anti-aging’ phrasing). |
| 2.14 | 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. | 🟢 | Uses formal clinical/scientific terminology (‘oral medications’, ‘powder mixed with water’, ‘dry capsules’) across all sections including the lede. |
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 Monitoring column headers are unmodified. |
| 3.2 | Every element carrying a data-qrs-var attribute in [qrs_template] is present in the QRS with the same name | 🟢 | All template data-qrs-var attributes are present (with # repeated as 1..5 for markers and 1..4 for qualitative items). |
| 3.3 | Everything outside the data-qrs-var spans — markup, text, styles, comments — is as in the template; spans that no checklist item addresses are left unchanged as well | 🟢 | All markup, CSS, comments, and website spans outside data-qrs-var regions match the template. |
4. Formatting
| # | Description | Result | Comments |
|---|---|---|---|
| 4.1 | An empty ER section never produces visible empty-state text in the QRS: the corresponding region is hidden or left empty. Phrases such as “None documented in human trials to date” or “Not formally studied” appear only where the ER uses them for a fact the QRS carries over. | 🟢 | Empty tiers (High/Medium Benefits and Risks) are hidden with style=”display:none” and empty documented interactions span produces no visible text. |
| 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 Label: bullets carried from the ER use the ER’s bold labels verbatim. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Labels are taken directly from ER headings and bold labels without invention or abbreviation. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji indicators appear anywhere in the QRS. |
| 4.5 | The QRS is designed to render on one A4 page. It fails this item only for one of four things: a trailing clause after a dash, an optional gloss, an example list left untrimmed, or a repetition. Nothing else is cut to fit. | 🟢 | All trailing dash clauses, optional glosses, and multi-example parenthetical lists are trimmed; no repetitions present. |
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 sits in a single HTML comment 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 block is delimited by — opening and closing lines. |
| 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. | 🟢 | Metadata is enclosed in an HTML comment and 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. | 🟢 | All values are trimmed and unquoted except duration: “00:10” which contains a colon. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | er_filename matches slippery_elm_2026-1112-1457_Unknown_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 is 26.11.9, 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) | 🟢 | qrs_creation_date is 2026-1112-1735 (YYYY-MMDD-HHMM). |
| 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 is stated as Unknown. |
| 5.9 | The nickname of the AI is the full name without the version number, with all remaining words joined by hyphens (e.g., Opus, Sonnet, Grok, Gemini-Flash, GPT); when the full name has no version number or is “Unknown”, the nickname equals the full name | 🟢 | Nickname equals full name (Unknown). |
| 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 is stated as Unknown. |
| 5.11 | The full name of the AI consists of the model name (the word or words directly before the version number, leaving out the first if there is more than one, e.g., Claude Opus 5.5 → Opus 5.5), the model version number and the variant (if any) as stated in the system prompt or developer instructions of the creating model, with every word capitalized and without product, effort or pricing names (e.g., Opus X.Y, Sonnet X.Y, Grok X.Y, Gemini X.Y Flash, GPT X.Y), the model name alone when the system prompt or developer instructions name a model without a version number (e.g., Grok), or “Unknown” when neither the system prompt nor the developer instructions of the creating model name a model | 🟢 | Full name is Unknown per model naming rule when no model is named in prompt. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | qrs_filename matches slippery_elm_2026-1112-1457_Unknown_QRS.html. |
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 &) |
🟢 | page_title is ‘Slippery Elm 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., & for &) |
🟢 | header_topic is ‘Slippery Elm for Health & Longevity’. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | header_subline_date is 11/12/2026. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | header_subline_model is Unknown. |
| 6.5 | No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. | 🟢 | No extra header content added. |
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 by defining slippery elm (‘an herbal red-elm inner-bark preparation’) and its uses in plain language before the evidence verdict. |
| 7.2 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Dense, execution-oriented distillation of the ER Conclusion. |
| 7.3 | [at_a_glance] is no longer than 70 words | 🟢 | 69 words (within the 70-word limit). |
| 7.4 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Every clause maps directly to passages in the ER Conclusion and Protocol/Sourcing sections. |
| 7.5 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | Uses plain language throughout with zero acronyms or specialist jargon. |
| 7.6 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial names, years, sample sizes, or p-values cited. |
| 7.7 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No effect sizes, relative risks, or statistical figures cited. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Derived from ER Key Interactions & Contraindications. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | Covers all three populations listed under ‘Populations who should avoid Slippery Elm’ in the ER. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Each item is formatted as an <li> element. |
| 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. | 🟢 | Stripped of mechanistic rationale, study details, and citations; retains only the ER’s ‘no human data’ hedges per 1.2. |
| 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). | 🟢 | All clinical scope qualifiers (‘severe dysphagia’, etc.) are preserved. |
| 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 does not use ranking notation inside parentheses in Contraindications. |
| 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. |
🟢 | Populated with the ER’s three contraindicated populations. |
| 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 | Section is not empty. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Derived from ER Key Interactions & Contraindications. |
| 9.2 | [caution_items] represent the ER’s documented interactions — the items under its “Documented interactions:” label — excluding any that are already listed as Contraindications and any entry phrased as no interaction found | 🟢 | caution_items is left empty since ER Documented interactions lists only ‘None identified’. |
| 9.3 | [caution_theoretical_items] represent the ER’s theoretical interactions — the items under its “Theoretical interactions (inferred from mechanism, not studied in humans):” label | 🟢 | caution_theoretical_items includes all six theoretical interaction bullets from the ER. |
| 9.4 | The ER placeholder “None identified” is never an item: it means that group is empty | 🟢 | ‘None identified’ is not rendered as an item. |
| 9.5 | Individual [caution_items] and [caution_theoretical_items] are formatted as <li></li>. The template’s bold “Theoretical (inferred from mechanism)” sub-heading is the only marker of the second list’s status: no item carries “(theoretical)”, “inferred from” or a mechanism clause | 🟢 | Formatted as <li> elements under the template’s ‘Theoretical (inferred from mechanism)’ sub-heading without redundant per-item theoretical tags. |
| 9.6 | 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. | 🟢 | All trailing clauses after em-dashes, mechanisms, and citations are stripped. |
| 9.7 | 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). | 🟢 | Parenthetical example drug lists are preserved and concisely trimmed to one example each. |
| 9.8 | 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 does not use ranking notation inside parentheses in Key Interactions. |
| 9.9 | If the ER’s theoretical group is empty, the whole Theoretical block — the caution_theoretical span with its sub-heading and list — is hidden with style="display:none", not removed: its spans stay in place, empty. |
N/A | The ER’s theoretical interactions group is not empty. |
| 9.10 | 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. |
🟢 | Section is populated with the ER’s six theoretical interactions. |
| 9.11 | 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, and the Theoretical block is hidden per 9.9. E.g. | N/A | Section is not empty. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Therapeutic Protocol section |
🟢 | Derived from ER Therapeutic Protocol. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from that section | 🟢 | Covers the three primary actionable protocol aspects: traditional slurry dosing, commercial regimens, and timing/medication spacing. |
| 10.3 | If fewer than three distinct actionable implementation aspects are mentioned in the ER, the unused sets are left empty and hidden with style="display:none", not filled with placeholder text or empty-state phrasing. |
N/A | The ER provides three or more distinct actionable implementation aspects. |
| 10.4 | All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from that section. | 🟢 | All three action label/value/sub cells contain accurate, meaningful content from Therapeutic Protocol. |
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 | 🟢 | Covers the three human time-to-effect aspects reported in the ER (acute sore throat, GI symptoms, intestinal barrier permeability). |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered by benefit evidence/magnitude matching the ER Low tier (controlled RCT throat relief first, followed by GI symptom relief and permeability). |
| 11.3 | If fewer than three distinct time-to-effect aspects are mentioned in the ER, the unused sets are left empty and hidden with style="display:none", not filled with placeholder text or empty-state phrasing. |
N/A | Three distinct time-to-effect aspects are present in the ER. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | All three time label/value/sub cells are populated with ER-supported timeframes and context. |
| 11.5 | If the ER provides no information on time to effect at all, the whole Time to effect block (its subhead and all three sets) is hidden with style="display:none", not removed: its spans stay in place, empty. |
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 |
🟢 | Derived from ER Expected Benefits. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | Uses benefits_high, benefits_medium, benefits_low, and benefits_speculative. |
| 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. | 🟢 | Concise bare descriptors matching the ER benefit headings without effect sizes, qualifiers, or citations. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical content included. |
| 12.5 | If a tier (high, medium, low, speculative) has no items, its span is hidden with style="display:none", not filled with “None documented in human trials to date” or similar empty-state phrasing. |
🟢 | Empty High and Medium tiers are hidden with style=”display:none”. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | Derived from ER Potential Risks & Side Effects. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | Uses risks_high, risks_medium, risks_low, and risks_speculative. |
| 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. | 🟢 | Concise bare descriptors matching the ER risk headings without frequencies, qualifiers, or citations. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical content included. |
| 13.5 | If a tier (high, medium, low, speculative) has no items, its span is hidden with style="display:none", not filled with “None documented in human trials to date” or similar empty-state phrasing. |
🟢 | Empty High and Medium tiers are hidden with style=”display:none”. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring Protocol & Defining Success section |
🟢 | Derived from ER Monitoring Protocol & Defining Success. |
| 14.2 | All measurable/quantifiable biomarkers from that section are listed, one table row per marker; the template’s # row is the pattern, repeated with # replaced by 1, 2, 3 … in the data-qrs-var names |
🟢 | Lists all five measurable biomarkers from the ER table using marker_1..5 data-qrs-var rows. |
| 14.3 | [marker_#name] is the marker, [marker#target] its target value or range as given in the ER, [marker#_why] its purpose in a few words; a target the ER does not give is written “Not specified in the ER” | 🟢 | Names and target ranges match the ER verbatim; ‘Why’ cells concisely state each marker’s purpose. |
| 14.4 | [monitoring_cadence] is populated with the monitoring cadence/frequency derived from that section. It is not left with placeholder text or empty. | 🟢 | monitoring_cadence accurately summarizes baseline and follow-up intervals from ER line 316. |
| 14.5 | If the ER names no measurable biomarker, the table is hidden with style="display:none" and the single # row is left as in the template |
N/A | The ER names five measurable biomarkers. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring Protocol & Defining Success section |
🟢 | Derived from ER Monitoring Protocol & Defining Success. |
| 15.2 | All subjective/qualitative markers from that section are listed, one <li> per marker; the template’s # item is the pattern, repeated with # replaced by 1, 2, 3 … |
🟢 | Lists all four qualitative markers as <li> items using qualitative_item_1..4. |
| 15.3 | If the ER names no qualitative marker, the card’s list is hidden with style="display:none" and the single # item is left as in the template |
N/A | The ER names four qualitative markers. |
Issues 11/12/2026 18:23
Pass rate 100.00%. No issues found.
Issues 11/12/2026 18:05
- 1.1 — Post-meal timing phrased as additive: At line 478 (
action_3_sub), “(also taken after dinner with water)” implies an additional dose after30 min after a meal, whereas ER line 272 specifies one dose either 30 minutes after a meal or daily with water after dinner. - 1.1 / 1.4 / 4.5 — Qualitative target repeated as time-to-effect: Lines 503 and 506 (
time_2_value/time_2_sub) import and repeat the Qualitative Assessment checkpoint “Upper-GI comfort … by weeks 1–4” (line 679 / ER line 326) to stateWeeks 1–12, whereas ER clinical data (lines 145 and 300) report GI and upper-GI symptom reductions accruing over 12 weeks. - 1.1 / 11.1 — Unsupported psoriasis timeframe in label: Lines 511 and 514 (
time_3_label/time_3_value) pairIntestinal Barrier Permeability and Plaque Psoriasis Supportwith12 weeks, whereas the ER reports 12-week timing only for intestinal permeability (lines 151 and 300) and gives no timeframe for plaque psoriasis (Brown 2004, line 151).
Fixes 11/12/2026 18:05
- 1.1 — Post-meal timing phrased as alternative: Changed
action_3_subfrom “(also taken after dinner with water)” to “(or one dose daily with water after dinner)” to match ER single-dose wording. - 1.1 / 1.4 / 4.5 — Qualitative target removed from time-to-effect: Changed
time_2_valuefrom “Weeks 1–12” to “Over 12 weeks” and updatedtime_2_subto reflect 12-week clinical GI and stool-consistency shifts without repeating the Qualitative Assessment checkpoint. - 1.1 / 11.1 — Psoriasis removed from time-to-effect label: Changed
time_3_labelfrom “Intestinal Barrier Permeability and Plaque Psoriasis Support” to “Intestinal Barrier Permeability” so the 12-week timeframe applies only to the ER-supported permeability endpoint.
Issues 11/12/2026 17:49
- 1.1 / 1.3 / 7.4 — Unqualified powder-over-capsules claim in lede: Line 439 (
at_a_glance) states “Protocols favor hydrated powder over dry capsules”, omitting the ER’s scope qualifier “for throat and esophageal coating” (ER lines 293, 301, 346) even though capsules are a regulated commercial regimen (ER line 270). - 1.2 / 1.3 — Dropped caution on harms in lede: Line 439 (
at_a_glance) writes “and harms are uncommon” instead of preserving the ER’s cautious phrasing “Documented harms are uncommon” (ER line 346). - 2.7 / 7.5 — Clinical-register term in lede: Line 439 (
at_a_glance) uses formulation-register “hydrated powder” rather than plain language such as “powder mixed with water”. - 1.1 / 11.4 — Conflated onset and duration in time_1: Lines 492 and 495 (
time_1_value,time_1_sub) state “5–30 minutes” and “lasting 30 min”, whereas the ER states throat-pain relief begins “within 5 minutes” and “persists through 30 minutes” / “persists at least 30 minutes” (ER lines 273, 300). - 2.7 / 2.8 / 4.5 / 9.6 — Optional Latin gloss in interactions: Line 570 (
caution_theoretical_items) retains the optional Latin binomial gloss(<em>Althaea officinalis</em>)after “marshmallow root” outside an ER bold label. - 2.8 / 4.5 — Repetitions between cell values and sub-texts: Lines 453/456 (
action_1), 475/478 (action_3), and 492/495 (time_1) repeat “in water” / “into water”, “after meals” / “before bedtime”, and “5” / “30 min” across.valueand.sub. - 1.3 / 14.3 — Omitted standard-reference-range qualifier in Monitoring: Lines 616, 627, and 638 (
marker_1_target,marker_2_target,marker_3_target) strip “(standard reference range)” from the target intervals given in the ER’s Optimal Functional Range column (ER lines 320–322).
Fixes 11/12/2026 17:49
- 1.1 / 1.3 / 7.4 — Unqualified powder-over-capsules claim in lede: Qualified the powder-versus-capsules comparison in
at_a_glanceto specify"for throat and esophagus coating"in line with the ER. - 1.2 / 1.3 — Dropped caution on harms in lede: Restored
"documented harms are uncommon"inat_a_glance(from"harms are uncommon") to preserve the ER’s cautious phrasing. - 2.7 / 7.5 — Clinical-register term in lede: Replaced
"hydrated powder"inat_a_glancewith plain-language"powder mixed with water"while keeping total length at 69 words. - 1.1 / 11.4 — Conflated onset and duration in time_1: Updated
time_1_valuefrom"5–30 minutes"to"Within 5 minutes"andtime_1_subto"Persists at least 30 min in multi-herb tea testing (indirect evidence)". - 2.7 / 2.8 / 4.5 / 9.6 — Optional Latin gloss in interactions: Removed
(<em>Althaea officinalis</em>)after"marshmallow root"incaution_theoretical_items. - 2.8 / 4.5 — Repetitions between cell values and sub-texts: Removed repeated phrases across
.valueand.subinaction_1("into water"),action_3("after meals"/"before bedtime"), andtime_1("5"/"30 min"). - 1.3 / 14.3 — Omitted standard-reference-range qualifier in Monitoring: Appended
"(standard reference range)"tomarker_1_target,marker_2_target, andmarker_3_targetto match the ER’sOptimal Functional Rangetable entries.