Audit: QRS - Coriolus versicolor to Treat Cancer

Audit conducted on 21/09/2026 02:35 using AI4L / Opus 5

Iterations

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. 🟢 All protocol values, gate items, tiered benefits/risks, biomarker rows and cadence trace to ER Therapeutic Protocol, Key Interactions & Contraindications, Expected Benefits, Potential Risks & Side Effects, Practical Considerations, Discontinuation & Cycling and Monitoring Protocol & Defining Success.
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 “No established numeric target — the result is positive or negative” is carried as “No established numeric target; positive or negative” (marker_9_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”). 🟢 ER “Absolute contraindication” for immunosuppressants is placed in the Contraindications gate, not downgraded to Key Interactions; “Pregnancy and lactation” remains an avoid item.
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. 🟢 PD-L1 appears as an ER-listed avoid population in the gate and as an ER-listed Low risk (“Absent Benefit in PD-L1-Positive Tumours”) in Risks; no Benefit- or Risk-Modifying Factor is promoted to 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. 🟢 The QRS carries no PMIDs, author names, NCT identifiers or brand names.
1.6 The QRS does not introduce new attributions. 🟢 No attributions of any kind in the QRS body.

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, declarative, evidence-first register matching the ER; British spellings (“tumour”, “mould”, “fibre”) carried through.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Doses, ranges and biomarker targets are given without hedging or exhortation.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Regimens are described as what trials used (“used in Western trials”, “highest dose tolerated”), not prescribed.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No imperative instruction to the reader; gate entries are labelled facts with the ER’s own “Monitor” / “Caution” markers.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Cadence line states the schedule used, without recommending language.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns anywhere in the document.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical terms retained are unavoidable drug/biomarker names; “stomach or bowel cancer surgery” is used in the lede rather than “gastric or colorectal”.
2.8 Information is presented in a concise and very compact manner 🟢 Every gate, benefit and risk entry is a sentence fragment; magnitudes, citations and rationale are stripped.
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. 🟢 Matches the ER’s stated framing “for a risk-aware adult already receiving or recently finished with conventional cancer treatment”.
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. 🟢 Multi-year 3 g/day divided dosing and a nine-marker monitoring panel are presented without softening the burden.
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. 🟢 Assumes access to oncology bloodwork, PD-L1 pathology status and three-times-daily dosing.
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. 🟢 Lede names the retail-versus-trial-material gap, and the PD-L1 gate marks the subgroup for whom the benefit is absent.
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 term “anti-aging” does not appear.
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. 🟢 Route is given as “Orally”, “Divided oral doses”, “divided oral doses”; no “pills”, “taken by mouth” or similar.

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 headings, gate titles, tier labels and the Marker/Target/Why column headers are byte-identical to the template.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 page_title, header_topic, header_subline_date, header_subline_model, at_a_glance, action_1–3 (label/value/sub), time_1–3 (label/value/sub), benefits_, stop_items, caution_items, risks_, marker_1–9 (name/target/why), monitoring_cadence, qualitative_item_1–6 all present.
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 unchanged from 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 source ER section drawn on by the QRS is empty.
4.2 Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label. 🟢 Protocol labels (“Standard Japanese extract regimen”, “Standard Chinese extract regimen”, “Whole-mushroom regimen used in Western trials”) and the nine interaction labels reproduce the ER bold labels.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Time-to-effect labels are drawn from the ER’s own wording in Practical Considerations (“immune markers”, “Symptom and quality-of-life changes”, “Survival differences”); biomarker names match the ER 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 characters present; the ER’s 🟩/🟥/🟨/⚠️/⭕️ markers were stripped.
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 rather than extended: magnitudes, confidence intervals, citations, mechanism and context/notes columns are all dropped; no second page or overflow block was added.

5. Metadata

# Description Result Comments
5.1 The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content. 🟢 Lines 2–14, immediately after <!doctype html> on line 1.
5.2 Inside that HTML comment the YAML block is delimited by a line “—” opening and a line “—” closing. Text before the opening “—” is permitted but is not parsed as YAML. 🟢 Opening --- on line 3, closing --- on line 13.
5.3 The metadata is not visible in any rendered view of the QRS and is not surfaced by any other element on the sheet. 🟢 Enclosed in an HTML comment; no metadata value is repeated in the 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:03" is quoted, and it contains a colon requiring it.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 Line 4: er_filename: coriolus_versicolor_cancer_2026-0921-0111_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 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) 🟢 Line 6: qrs_creation_date: 2026-0921-0214.
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢 Line 7: qrs_creator_ai_nickname: Opus.
5.9 The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) 🟢 “Opus” — single word, no version.
5.10 The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” 🟢 Line 8: qrs_creator_ai_fullname: Opus 5.
5.11 The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier (e.g., Opus 4.6, Sonnet 3.2, Grok 4.5, Gemini 3.1, ChatGPT 5.4) 🟢 “Opus 5” — nickname plus version, no qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 Line 9 matches the file’s own name 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. 🟢 All nine values are clean; git_user and git_issue are unquoted scalars.

6. Page Title & Header

# Description Result Comments
6.1 [page_title] is set to the [canonical_topic] of the ER frontmatter followed by “ - Quick Reference Sheet” (e.g., “Intervention - Quick Reference Sheet”). The [canonical_topic] is HTML-entity-encoded as needed (e.g., &amp; for &) 🟢 Line 22: “Coriolus versicolor to Treat Cancer - Quick Reference Sheet”; no entity encoding required.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 Line 417: “Coriolus versicolor to Treat Cancer”, matching ER frontmatter canonical_topic.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 Line 421: “09/21/2026” from qrs_creation_date: 2026-0921-0214.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Line 425: “Opus 5”.
6.5 No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. 🟢 Header holds only the title and the template’s standard subline; the ER’s “Also known as” list was 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 🟢 Compresses the Conclusion’s four load-bearing points: licensed extracts in long clinical use, the survival gain after gastrointestinal surgery, minor harms, and the retail-material gap.
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. 🟢 Each sentence maps to a distinct Conclusion clause (“two licensed extracts have been given alongside cancer surgery and chemotherapy in Japan and China for decades”; “a small but consistent survival gain when the Japanese extract is added to chemotherapy after stomach or bowel cancer surgery”; “Harms are minor”; “the products on Western shelves are a different material from what was studied”).
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms; “wood-decay mushroom”, “stomach or bowel cancer surgery” and “Western retail products” are lay terms.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial names, years or sample sizes.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 “a small survival gain” carries no numeric estimate; no hazard or risk ratios.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All seven entries come from that section’s “Populations who should avoid Coriolus versicolor” list plus its “Absolute contraindication” bullet.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All six ER avoid-populations are present, plus the immunosuppressant bullet the ER marks “Absolute contraindication”.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Lines 569–581: seven discrete <li> elements inside the 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. 🟢 The ER’s rationale clauses (“on absence of any safety data”, “since that subgroup showed none”, “A receptor activator that switches on killer cells directly opposes the treatment goal”) are stripped; no dash-trailing clauses remain.
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). 🟢 “Child-Pugh Class C” preserved; “prednisone ≥20 mg daily” threshold preserved; autoimmune and immunosuppressant example lists shortened but retained.
8.6 When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol. 🟢 The ER uses no ranking notation here; the one comparison symbol carried over (“≥20 mg daily”) is a self-explanatory dose threshold, and all example lists are plain comma-separated.
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 does identify such populations, and the section is correspondingly populated.
8.8 If the section is left empty, an HTML comment inside the [stop_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. N/A The section is not empty.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All nine entries map one-to-one onto the ER’s interaction bullets.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 The ER’s ten interaction bullets minus the immunosuppressant bullet (moved to Contraindications) = the nine items shown.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Lines 589–618: nine discrete <li> elements inside the 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. 🟢 Each item is reduced to the ER bold label plus the ER’s own one-word action (“Monitor” / “Caution”); the Lam et al. citation and all mechanistic sentences 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 interaction retains a named example-drug parenthetical; longer ER lists are trimmed to two representatives rather than dropped.
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. 🟢 No ranking notation in the ER bullets; all parentheticals are plain comma-separated drug lists.
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 all nine appear.
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 first three bullets of the ER Therapeutic Protocol section.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 The two licensed-extract regimens carrying the survival evidence plus the whole-mushroom regimen relevant to Western availability; the remaining ER bullets are single-trial or non-actionable commentary.
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 used.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 Labels, doses (“3 g polysaccharide-K daily”, “~3 g polysaccharopeptide daily”, “3–9 g daily”) and sub-lines all trace to the ER bullets verbatim in substance.

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 🟢 All three horizons named in the ER’s Practical Considerations “Time to effect” bullet are carried: immune markers, symptom/quality-of-life, survival.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Survival differences (ER High-tier benefit) first; the two Low-tier-linked horizons follow.
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 used.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 Values “3–5 years”, “Within 6 weeks”, “1–2 months” match the ER; sub-lines draw on Practical Considerations, Expected Benefits and the Discontinuation & Cycling washout finding.
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; the section is correctly retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Each tier’s content maps to the ER headings under the same tier; the ER’s ⭕️-flagged cervical-lesion item is correctly excluded as not central to the topic.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present and populated, lines 539–559.
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. 🟢 Hazard ratios, confidence intervals, number-needed-to-treat and all Magnitude/caveat prose are stripped; each tier is a semicolon-joined fragment list.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses remain 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 tiers have ER content; no sub-section is empty.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All nine ER risk headings across the four tiers are represented.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present and populated, lines 630–646.
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. 🟢 The ⚠️ Conflicted markers, Magnitude lines and “Not quantified in available studies” prose are stripped.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses remain in any risks entry.
13.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. N/A All four tiers have ER content; no sub-section is empty.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Rows reproduce the ER Monitoring Protocol & Defining Success biomarker table.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All nine ER table rows are present in ER order, with the Optimal Functional Range values carried verbatim (“1.8–3.0 × 10⁹/L”, “2.0–5.0 × 10⁹/L”, “Below 2.0”, “10–26 U/L”, “4.2–5.0 g/dL”, “Below 1.0 mg/L”, “Below 3.0 ng/mL in non-smokers”, “Above 90 mL/min/1.73 m²”, PD-L1 status).
14.3 [monitoring_cadence] is populated with the monitoring cadence/frequency derived from the ER Monitoring section. It is not left with placeholder text or empty. 🟢 Lines 786–789 reproduce the ER’s baseline-off-treatment, four-week, twelve-week and three-to-six-month schedule aligned to scheduled oncology bloodwork.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Items reproduce the ER’s “Qualitative markers worth tracking alongside the laboratory values” bullet list.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All six ER bullets present: fatigue severity, appetite/weight, gastrointestinal tolerance, performance status, fingernail appearance, infection and treatment-delay frequency.

Issues 21/09/2026 02:35

Pass rate 100.00%. No issues found.

Issues 21/09/2026 02:29

  1. 1.3 — Non-central benefit stated unqualified: benefits_low (line 551) lists “papillomavirus clearance and cervical lesion repair” without the ER’s scope limit; ER lines 188–192 flag that finding “⭕️ Not Central to Treat Cancer”, note it “bears on prevention, not on treating established cancer”, and attribute it to a multi-ingredient vaginal gel rather than the oral regimens the sheet presents.

Fixes 21/09/2026 02:29

  1. 1.3 — Non-central benefit removed: Dropped “papillomavirus clearance and cervical lesion repair” from benefits_low, since the ER flags that finding as not central to treating cancer and attributes it to a multi-ingredient vaginal gel rather than the oral regimens the sheet presents.

Issues 21/09/2026 02:21

  1. 4.5 — Sheet overflows one A4 page: At the template’s print geometry the populated sheet carries ~5,900 characters of visible text and an estimated ~1.8–2.0 A4 pages of rendered height, driven mainly by the nine-item Key Interactions gate (lines 593–637), the nine-row Monitoring table with multi-line “why” and “target” cells (lines 681–808), the six qualitative items (lines 824–859) and the long protocol sub-lines.
  2. 2.8 — Redundant and padded field text: [time_2_sub] (line 518) and [time_3_sub] (lines 529–531) merely restate their own label and value, [time_1_sub] repeats “three to five years” already shown in [time_1_value], and the Monitoring “why” cells and qualitative items carry full ER sentences rather than compacted phrases.

Fixes 21/09/2026 02:21

  1. 2.8 — Redundant time-to-effect sub-lines: [time_1_sub], [time_2_sub] and [time_3_sub] no longer restate their own label and value; they now carry distinct ER facts (“Visible only in trial follow-up, not to an individual”, the three-week washout reversal, and the concurrent-treatment restriction).
  2. 4.5 / 2.8 — Protocol sub-lines condensed: The three [action_#_sub] cells were tightened (e.g. action_3 from “9 g daily was the highest dose tolerated over six weeks, and 3 g daily produced no immune change” to “9 g was the highest dose tolerated, 3 g produced no immune change”), cutting roughly one wrapped line per cell.
  3. 4.5 — Contraindications tightened: Item 1 shortened to “Transplant recipients on maintenance immunosuppression; active graft-versus-host disease”, the autoimmune exemplar list trimmed to two, and the immunosuppressant list reduced to three named agents while keeping the ≥20 mg prednisone threshold.
  4. 4.5 / 9.5 — Interaction example lists trimmed: All nine Key Interactions retained, with each parenthetical drug list cut to two representative agents (e.g. acid suppressants to “omeprazole, famotidine”, beta-glucan supplements to “Ganoderma lucidum, Grifola frondosa”), as 9.5 permits for the one-page budget.
  5. 4.5 — Benefit and risk items compacted: Low-tier benefit shortened to “papillomavirus clearance and cervical lesion repair” and the speculative risk to “fungal-protein hypersensitivity”.
  6. 4.5 / 2.8 — Monitoring rationales reduced to single-line phrases: All nine [marker_#_why] cells were rewritten as compact phrases (e.g. “Reflects nutritional reserve and the inflammatory state that predicts treatment tolerance” to “Reflects nutritional reserve and treatment tolerance”), and [marker_9_target] shortened to “No established numeric target; positive or negative”.
  7. 4.5 — Cadence and qualitative items compacted: [monitoring_cadence] reduced to “Baseline off the mushroom, then four weeks, twelve weeks, and every three to six months thereafter, aligned to scheduled oncology bloodwork”, and all six qualitative items shortened while keeping every marker listed.

Note: visible sheet text fell from ~5,930 to ~5,130 characters. The remaining length is structural — the ER supplies nine biomarkers, nine non-contraindicated interactions and six qualitative markers, and checklist items 14.2, 9.2 and 15.2 require all of them to be listed, so no further reduction was possible without dropping mandated items.