Audit: QRS - Chaga for Health & Longevity

Audit conducted on 04/09/2026 16:28 using AI4L / Opus 5

Iterations

Summary

Items	Count
Total	93
Passed	86
Failed	0
N/A	7
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 variable content traced to the ER: protocol cells to Therapeutic Protocol, gates to Key Interactions & Contraindications, benefit/risk items to the ER H4 headings, all 10 markers and their targets/why-text to the ER biomarker table, cadence to 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.	🟢	time_1_value carries the ER’s literal “Unknown”; at_a_glance keeps “no controlled human trial of chaga alone has reported a health outcome”.
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 and breastfeeding” remains under Contraindications, not Key Interactions; the “conflicted” marker is retained on both conflicted benefits.
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.	🟢	Every gate item originates in the ER’s Key Interactions & Contraindications section; no Benefit- or Risk-Modifying Factor was promoted into a gate, and no modifying factor appears among the risk tiers.
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 identifiers, author names, or brand names (Nammex, Real Mushrooms, Befungin) appear anywhere in the QRS.
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.	🟢	Matches the ER’s sober “mechanism without measurement, set against a documented kidney signal” framing.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Numeric targets, cadence, and a concrete protocol give the reader actionable footing while remaining neutral about efficacy.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Content is stated as findings and ranges, never as instructions to the reader.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperatives; gates list populations and agents rather than directives.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No occurrence of “recommend”, “advise”, “should”, or “must” in any populated variable.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere in the document body.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Retained terms (“enteric hyperoxaluria”, “oxalate nephropathy”) are ER-verbatim item names carrying their own parenthetical or contextual gloss; no jargon is added beyond the ER.
2.8	Information is presented in a concise and very compact manner	🟢	Fifteen speculative benefits and six speculative risks are compressed into single semicolon-separated runs with no elaboration.
2.9	It DOES NOT address the reader directly	🟢	Confirmed by full-text scan for “you”/”your”; none present.
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.	🟢	Optimal-range biomarker targets and a 10-marker monitoring panel address exactly this audience.
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.	🟢	24-hour urine oxalate collection, urine microscopy, and a multi-point retest cadence presume that willingness.
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 ranges are stated instead of conventional lab cut-offs, which is not general-population framing.
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 foregrounds the absent human efficacy evidence against the documented renal harm, the weighting the ER reaches for this audience.
2.14	The document’s own voice frames usage in longevity terms, not “anti-aging” (e.g., “anti-aging clinics”, “anti-aging community”, “anti-aging medicine”). Proper names that contain “anti-aging” (e.g., “American Academy of Anti-Aging Medicine”) are quoted verbatim.	🟢	“Anti-aging” does not appear; the title and header use “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.	🟢	“capsule”, “extract”, “decoction”, “hypersensitivity” used throughout; no colloquial substitutes found.

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”	🟢	Diff against [qrs_template] shows every fixed heading, gate heading, tier label, and table header byte-identical to the template.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	Programmatic set comparison: all 34 template variable names present; the only additional names are the expansions of the template’s repeatable marker_#_* and qualitative_item_# patterns.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Structural diff shows no edits outside the addressed variables; the template’s own BENEFTIS comment typo and the website="..." spans are carried through unchanged.

4. Formatting

#	Description	Result	Comments
4.1	When the source ER section is empty, the QRS uses the ER’s own empty-state phrasing verbatim. Typical phrasings are “None documented in human trials to date” and “Not formally studied”	N/A	No ER section mapped into the QRS is empty; the unpopulated benefit/risk tiers are governed by items 12.5 and 13.5, not by empty-state phrasing.
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.	🟢	“Modern dual extraction”, “Traditional Slavic decoction”, “Time of day” are the ER’s bold protocol labels verbatim; gate labels likewise.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	No invented label found; all three action_#_label values and all marker names match the ER exactly.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	Unicode scan returns no emoji; the ER’s “⚠️ Conflicted” markers were converted to the plain word “conflicted”.
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.	🟢	Each section is at its minimum viable form: at_a_glance at 59 words, tiered items reduced to bare names, gate items stripped of all post-dash clauses, and marker “why” text held to a single short clause.

---

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; the comment opens 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, preceded only by the descriptive comment title on line 2.
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; none of its values are echoed into the header or footer.
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, 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: chaga_2026-0904-1322_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.7.02, matching the version badge in 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-0904-1558, 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” = nickname + version, no qualifier appended.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 states chaga_2026-0904-1322_Opus_QRS.html, which is the file’s actual 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.	🟢	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: “Chaga for Health & Longevity - Quick Reference Sheet”; the ampersand is correctly entity-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: “Chaga for Health & Longevity”, matching the ER’s canonical_topic.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “09/04/2026”, the correct reformatting of 2026-0904-1558.
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 structurally identical to the template; the ER’s seven alternate names were correctly 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 ER conclusion’s three moves — what chaga is, the absent human evidence, and the documented renal harm — into the decision-relevant bottom line.
7.2	[at_a_glance] is no longer than 60 words	🟢	Programmatic count: 59 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Birch/tea/capsule, the lab-and-rodent activity list, “no controlled trial of chaga alone reporting a health outcome”, the heavy oxalate load, and the dialysis-grade kidney damage each map to a distinct sentence of the ER Conclusion.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “oxalate” is immediately glossed as “a crystal-forming compound”, and “dialysis” is in general usage.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial name, year, sample size, or p-value appears.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numeric result of any kind; the oxalate content and intake figures from the ER were correctly left out.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All seven items map one-to-one onto the ER’s “Populations who should avoid Chaga” list within that section.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All seven ER avoid-list bullets are present, and the ER’s absolute contraindication for solid-organ transplant recipients is captured by item 3.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Lines 566–572: seven discrete <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.	🟢	The ER’s trailing clause “— no human safety data at any dose” was stripped from the pregnancy item, and “Anyone on warfarin” was reduced to “Warfarin”; 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).	🟢	“stage 3 or worse (eGFR below 60 mL/min/1.73 m²)” is preserved intact, as is the enteric-hyperoxaluria cause list, restated compactly as a parenthetical.
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 avoid-list uses 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 seven 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 left empty.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All nine items map onto the ER’s interaction bullets in that section.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Nine of the ER’s ten interaction bullets are carried; the omitted one — Immunosuppressants after solid-organ transplant — is the absolute contraindication already listed in stop_items, exactly as this item requires.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Lines 580–593: nine discrete <li> elements inside the caution_items span.
9.4	Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact.	🟢	Every ER bullet’s post-em-dash rationale (INR checks, the two-week surgical hold, the 100 mg oxalate ceiling, the calcium binding mechanism) is stripped; no dash-trailing content survives.
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 are retained; the nephrotoxic-drug names were lifted from the ER body into the parenthetical, and only redundant suffixes were trimmed (“chromium picolinate” → “chromium”, “turmeric extract” → “turmeric”).
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 names ten such interactions, and the section is correctly populated rather than left empty.
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 left empty.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER Protocol section	🟢	All three cells derive from the ER’s Therapeutic Protocol bullets.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	The two live dosing routes (modern dual extract, traditional decoction) plus timing are the ER’s only currently actionable regimens; the Befungin bullet is historical and the remaining bullets are modifiers rather than implementation aspects.
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 mentions three or more actionable implementation aspects, and 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 spans carry ER-derived content: the “1–2 g extract daily” and “1–2 g per cup, two to three times daily” amounts and the “before or with meals” timing are stated verbatim in the ER.

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	🟢	The ER offers exactly one time-to-effect statement (Practical Considerations → “Time to effect: Unknown”), and it is the one carried.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Only one set is populated, so ordering is trivially satisfied.
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.	🟢	Lines 509 and 520: the two unused pcell blocks carry style="display: none" and their six spans are empty, with no placeholder text.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	Label “Time to effect” is the ER’s bold bullet label, value “Unknown” is the ER’s literal answer, and the sub reproduces the ER’s no-endpoint-measured and weeks-to-months traditional expectation.
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 — an explicit “Unknown” plus the traditional weeks-to-months expectation — so removal does not apply.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	Both populated tiers correspond to the ER’s Expected Benefits H4 headings.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present at lines 538–546, in template order.
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.	🟢	The 20-man crossover trial, the 250–500 mg/kg mouse dose, the 48–72 h cytotoxicity window and every other study detail are dropped; only the ER’s benefit names remain.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in either populated tier.
12.5	If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing.	🟢	The ER states no benefit reaches High or Medium; lines 538–539 set both spans to style="display: none" with empty content and no empty-state text.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	Both populated tiers correspond to the ER’s Potential Risks & Side Effects H4 headings.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present at lines 605–610, in template order.
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 14.2 g/100 g oxalate figure, the 10–15 g daily intakes, and the rat dose thresholds are all omitted; only the risk names remain.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	The ER’s glosses “(oxalate nephropathy — crystal-driven damage to the filtering units)” and “(low blood sugar)” are stripped; no parentheses remain.
13.5	If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing.	🟢	The ER states no risk reaches High or Medium; lines 605–606 set both spans to style="display: none" with empty content and no empty-state text.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Every row derives from the ER’s Monitoring Protocol & Defining Success biomarker table.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All ten ER biomarkers are present in order — serum creatinine, eGFR, cystatin C, 24-hour urine oxalate, urine microscopy, fasting glucose, HbA1c, hs-CRP, ALT, urine specific gravity — with targets and “why” text matching the ER.
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 764–767 reproduce the ER’s full schedule: baseline, kidney markers at 4 weeks / 3 months / every 6 months, urine oxalate annually, metabolic markers at 3 months.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	All six items derive from the ER’s “Qualitative markers worth tracking alongside the laboratory panel” list.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All six ER qualitative markers are present, with the ER’s trailing explanatory clauses correctly trimmed.

Issues 04/09/2026 16:28

Pass rate 100.00%. No issues found.

Issues 04/09/2026 16:21

1. 9.5 — Nephrotoxic drug examples dropped: The “Nephrotoxic drugs” interaction at QRS line 583 carries no example agents, although the ER bullet (ER line 304) names ibuprofen, naproxen, and furosemide in parentheses.
2. 1.2 — Evening-dosing hedge narrowed: action_3_sub at QRS line 484-486 states “No advantage reported for evening dosing”, dropping the ER’s symmetric “No advantage or drawback has been reported for evening dosing” (ER line 354).

Fixes 04/09/2026 16:21

1. 9.5 — Nephrotoxic drug examples restored: Changed the interaction item from “Nephrotoxic drugs” to “Nephrotoxic drugs (ibuprofen, naproxen, furosemide)”, reinstating the ER bullet’s example agents.
2. 1.2 — Evening-dosing hedge restored: Changed action_3_sub from “No advantage reported for evening dosing” to “No advantage or drawback reported for evening dosing”, matching the ER’s symmetric phrasing.

Issues 04/09/2026 16:13

1. 4.2 / 4.3 / 11.4 — Invented time-to-effect label: [time_1_label] at line 497 is “Onset”, a label that appears nowhere in the ER; the source bullet in ER Practical Considerations (line 401) is labelled “Time to effect:”, which is the label the QRS is required to carry verbatim.

Fixes 04/09/2026 16:13

1. 4.2 / 4.3 / 11.4 — Invented time-to-effect label: Replaced [time_1_label] at line 497 with the ER’s own bold label, changing “Onset” to “Time to effect” to match the source bullet in ER Practical Considerations.

Issues 04/09/2026 16:07

1. 4.5 — Sheet overruns the one A4 page budget: Several cells still carry uncondensed ER prose — time_1sub (QRS lines 503-507), marker_5_target (688-691), monitoring_cadence (767-770), qualitative_item_1 / _5 / _6 (780-807, each keeping a trailing explanatory clause), the three action#_sub cells (456-486), and the long parenthetical lists in caution_items (588-594) — pushing the sheet well past one page.

Fixes 04/09/2026 16:07

1. 4.5 — Protocol cell subtexts condensed: Trimmed action_1_sub (“captures both the fibers and the fat-soluble triterpenoids” → “captures fibers and fat-soluble triterpenoids”), action_2_sub (“later carried into Soviet pharmacopoeia” → “later in Soviet pharmacopoeia”) and action_3_sub (“No advantage or drawback has been reported for evening dosing” → “No advantage reported for evening dosing”).
2. 4.5 — Time-to-effect subtext shortened: time_1_sub reduced from 185 to 125 characters by dropping the redundant “so no onset interval can be stated” and “rather than anything acute” clauses.
3. 4.5 — Monitoring cells condensed: marker_5_target shortened to “No numeric target — presence versus absence of calcium-oxalate crystals against own baseline”, and monitoring_cadence tightened from 219 to 174 characters while keeping every ER interval.
4. 4.5 — Qualitative items stripped of trailing explanations: qualitative_item_1 dropped “— the symptoms that preceded diagnosis in the published kidney cases”, item 5 dropped “after servings”, and item 6 was tightened to “suggesting hypersensitivity to a fungal product”.
5. 4.5 — Interaction parentheticals trimmed: Shortened the example lists to “(berberine, chromium, bitter melon, cinnamon)” and “(spinach, rhubarb, beet greens, almonds, black tea, turmeric)”; both lists are kept, not dropped.
6. 4.5 — Speculative benefits line tightened: Condensed three of the fifteen entries (“protection of cells from oxidative DNA damage” → “protection from oxidative DNA damage”, “direct inhibition of cancer cell growth” → “inhibition of cancer cell growth”, “reduction of fat build-up in the liver” → “reduction of liver fat build-up”) without dropping any entry.