Audit: QRS - Psyllium Seed Husks for Health & Longevity

Audit conducted on 21/09/2026 02:56 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.	🟢	Protocol cells trace to ER lines 369/371/373/395; time-to-effect cells to ER line 432; benefit and risk tiers to the ER Expected Benefits and Potential Risks & Side Effects headings; monitoring rows to the ER biomarker table (lines 466–474).
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.	🟢	marker_9_why keeps the ER’s “theoretically reduced by bile-acid binding”; no ER hedge is converted to a firm statement.
1.3	The QRS never strengthens an ER claim (e.g., “not formally studied” → “not required”) or softens one (e.g., “do not use during pregnancy” → “use with caution during pregnancy”).	🟢	Contraindications remain contraindications and interactions remain interactions; no avoidance statement is downgraded to caution.
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 11 caution_items map one-to-one to the ER Key Interactions & Contraindications bullets; all 5 stop_items map to the ER “Populations who should avoid Psyllium Seed Husks” list. Nothing is drawn from Risk-Modifying Factors or Benefit-Modifying Factors.
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 contains no PMIDs, citations, author names, NCT identifiers or brand names.
1.6	The QRS does not introduce new attributions.	🟢	No attributions of any kind appear in the QRS.

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.	🟢	The lede reuses the ER Conclusion register (“consistent rather than large”, “present only while it is taken”).
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Quantified doses, windows and targets throughout, expressed without alarmism or promotion.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Cells are declarative statements of what trials used and what is monitored, not instructions.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	monitoring_cadence and the protocol subs are phrased descriptively (“Taken immediately before meals”, “rechecked at 8 weeks”), with no imperatives.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No occurrence of “recommended”, “should”, “advised” in the QRS’s own voice.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns appear anywhere in the document.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Retained technical terms carry the ER’s own glosses (“paralytic ileus (a temporarily paralysed bowel)”, “dysphagia (difficulty swallowing)”).
2.8	Information is presented in a concise and very compact manner	🟢	Gate and tier items are reduced to noun phrases; no item carries a trailing rationale clause.
2.9	It DOES NOT address the reader directly	🟢	Confirmed: no “you”/”your” anywhere in the source.
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.	🟢	Nine monitored biomarkers with functional targets and a titration-aware protocol address exactly this 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.	🟢	Split pre-meal dosing 2–3× daily and long-term biomarker tracking are presented without hedging about convenience.
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.	🟢	Functional rather than conventional reference ranges are used (e.g., LDL < 70 mg/dL, HbA1c 4.8–5.4%).
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 lede states the glycemic effect appears “where control has already slipped”, and marker_4_why notes fasting glucose “predicts who benefits at all”.
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; the title uses “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)”; “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.	🟢	Route and drug-class terms are formal throughout: “co-administered oral medications”, “Over-the-counter medications”, “Antidiabetic drugs”, “narrow-therapeutic-index oral drugs”. No lay route phrasing on any surface 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 heads, tier labels and column headers are byte-identical to [qrs_template].
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 38 template span names are present; the repeatable marker_#_* and qualitative_item_# patterns are instantiated as marker_1–marker_9 and qualitative_item_1–qualitative_item_5.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	A structural diff against [qrs_template] with variable content masked shows differences only inside data-qrs-var spans; the website="evidence_review", website="audit" and website="full_review" spans, the CSS block and the footer disclaimer 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 source ER section mapped to the QRS is empty; every tier, gate, protocol and monitoring source carries content.
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.	🟢	action_1/2/3_label reproduce “Standard dose”, “Split dosing before meals” and “Formulation”; all 11 caution_items reproduce the ER interaction bold labels.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	time_#_labels (“Lipid changes”, “Glycemic effects”, “Bowel effects”) are taken from the ER Practical Considerations time-to-effect bullet; marker names match the ER biomarker table verbatim.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji in the QRS; the ER’s “⚠️ Conflicted” markers are correctly dropped and evidence strength is carried by the tier labels and CSS palette.
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 reduced to its minimum permitted by the section-specific rules: gate and tier items are bare noun phrases, monitoring why cells are single clauses, and the lede is 57 of the 60 permitted words. No further condensation is available without violating 9.2, 14.2 or 15.2.

---

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 comment opens on line 2, immediately after <!doctype html> on line 1, and closes on line 14 before any other content.
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 --- on line 3 and closing --- on line 13; the preamble “QRS — Metadata (invisible, parsed by audit tooling)” sits before the opening delimiter.
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 and not duplicated anywhere in <head> or <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: psyllium_seed_husks_2026-0921-0008_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.11, matching the version badge of [qrs_prompt].
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-0921-0250, correctly formatted.
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” is nickname plus version with no trailing qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the on-disk filename psyllium_seed_husks_2026-0921-0008_Opus_QRS.html.
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 nine keys; no stray whitespace and no 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 &)	🟢	Line 22: “Psyllium Seed Husks for Health & Longevity - Quick Reference Sheet”, matching ER canonical_topic with the ampersand encoded.
6.2	[header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &)	🟢	Line 417: “Psyllium Seed Husks for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “09/21/2026”, the correct reformatting of 2026-0921-0250.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “Opus 5”, matching the frontmatter value.
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 header carries only title and the template subline; no alternate-names line or badge was added.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Condenses ER line 508: mechanism, the four reproducible effect domains, and the maintenance-only nature of the effect.
7.2	[at_a_glance] is no longer than 60 words	🟢	57 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Gel-forming/survives to stool, lower cholesterol, blood sugar “where control has already slipped”, stool softening and firming, small systolic drop, and “consistent rather than large” each trace to a distinct clause of ER line 508.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “the upper blood pressure number” is used in place of “systolic”, and “undigested” in place of “non-fermented”.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial, author, year or sample size is named.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numbers of any kind appear in the lede.

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 Psyllium Seed Husks” list, ER lines 335–345.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All five ER avoidance bullets are present, in ER order, with none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Five <li> elements inside the stop_items span, lines 567–582.
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.	🟢	The em-dash clause on ER line 343 (“— fluid-restricted dialysis patients, bed-bound individuals…”) is stripped, as is the “including post-stroke and advanced Parkinson’s disease” elaboration on line 341. No dashes remain in any item.
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).	🟢	“(a temporarily paralysed bowel)” and “(difficulty swallowing)” retained; the 240 mL threshold and the four-week post-surgery window 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 avoidance list contains 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 five such populations, and the section is correspondingly populated rather than empty.
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 lines 313–333.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All 11 ER interaction bullets are present in ER order; none duplicates a contraindication.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Eleven <li> elements inside the caution_items span, lines 590–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.	🟢	Each item is the bare ER bold label; every mitigation clause (“two-hour separation”, “rechecked after eight weeks”) and all mechanistic rationale are stripped.
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 example drug list is retained verbatim, including “(insulin, sulfonylureas such as glipizide, glimepiride)” and “(vitamin D, vitamin K, calcium, zinc, iron)”; only the non-qualifying lay definition of the low-FODMAP diet is trimmed for budget.
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 interaction bullets contain 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 documents 11 such interactions and the section is populated accordingly.
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 derive from the ER Therapeutic Protocol section, lines 369–395.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose, split pre-meal timing and formulation are the three decision-bearing levers in that section; the remaining bullets (half-life, alternatives, polymorphisms, sex, age) are informational rather than 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 more than three actionable aspects, so 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 cells carry ER-derived content; no placeholder text 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	🟢	Lipid, glycemic and bowel windows are the three the ER quantifies at line 432.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Order matches the ER Expected Benefits High-tier ordering: LDL/apoB, glycemic control, constipation relief.
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.	🟢	“3–4 weeks / Plateau by eight weeks”, “At least 8 weeks / Trials under 50 days often miss them” and “12–72 hours / Stool form responds within days” all trace to ER lines 432 and 478.
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, so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All four tiers mirror the ER Expected Benefits sub-headings, lines 151–221.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans are present and populated.
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 tier is a semicolon-separated list of the ER sub-headings alone; no magnitude, mechanism or citation is carried over.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	The ER benefit headings contain no parentheticals, 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.	N/A	All four ER benefit tiers contain items, so no span needs hiding.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All four tiers mirror the ER Potential Risks & Side Effects sub-headings, lines 243–289.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans are present and populated.
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 tier lists the ER sub-headings only; the “⚠️ Conflicted” markers and all magnitude data are stripped.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content appears in any risk item.
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 ER risk tiers contain items, so no span needs hiding.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Rows derive from the ER Monitoring Protocol & Defining Success biomarker table, lines 464–474.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All nine ER biomarkers are present in ER order: LDL Cholesterol, Apolipoprotein B, HbA1c, Fasting Glucose, Blood Pressure, Serum Ferritin, Thyroid Stimulating Hormone, Serum Lithium, Serum 25-Hydroxyvitamin D.
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.	🟢	Condenses ER line 462: baselines, 8-week lipid/BP recheck, 12-week HbA1c, 4–8-week drug levels, then 6–12 monthly with annual ferritin.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Sourced from the “Qualitative markers worth tracking alongside the laboratory values” list, ER lines 476–486.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All five ER qualitative markers are present in ER order, mapped to qualitative_item_1 through qualitative_item_5.

Issues 21/09/2026 02:56

Pass rate 100.00%. No issues found.