Audit: QRS - Psilocybin for Health & Longevity

Audit conducted on 21/08/2026 17:28 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 item traced to the ER: gates to Key Interactions & Contraindications, benefit/risk tiers to the ER headings, markers/targets to the ER monitoring table, protocol cells to Therapeutic Protocol.
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. 🟢 Cautious phrasing carried over, e.g. marker_3_why “proposed but not shown to lower” (ER line 418) and marker_8/9 targets “No established target” (ER lines 423-424).
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”). 🟢 Thresholds and absolutes preserved unchanged: “at or above 140/90 mmHg despite treatment”, “Corrected QT above 450 ms (men) or 470 ms (women)”, “Pregnancy and breastfeeding”.
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. 🟢 Nothing from Benefit-Modifying Factors or Risk-Modifying Factors is surfaced in the gates; all gate items come from the ER interactions/contraindications section.
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 appear anywhere in the QRS.
1.6 The QRS does not introduce new attributions. 🟢 Griffiths/Johnson, Bogenschutz/Ross, Schindler, COMPASS and PEX010 attributions in the ER are all omitted; none added.

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 sceptical-but-fair register, including the blinding and funding caveats 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 🟢 Expert and objective, with concrete numbers in the protocol, gates, and monitoring table.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Descriptive throughout; describes what trials and protocols do rather than instructing.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No prescriptive or advisory constructions; the footer disclaimer is unchanged template text.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No “recommended”, “advised”, or “should” constructions in the QRS’s own voice.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns anywhere in the file (verified by search).
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain wording used where possible; the remaining technical terms (Child-Pugh, NYHA, QTc, hs-CRP, eGFR) are necessary identifiers taken verbatim from the ER.
2.8 Information is presented in a concise and very compact manner 🟢 Every cell is a condensed phrase; gate and tier items are bare facts with no rationale.
2.9 It DOES NOT address the reader directly 🟢 Confirmed: no direct address to the reader.
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. 🟢 Framed for a proactive, risk-aware reader: decision gates, monitoring targets, and protocol parameters are foregrounded.
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. 🟢 Presents an effortful protocol (supervised six-to-eight-hour sessions, antidepressant taper, two-to-four-week baseline work) without softening.
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 willingness to undertake screening, monitoring, and supervised sessions; not written for a general audience.
2.13 Framing, takeaways, and risk/benefit weighting throughout the document reflect this audience, including where an intervention’s signal for the average person differs from its signal for this audience. 🟢 The healthy-user signal is handled explicitly — [at_a_glance] states the slowed-aging claim rests on cells and mice, and geroprotection sits in the Speculative benefit tier.
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 sheet uses “aging brain” and “slowed-aging”.
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 throughout (e.g. “Monoamine oxidase inhibitors”, “valve regurgitation”, “epigenetic age”).

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 present and unmodified: “Protocol” (line 444), “Time to effect” (482), “Benefits” (525), “Risk & Side Effects” (590), “Monitoring” (614), “Qualitative Assessment” (733), “Contraindications” (549), “Key Interactions” (567), High/Medium/Low/Speculative in both tiered cards, and Marker/Target/Why (618-620).
3.2 All “<span data-qrs-var=”NAME”>…</span>” from the [qrs_template] are present in the the QRS. 🟢 68 data-qrs-var spans present and complete: header (4), at_a_glance, action_1-3 x3, time_1-3 x3, benefits x4, stop/caution, risks x4, marker_1-9 x3, monitoring_cadence, qualitative_item_1-7.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Untouched template spans remain as shipped, including , and (lines 423, 426, 438).

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; every QRS section had ER content to draw on.
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. 🟢 ER bold labels reused verbatim: “Standard supported-session model”, “Two-dose model”, “Time of day” (ER lines 358, 359, 363), and the interaction/contraindication labels in both gates.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 No label is invented where the ER supplies one; biomarker row labels match the ER table names exactly.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji anywhere in the file; the ER’s 🟩/🟥/🟨 tier markers and ⚠️ Conflicted flags are 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. 🟢 Each section is condensed to bare facts — tier lines carry ER headings only, gate items carry no rationale, and Why cells are single clauses — rather than extended with ER elaboration.

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 opens at line 2, immediately after <!doctype html> and before any other comment or markup.
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. 🟢 YAML delimited by — at lines 3 and 13; the leading “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. 🟢 Wholly inside an HTML comment; no element on the sheet repeats any of the values.
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:03”, which contains a colon and therefore requires quoting.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: psilocybin_2026-0821-1449_Opus_ER.md (line 4).
5.6 Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” 🟢 qrs_prompt_version: 26.7.02 (line 5), 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) 🟢 qrs_creation_date: 2026-0821-1711 (line 6), correct YYYY-MMDD-HHMM format.
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢 qrs_creator_ai_nickname: Opus (line 7).
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]” 🟢 qrs_creator_ai_fullname: Opus 5 (line 8).
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, no additional qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename: psilocybin_2026-0821-1449_Opus_QRS.html (line 9), 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. 🟢 Confirmed again across all nine keys; only duration carries quotes, as required by its colon.

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 reads “Psilocybin for Health & Longevity - Quick Reference Sheet”, matching canonical_topic plus the fixed suffix, with the ampersand entity-encoded.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 [header_topic] is “Psilocybin for Health & Longevity” (line 417), matching canonical_topic.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 08/21/2026 (line 421) is qrs_creation_date 2026-0821 in MM/DD/YYYY.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 “Opus 5” (line 425) matches 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. 🟢 Header carries only the title and the template subline; no badge, alternate-names line, version stamp, or audit date.

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 (lines 452-456): strongest signal, thinner signals, harms, the two structural weaknesses, and the aging caveat.
7.2 [at_a_glance] is no longer than 60 words 🟢 58 words, within the 60-word cap.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each clause maps to a distinct ER passage — ER line 452 (mood shift, strongest/thinner evidence, harms), line 454 (blinding, funding), line 456 (cells and mice).
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms or technical classifications; uses “this mushroom compound”, “serious-illness distress”, “funders often have a stake”.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial names, years, sample sizes, or p-values.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No effect sizes, relative risks, or statistical results.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All nine items trace to the ER Key Interactions & Contraindications section (ER lines 319-339).
8.2 [stop_items] represent the Contraindications from the ER 🟢 Covers the two ER absolute contraindications (MAOIs, lithium) plus all eight entries of “Populations who should avoid Psilocybin”; lithium is folded into the ER’s own “Seizure disorder, or current lithium therapy” bullet.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Nine discrete <li> elements inside the [stop_items] span (lines 552-562).
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. 🟢 No trailing rationale — the ER’s “given hepatic clearance of psilocin” and the Child-Pugh gloss are stripped; no dash 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). 🟢 Thresholds and staging preserved: 140/90 mmHg, infarction within 6 months, NYHA III–IV, moderate-or-greater valve regurgitation, QT 450/470 ms, Child-Pugh Class B or C, MAOI drug examples.
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 its contraindication bullets.
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 must 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 empty, so no absence comment is required.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All eight items trace to the ER’s caution bullets (ER lines 321-328).
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Carries the eight caution-level ER bullets and correctly excludes the MAOI and lithium bullets already placed in Contraindications.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Eight discrete <li> elements inside the [caution_items] span (lines 570-580).
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. 🟢 Mechanistic rationale and mitigation clauses from the ER bullets are all stripped; no dash clauses remain.
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). 🟢 Named example drugs preserved for every item — escitalopram/sertraline/venlafaxine, amitriptyline/imipramine, risperidone/olanzapine/quetiapine, dextromethorphan/diphenhydramine, the four serotonergic supplements, Syrian rue/harmala alkaloids, amphetamine/methylphenidate/caffeine, cannabis/alcohol/other psychedelics.
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 its interaction bullets.
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 empty, so no absence comment is required.

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 (ER lines 358, 359, 363).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Covers the two named delivery models that carry the trial evidence plus session timing — the three parameters a reader would have to fix to act.
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 well more than three actionable implementation aspects, so no set is unused.
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, e.g. action_1_sub’s synthetic psilocybin, eyeshades and music, two monitors for six to eight hours (ER line 358).

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 🟢 Covers the depression, heavy-drinking, and well-being/openness time courses — the only three the ER quantifies (ER lines 165, 193, 394).
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered High (depressive symptoms) → Medium (heavy drinking) → Low (well-being and trait openness), matching the ER benefit 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 Three distinct time-to-effect aspects exist in the ER, so no set is unused.
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; e.g. time_3_sub’s “only after a complete mystical-type experience” comes from ER line 193.
11.5 If the ER does not provide any information on time to effect, the section is removed completely from the Protocol Panel N/A The ER provides time-to-effect information, so the row is correctly retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All eleven items map one-to-one onto the ER Expected Benefits headings (ER lines 155-219).
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present and populated (lines 527-542).
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. 🟢 Items are ER headings reduced to bare facts; no effect sizes, magnitudes, or mechanisms carried over.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content survives; the ER’s ⚠️ Conflicted marker on the depression heading is also dropped.
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. N/A All four tiers have items in the ER, 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 eleven items map one-to-one onto the ER Potential Risks & Side Effects headings (ER lines 240-304).
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present and populated (lines 592-608).
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. 🟢 Items are ER headings reduced to bare facts; relative risks and confidence intervals are all omitted.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 Parenthetical content stripped — ER’s “Cardiac Valvulopathy (Damage to a Heart Valve)” becomes “Cardiac valvulopathy”.
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 All four tiers have items in the ER, so no span needed hiding.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Table and cadence both derive from the ER Monitoring Protocol & Defining Success section (ER lines 412-424).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All nine ER biomarkers listed with targets verbatim: resting blood pressure, QTc, hs-CRP, ALT, eGFR, PHQ-9, GAD-7, trait openness, epigenetic age.
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. 🟢 [monitoring_cadence] (line 727) carries the full ER cadence: 2-4 week baseline, in-session vitals at 30/60/90/120 minutes, scales at day 2, day 8, week 3, week 6 then quarterly through year 1, annual bloods, echocardiogram only after frequent sustained low-dose exposure.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Derived from the qualitative marker list in the ER Monitoring Protocol & Defining Success section (ER lines 428-434).
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All seven ER qualitative markers listed verbatim across qualitative_item_1 to qualitative_item_7.

Issues 21/08/2026 17:28

Pass rate 100.00%. No issues found.

Issues 21/08/2026 17:17

  1. 4.5 — Sheet overflows one A4 page: Total visible text is 841 words and the sheet renders to roughly two A4 pages; the Monitoring “Why” column (lines 637-737), [monitoring_cadence] (lines 743-748, 421 characters) and the protocol/time [sub] cells (lines 454-455, 466-467, 478-479, 496-497, 508-509, 520-521) carry ER sentences verbatim instead of being condensed to the per-section budget.

Fixes 21/08/2026 17:17

  1. 4.5 — Monitoring “Why” column condensed: All nine marker_#_why cells were reduced from verbatim ER sentences to phrase-length entries (e.g. “Psilocybin transiently raises it; a high starting point makes the rise consequential” → “Psilocybin transiently raises it; a high baseline matters”), collapsing most table rows from two lines to one.
  2. 4.5 — Sentence-length marker targets shortened: marker_8_target and marker_9_target were trimmed to “No established target; track change from own pre-session score” and “No established target; track change from own baseline, one provider”, keeping the ER’s “No established target” phrasing.
  3. 4.5 — Monitoring cadence compressed: monitoring_cadence was cut from 421 to 348 characters by tightening the wording (“in the two to four weeks before” → “2–4 weeks before”, “every 3 months through the first year” → “quarterly through year 1”) without dropping any monitoring step.
  4. 4.5 — Protocol and time-to-effect subs condensed: action_1_sub, action_3_sub, time_1_sub and time_3_sub were shortened from full ER sentences to compact clauses, dropping one wrapped line from each protocol-grid row.
  5. 4.5 — Decision-gate items trimmed: Four contraindications and two key interactions were tightened (e.g. “Uncontrolled hypertension (resting blood pressure at or above 140/90 mmHg despite treatment)” → “Uncontrolled hypertension (at or above 140/90 mmHg despite treatment)”), with every threshold, time window, severity class and named example drug retained.