Audit: QRS - Japanese Honeysuckle for Health & Longevity

Audit conducted on 15/08/2026 14:29 using AI4L / Opus 5

Iterations

Summary

Items	Count
Total	93
Passed	84
Failed	0
N/A	9
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 values trace to the ER: doses (6-15 g, 125-175 mg, 30 g / 600 mL to 200 mL) to ER Therapeutic Protocol; all seven biomarker targets and the cadence to the ER Monitoring Protocol & Defining Success table and text; gate items to ER Key Interactions & Contraindications.
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.	🟢	“Accelerated viral clearance, conflicted” carries over the ER’s “⚠️ Conflicted” flag on the MIR2911 benefit; time_3_sub keeps “mechanism disputed”.
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”).	🟢	Contraindication qualifiers are preserved intact (“unless certified unsulfured”, “until repletion, unless separated from meals”, “unless weekly monitoring is in place”); nothing is upgraded or downgraded.
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.	🟢	Benefits map to ER Expected Benefits tiers, risks to Potential Risks & Side Effects tiers, gates to Key Interactions & Contraindications; no Benefit-/Risk-Modifying Factor is surfaced as a gate item.
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, author names, years, NCT identifiers or brand names 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.	🟢	Register matches the ER throughout; the At-A-Glance mirrors the plain register of the ER Conclusion (“eaten as food and used as medicine”, “the same plant acids found in coffee”).
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Expert and data-driven (numeric doses, biomarker ranges) while remaining accessible.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Presents facts and thresholds; no imperative or prescriptive framing.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No prescriptive verbs; grep over the rendered body returns no “should”, “must”, “recommend”, “advise”, “ensure” or “consider”.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Content is stated as evidence, not as recommendation.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronoun occurs anywhere in the file.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms retained are load-bearing (named substrate drugs required by 9.5, biomarkers required by 14.2); no unnecessary jargon.
2.8	Information is presented in a concise and very compact manner	🟢	Every cell is a condensed fragment; no section exceeds its budget.
2.9	It DOES NOT address the reader directly	🟢	Confirmed by the same pronoun check as 2.6.
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.	🟢	Framing assumes a proactive reader who will verify species, source unsulfured material and track seven biomarkers.
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.	🟢	Protocol includes a 60-80 minute decoction alternative and a two-hour iron separation, both effortful.
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.	🟢	Content depth (CYP substrate lists, ferritin thresholds, urinary 8-OHdG) is well beyond general-population material.
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.	🟢	Risk weighting foregrounds product-quality issues (sulfur fumigation, species substitution) that matter specifically to a self-sourcing 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.	🟢	The string “anti-aging” does not occur; the header 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.	🟢	Formal terminology in the sheet body (“Non-steroidal anti-inflammatory drugs”, “hypersensitivity”, “non-heme iron”); the plainer At-A-Glance register is mandated by 7.4 and mirrors the ER Conclusion.

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 verified verbatim against [qrs_template]: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”, “Contraindications”, “Key Interactions”, “Marker”/”Target”/”Why”, and every rendered tier label.
3.2	All “<span data-qrs-var=”NAME”>…</span>” from the [qrs_template] are present in the the QRS.	🟢	Diff against [qrs_template] shows all 34 template variables present; marker_#* and qualitative_item# are expanded to the seven marker rows and five qualitative items as the template pattern intends.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Structural diff against the template shows no change outside the variable spans; the website=”evidence_review”, website=”audit” and website=”full_review” spans, CSS and footer 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 is empty, so no empty-state phrasing is required.
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 are verbatim ER bold labels (“Standard decoction dose”, “Standardized extract approach”, “High-dose acute protocol”); marker names are verbatim ER Biomarker column values; gate labels are verbatim ER bullet labels.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	No label is paraphrased or invented where the ER supplies one; the only shortenings are within the trimming latitude of 8.5/9.5.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji characters occur anywhere in the file.
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.	🟢	Three protocol cells, three time cells, three benefit lines, four risk lines, 6+8 gate items, seven marker rows and five qualitative items fit the single-page budget.

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 metadata comment spans lines 2-14, immediately after “<!doctype html>” on line 1 and before the “” comment on line 16.
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 preceding “QRS — Metadata” text 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; no element on the sheet echoes any metadata value.
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 and unquoted except duration: “00:02”, which contains a colon and therefore requires quoting.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: japanese_honeysuckle_2026-0825-1204_Opus_ER.md, matching the audited source ER.
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-1401, in YYYY-MMDD-HHMM form.
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 number with no additional qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9: qrs_filename: japanese_honeysuckle_2026-0825-1204_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: no leading/trailing whitespace and no unnecessary quoting on any key.

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: “Japanese Honeysuckle for Health & Longevity - Quick Reference Sheet”, matching ER canonical_topic with “&” 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: “Japanese Honeysuckle 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 MM/DD/YYYY form of qrs_creation_date 2026-0815-1401.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “Opus 5”, matching qrs_creator_ai_fullname.
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 is byte-identical to the template apart from the two variable spans; no badge, AKA line, version stamp or audit date is present.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Condenses the ER Conclusion: food-and-medicine history, coffee-family chemistry, the lopsided evidence base, and the practical form and tolerability.
7.2	[at_a_glance] is no longer than 60 words	🟢	59 words, verified by word count of the span contents.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause maps to a distinct Conclusion passage: paragraph 1 for the food/medicine and plant-acid framing and the lab-versus-human contrast, paragraph 2 for the verified-unsulfured form, tolerability, digestive upset and iron reduction.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	Plain-language throughout: “plant acids” for chlorogenic acids, “less iron taken up from meals” for reduced non-heme iron absorption; no acronyms.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No study name, year, sample size or p-value appears.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No effect size, relative risk, confidence interval or statistic appears.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	Derived from the “Populations who should avoid Japanese honeysuckle” list of the ER Key Interactions & Contraindications section.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All six ER contraindication bullets are represented, one-to-one and in ER order.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Six discrete <li></li> elements inside the [stop_items] span (lines 540-545).
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.	🟢	Trailing clauses stripped: “— absolute contraindication” from the hypersensitivity item and “where a 10-20% shift in drug level is clinically consequential” from the transplant item; no citations or study details 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).	🟢	Qualifiers preserved: “(prior bronchospasm after sulfited food)”, “ferritin below 30 ng/mL”, “(target INR 2-3)”, “any gestational age”, and every “unless” clause.
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 uses no ranking notation inside parentheses in this section.
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 section is populated, and the ER does identify populations that should avoid the intervention.
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. <!– empty: ER names no population that should avoid the intervention –>	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	🟢	Derived from the bulleted interaction list of the ER Key Interactions & Contraindications section.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All eight ER caution bullets are present in ER order; the ninth ER bullet (“Intravenous herbal preparations of any kind”) is an absolute contraindication and is correctly carried in [stop_items] instead.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Eight discrete <li></li> elements inside the [caution_items] span (lines 553-560).
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.	🟢	Only the ER bold labels are carried; all mechanism, consequence and monitoring text after the colon is stripped, and no em-dash clause remains.
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 preserved: the CYP3A4, CYP2C9 and CYP1A2 substrate lists in full, the NSAID list, the antihypertensive and supplement lists, and both named cooling herbs.
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 uses no ranking notation inside parentheses in this section.
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 section is populated, and the ER does identify interactions that change how the intervention is used.
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. <!– empty: ER names no interaction that changes how the intervention is used –>	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 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 three dose-defining bullets are chosen (standard decoction, standardized extract, high-dose acute) over the non-actionable ones (genetic polymorphisms, sex-based differences, baseline biomarkers).
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 Therapeutic Protocol section supplies more than three distinct actionable aspects.
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section.	🟢	All nine action fields carry ER-derived content; no placeholder or empty-state 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	🟢	Throat and airway symptoms (ER Practical Considerations, “Time to effect”), digestive symptoms (same bullet, eight weeks), and viral clearance (ER Expected Benefits, median 4.0 days).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered by benefit tier: throat/airway and digestive are both Medium 🟩🟩 in the ER and appear first in ER order; viral clearance is Low 🟩 and appears last.
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.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All nine time fields carry ER-derived content; time_1_sub and time_2_sub are near-verbatim from the ER “Time to effect” bullet.
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 row is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All three tier lines derive from the ER Expected Benefits section headings.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four benefit spans are present; benefits_high is hidden because the ER has no High tier.
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 line is a semicolon-joined list of condensed ER benefit headings with no magnitudes, mechanisms or citations.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content survives; “Attributed to MIR2911” and “from Chlorogenic Acids” are dropped from the Low tier.
12.5	If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing.	🟢	The ER Expected Benefits section has Medium, Low and Speculative tiers only; benefits_high is set to style=”display: none” with no empty-state phrasing (line 521).

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All four tier lines derive from the ER Potential Risks & Side Effects section headings.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four risk 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 line is a semicolon-joined list of condensed ER risk headings with no mechanism, frequency or citation detail.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content survives.
13.5	If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing.	N/A	The ER populates all four risk tiers, so no span needs hiding.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Derived from the ER Monitoring Protocol & Defining Success biomarker table.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All seven ER table rows are present with matching targets: hs-CRP, ALT, Ferritin, Eosinophil count, Seated blood pressure, Urinary 8-OHdG, INR.
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.	🟢	Populated from the ER monitoring paragraph: baseline, 8 weeks, then every 6-12 months, with weekly INR or drug level for 4 weeks on warfarin or a narrow-margin medication.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Derived from the qualitative-marker list closing the ER Monitoring Protocol & Defining Success section.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All five ER qualitative bullets are present: throat comfort, digestive symptom burden, upper-respiratory episode frequency, afternoon energy and dizziness, and immediate hypersensitivity signs.

Issues 15/08/2026 14:29

Pass rate 100.00%. No issues found.

Issues 15/08/2026 14:21

1. 10.2 — Protocol cell duplicates dosing frequency: action_3 “Split versus single dosing / Twice daily” restates the “twice daily” already given in action_2’s value, and displaces the ER’s distinct “High-dose acute protocol” bullet (ER 359: 30 g boiled in 600 mL for 80 minutes down to 200 mL, taken as two 100 mL portions).
2. 12.3 — Mechanism carried into Benefits tier: The Low benefits item retains “attributed to MIR2911” and “from chlorogenic acids”, which are mechanistic attributions rather than the key fact, contrary to 12.3’s prohibition on attributions and mechanistic explanations.

Fixes 15/08/2026 14:21

1. 10.2 — Protocol cell duplicates dosing frequency: Replaced the redundant third protocol cell “Split versus single dosing / Twice daily” with the ER’s distinct “High-dose acute protocol” (ER 359): 30 g dried buds daily, boiled in 600 mL down to 200 mL, taken as two 100 mL portions.
2. 12.3 — Mechanism carried into Benefits tier: Stripped the mechanistic attributions from the Low benefits item, changing “Accelerated viral clearance attributed to MIR2911, conflicted … modest blood pressure and vascular effects from chlorogenic acids” to “Accelerated viral clearance, conflicted … modest blood pressure and vascular effects”.

Issues 15/08/2026 14:15

1. 1.3 — Softened discontinuation urgency: [qualitative_item_5] (line 701) states “warrants stopping” where the ER (line 458) states “which warrants immediate discontinuation”, dropping the urgency qualifier “immediate”.

Fixes 15/08/2026 14:15

1. 1.3 — Restored discontinuation urgency: [qualitative_item_5] changed from “warrants stopping” to “warrants immediate discontinuation”, matching the ER’s wording at line 458.

Issues 15/08/2026 14:06

1. 4.5 — Content exceeds one A4 page: Estimated rendered height is roughly 1.75 A4 pages; the longest fields are monitoring_cadence (line 680, 43 words), marker_6_target (line 659) and marker_7_target (line 670), the 100+ character subs action_1_sub (line 450), action_3_sub (line 472) and time_2_sub (line 500), and several three-line gate items in stop_items/caution_items (lines 540–561).

Fixes 15/08/2026 14:06

1. 4.5 — Protocol and time-to-effect subs condensed: Trimmed action_1_sub, action_3_sub, time_2_sub and time_3_sub from full ER sentences to short phrases (e.g. “Simmered in water; the Chinese Pharmacopoeia range and the basis for most clinical use of the single herb” → “Simmered in water; the Chinese Pharmacopoeia range”).
2. 4.5 — Benefits and risks tiers shortened: Condensed benefits_speculative, risks_low and risks_speculative to shorter equivalents (e.g. “cumulative effects of long-term daily high-dose use” → “long-term high-dose use”), saving two rendered lines.
3. 4.5 — Gate items tightened: Shortened three stop_items and two caution_items while preserving every parenthetical qualifier and drug example (e.g. “Warfarin with a target international normalized ratio of 2–3, unless weekly monitoring is in place” → “Warfarin (target INR 2–3), unless weekly monitoring is in place”).
4. 4.5 — Monitoring table and cadence compacted: Shortened marker_6_target, marker_6_why, marker_7_target, and cut monitoring_cadence from 43 words to 31 while keeping the baseline, 8-week, 6–12-month and weekly-INR elements.
5. 4.5 — Qualitative items reduced to one line each: Condensed qualitative_item_1, _3, _4 and _5 (e.g. “Energy through the afternoon, and any new dizziness or lightheadedness that would suggest an additive blood-pressure effect” → “Afternoon energy, and any new dizziness suggesting an additive blood-pressure effect”).