Audit: QRS - Reishi Mushroom for Health & Longevity

Audit conducted on 15/08/2026 10:14 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 populated span traces to ER text: protocol doses to ER Therapeutic Protocol (lines 358–362), time-to-effect to Practical Considerations (line 415), benefits/risks to the ER H4 headings, markers to the ER monitoring table (lines 447–458).
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.	🟢	ER caution is carried: “theoretical antiplatelet effect” (marker_5_why), “which trials did not find” (marker_6_why), “No established target” (marker_11_target), “Nothing measurable should be expected before two months” (time_1_sub).
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/breastfeeding stays in the STOP gate, not the caution gate; liver disease stays a contraindication; the immune benefit is not upgraded past “modulation of circulating immune cell populations”.
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.	🟢	Contraindications come only from the ER’s “Populations who should avoid” list; Key Interactions only from the ER interaction bullets; no Benefit- or Risk-Modifying Factor is promoted into a gate.
1.5	PubMed IDs, study citations, expert names, clinical trial identifiers (NCT*), and brand names appear in the QRS only if they appear in the source ER for the same fact.	🟢	No PMIDs, NCT IDs, author names, or brand names appear anywhere in the QRS; “Noguchi’s group” is correctly dropped from action_3_sub.
1.6	The QRS does not introduce new attributions.	🟢	No attributions of any kind are present.

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, non-promotional register matching the ER; the ER Conclusion’s own framing (“low-cost addition with a narrow upside and one rare but serious danger”) is carried into at_a_glance.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Marker targets, dose ranges and time windows give the reader concrete handles; language stays neutral and non-alarmist while stating the liver risk plainly.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Content is stated impersonally (“Symptom scores only; objective urinary measures did not change”) rather than as instructions issued to a patient.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperative clinical instructions in the QRS’s own voice; the cadence and qualitative entries restate the ER’s protocol descriptively.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No occurrence of “recommend”, “advise”, “consult” or equivalents in the document body.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere in the rendered content.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms are limited to the marker names, where precision is required; at_a_glance uses “blood fats”, “tiredness”, “dried fungus”.
2.8	Information is presented in a concise and very compact manner	🟢	Gate and tier entries are single noun phrases with no rationale; protocol subs are one clause each.
2.9	It DOES NOT address the reader directly	🟢	Confirmed — no direct address in any span.
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.	🟢	Functional (not conventional-lab) marker ranges, a twelve-marker panel and a 12-week reassessment point address a self-monitoring optimizer.
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.	🟢	Lymphocyte subset testing, 1–2 hour decoction preparation and a repeated liver panel are retained without hedging on effort or cost.
2.12	The document is NOT written for the general population, who are unwilling to employ lifestyle and behavioral changes or follow protocols that may be inconvenient, costly, or require effort.	🟢	No simplification toward a general-population “just take a capsule” framing; three distinct non-interchangeable preparations are kept.
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 leads with the narrow upside and the label-accuracy problem, the two facts that matter most to an optimizer, rather than the traditional-use story.
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 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)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt.	🟢	Clinical registers are used throughout the gates, risks, and monitoring table; the lay wording is confined to at_a_glance, where item 7.4 mandates plain-language substitution.

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 strings match the template byte-for-byte (lines 440, 477, 519, 539, 552, 573, 592, 596–598, 744).
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 38 template variable names are present; the repeatable marker_#_* and qualitative_item_# spans are expanded to marker_1–12 and qualitative_item_1–6 (76 span instances total, all balanced).
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The website="evidence_review", website="audit" and website="full_review" spans, the CSS block, the override stylesheet link and the footer disclaimer are byte-identical to the template.

4. Formatting

#	Description	Result	Comments
4.1	When the source ER section is empty, the QRS uses the ER’s own empty-state phrasing verbatim. Typical phrasings are “None documented in human trials to date” and “Not formally studied”	N/A	No ER section that feeds a QRS span is empty; the single “None documented” in the ER (line 387) sits in Discontinuation & Cycling, which the QRS does not source.
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–3_label reproduce the ER’s bold protocol labels verbatim; gate items reproduce the ER’s bold interaction labels (drug parentheticals trimmed as 9.5 permits); marker names match the ER table column verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	The only derived labels are the three time-to-effect cells, which the ER supplies as one combined bullet with no per-item bold label; they mirror the ER’s own wording (“Immune marker changes”, “urinary symptom and fatigue changes”, “lipid changes”).
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji code points occur in the file; the ER’s 🟩/🟥/🟨 tier markers and ⚠️ Conflicted flags are correctly dropped in favour of the CSS palette and bold tier labels.
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 its minimum form: tier entries are bare noun phrases, gate items carry no rationale, protocol subs are one clause, and the qualitative list keeps the ER’s six entries with trailing justifications trimmed.

---

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.	🟢	Comment opens at line 2, immediately after the doctype at line 1, and closes at 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 “—” at line 3, closing “—” at line 13; the preamble text on line 2 precedes 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.	🟢	It sits entirely inside an HTML comment and no value is echoed into any visible element.
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: "00:03" 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: reishi_mushroom_2026-0815-0651_Opus_ER.md, matching the ER’s own filename frontmatter value.
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 the version badge at the top of 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-0815-1008, correct format.
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 context-window or tier qualifier appended.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9: qrs_filename: reishi_mushroom_2026-0815-0651_Opus_QRS.html, matching 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.	🟢	Re-verified across all nine keys including git_user and git_issue; 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 &)	🟢	Line 22: “Reishi Mushroom for Health & Longevity - Quick Reference Sheet”; matches 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: “Reishi Mushroom for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “08/15/2026”, the correct MM/DD/YYYY rendering of 2026-0815-1008.
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 block (lines 415–428) is the template’s subline only; the ER’s “Also known as” line is not carried over.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Line 433 compresses all four Conclusion paragraphs into form, main finding, weaker signals, the cost/upside/danger trade-off, and product quality.
7.2	[at_a_glance] is no longer than 60 words	🟢	56 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause maps to a distinct Conclusion sentence (ER lines 489, 491, 493) plus the Sourcing and Quality label-accuracy finding (ER line 404).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; the ER’s plain-language substitutions are retained (“blood fats” for lipids, “tiredness” for fatigue, “dried fungus” for the species name).
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial names, years or sample sizes appear.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numbers of any kind appear in the summary.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All six entries come from the “Populations who should avoid Reishi Mushroom” list in that ER section (lines 331–336).
8.2	[stop_items] represent the Contraindications from the ER	🟢	Six ER avoid-list bullets map one-to-one to the six <li> entries at lines 542–547; none added, none dropped.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Six well-formed <li>…</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.	🟢	Leading “Anyone with/People with” phrasing is trimmed and the ER’s trailing clause “rather than evidence of harm” (line 336) is stripped; no dash-trailing content remains.
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 thresholds survive: ALT/AST >1.2× ULN, platelets <100,000/mm³, clotting time >1.5× ULN, the 14-day pre-procedure window, and “(absence of safety data)”.
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 Key Interactions & Contraindications section uses no bare 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 six such populations and the section is correctly populated rather than left 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	🟢	All nine entries derive from the bulleted interaction list at ER lines 309–325.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	The immunosuppressant half of ER line 317 is correctly excluded (covered by the “deliberate immunosuppression” contraindication) and the “Vitamin C: No interaction” bullet is correctly omitted as it changes nothing about use.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Nine well-formed <li>…</li> elements at lines 555–563.
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 ER em-dash gloss is stripped (“— drugs that make the kidney excrete sugar”, “— a fermented shiitake extract”, “— cancer drugs that release the brakes on the immune system”) along with the Caution/Monitor verdicts and consequence sentences.
9.5	Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely).	🟢	All named example drugs survive, with class prefixes trimmed as permitted (gliclazide, empagliflozin, lisinopril, amlodipine, simvastatin, ciclosporin, tamoxifen, paroxetine, pembrolizumab, nivolumab, nattokinase, AHCC).
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 identifies nine such interactions and the section is correctly populated.
9.8	If the section is left empty, an HTML comment inside the [caution_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g.	N/A	The section is not empty.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER Protocol section	🟢	All three cells derive from the ER Therapeutic Protocol bullets at lines 358–362.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	The three distinct dosing regimens — basic extract, traditional decoction, concentrated ethanol extract — are selected over the secondary bullets on timing, sex, age and genetics.
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; all three sets are populated.
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: “1.5–5.2 g daily”, “6–12 g daily”, “6 mg daily” with matching preparation notes; the “Noguchi’s group” attribution is correctly stripped from action_3_sub.

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	🟢	Matches the three windows the ER states at line 415 — immune markers at 8 weeks, urinary/fatigue at 8–12 weeks, lipids at 12 weeks.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered High (immune modulation) → Medium/Low (urinary symptoms, fatigue) → Low (lipids), matching the ER’s Expected Benefits tiers.
11.3	If less that three distinct time-to-effect aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing.	N/A	The ER supplies three distinct time-to-effect aspects; all three sets are populated.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All nine spans populated; the subs draw on ER lines 415 (“Nothing measurable should be expected before two months”), 175 (objective urinary measures unchanged) and 393 (12-week reassessment point).
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 correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All ten entries are the ER’s H4 benefit headings from lines 159–217, kept in their ER tiers.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans are present and populated (lines 521–532).
12.3	Items are as concise as possible. No explanations, no elaborations, no effect sizes, no qualifiers, no attributions, no citations, no study details, no mechanistic explanations, etc. Just the key fact.	🟢	Each entry is a bare noun phrase; no Magnitude figures (CD3 +3.91%, RR 1.50, IPSS −1.18) and no “⚠️ Conflicted” flags are carried across.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any benefits entry.
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 needed hiding.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All eight entries are the ER’s H4 risk headings from lines 243–287, kept in their ER tiers.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans are present and populated (lines 575–586).
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 entry is a bare noun phrase; the Magnitude data (RR 1.67, post-meal glucose figures) and the case-report provenance are all omitted.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any risks entry; the ER’s inline glosses such as “(allergy-related white blood cells)” are dropped.
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 needed hiding.

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 (lines 445–458).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All twelve ER biomarkers are present in ER order — ALT, AST, GGT, total bilirubin, platelet count, PT/INR, fasting insulin, HbA1c, triglycerides, hs-CRP, lymphocyte subsets, IPSS — with targets and rationales copied 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.	🟢	Line 738 condenses ER line 443: baseline, liver panel and full blood count at 8–12 weeks then every 6 months, metabolic and inflammatory markers at 12 weeks, and immediate testing on symptoms.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	All six entries come from the “Qualitative markers worth tracking alongside the labs” list at ER lines 462–467.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	Six of six ER qualitative markers are present in ER order; only the trailing attribution “which improved in the fatigue and student trials” is trimmed from item 3.

Issues 15/08/2026 10:14

Pass rate 100.00%. No issues found.