Audit: QRS - Thymalin for Health & Longevity

Audit conducted on 01/09/2026 00:25 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 spans trace to ER text: at_a_glance to ER Conclusion (l.419-423), action cells to ER Protocol (l.328-334), time cells to ER l.363 / l.160 / l.178, benefit and risk items to ER Expected Benefits and Potential Risks headings, gates to ER Key Interactions & Contraindications, markers to the ER Monitoring table (l.385-396).
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.	🟢	The ER’s “⚠️ Conflicted” markers are carried as “(conflicted)” in benefits_low and risks_low; “inferred”, “small, unblinded single-centre series” and “no trial has compared split dosing” are preserved.
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”).	🟢	Contraindications remain contraindications, interactions remain interactions; the conflicted benefit and conflicted risk keep their hedge.
1.4	The QRS does not relabel an ER fact under a different decision category. A “Benefit-Modifying Factor” from ER section is not surfaced as a “Caution”; a “Risk-Modifying Factor” is not surfaced as a “Side Effect”; etc.	🟢	Contraindications come from the ER “Populations who should avoid Thymalin” list, Key Interactions from the ER interaction bullets, Benefits from Expected Benefits, Risks from Potential Risks & Side Effects. No cross-category migration.
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, no NCT identifiers, no expert names and no brand names; the generic drug names in caution_items are all ER-sourced.
1.6	The QRS does not introduce new attributions.	🟢	The only attribution present, “the product information” in marker_11_why, is verbatim from the ER Monitoring table.

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 measured, sceptical register — “almost all from the institute that developed it, and never repeated” mirrors ER l.421.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Ranges, thresholds and course structure are given concretely, giving the reader the material to decide, without hype or discouragement.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	No imperatives or directives anywhere in the content spans.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	Sections state what the evidence records; no “should”, “must”, “recommend”, “consult” or equivalent appears in any content span.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	monitoring_cadence and the protocol cells are stated descriptively, compressing the ER’s passive voice rather than instructing.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns occur in any content span.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Acronyms are spelled out (“high-sensitivity C-reactive protein”, “erythrocyte sedimentation rate”, “total immunoglobulin E”), and “induration” is glossed as “hardened, thickened skin”.
2.8	Information is presented in a concise and very compact manner	🟢	Each benefit and risk tier is a single line item; gate items are bare noun phrases; protocol subs are one to two sentences.
2.9	It DOES NOT address the reader directly	🟢	Confirmed by a full scan of the content spans; 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.	🟢	The sheet supplies dose, route, course length, repeat cadence, twelve biomarkers with functional ranges, and a screening rationale — material for someone intending to act.
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 intramuscular injection course with reconstitution requirements and a twelve-marker panel 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 familiarity with injectables, flow-cytometry subsets and antibody titres; no consumer-grade simplification.
2.13	Framing, takeaways, and risk/benefit weighting throughout the document reflect this audience, including where an intervention’s signal for the average person differs from its signal for this audience.	🟢	at_a_glance leads with the single-source, unreplicated provenance and unverified supply — the decisive weighting for a proactive reader considering an unapproved injectable.
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.	🟢	“Longevity” is used in the title, header and action_2_label; “anti-aging” appears nowhere.
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.	🟢	Uses “intramuscular”, “injection”, “hypersensitivity”, “adverse event”, “lyophilised powder”; no colloquialisms.

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 twelve fixed strings match the template byte-for-byte (lines 445, 492, 543, 635, 659, 839, 576, 609, the four <strong> tier labels, and 663-665).
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 38 template span names present; the repeatable marker_#_* and qualitative_item_# placeholders are expanded to marker_1..12 and qualitative_item_1..5. No template span dropped.
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 footer disclaimer, all CSS and all structural comments (including the template’s “BENEFTIS” comment) are 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 source ER section is empty. The only absent tier, Risks High, is governed by item 13.5 rather than by this item.
4.2	Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label.	🟢	action_1_label “Standard course”, action_2_label “Longevity schedule used by the developers” and action_3_label “Single versus split dosing” are the ER Protocol bold labels verbatim (ER l.328, 329, 334).
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Protocol labels, benefit and risk tier labels, and all twelve marker names are verbatim from the ER.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	A full-file scan returns no emoji codepoints; the ER’s 🟩/🟥/🟨/⚠️ markers were all removed.
4.5	The QRS is designed to render on one A4 page. Any section that has more content in the ER than fits the per-section budget is condensed by the LLM, not extended onto a second page.	🟢	Every section is condensed to its minimum consistent with the mandated coverage: the eleven ER benefit and risk headings collapse into four and three single-line tiers, and protocol subs run one to two sentences.

---

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; the preamble text on line 2 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; none of its values are repeated in the rendered header, footer or 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:04" is quoted, and it contains a colon; all other values are bare and untrimmed of nothing.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: thymalin_2026-0831-2216_Opus_ER.md, matching the ER’s own filename frontmatter.
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 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-0901-0009, correct format.
5.8	The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]”	🟢	Line 7: qrs_creator_ai_nickname: Opus.
5.9	The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT)	🟢	“Opus” is a single word with no version or qualifier.
5.10	The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]”	🟢	Line 8: qrs_creator_ai_fullname: Opus 5.
5.11	The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier (e.g., Opus 4.6, Sonnet 3.2, Grok 4.5, Gemini 3.1, ChatGPT 5.4)	🟢	“Opus 5” is nickname plus version number, with no context-window or build qualifier appended.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9: qrs_filename: thymalin_2026-0831-2216_Opus_QRS.html, matching the file on disk.
5.13	All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting.	🟢	Re-verified across all nine keys; only the colon-bearing duration value is quoted.

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: “Thymalin for Health & Longevity - Quick Reference Sheet”, matching the ER canonical_topic with the ampersand encoded.
6.2	[header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &)	🟢	Line 417: “Thymalin for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “09/01/2026”, the correct reformatting of qrs_creation_date: 2026-0901-0009.
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 (lines 415-428) is structurally identical to the template; the ER’s “Also known as” line 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 three ER Conclusion paragraphs (l.419-423) into what it is, what was reported, who reported it, harms, and supply.
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.	🟢	Restoring immune cells to ER l.419; Soviet-era use and the over-60 follow-up to l.421; single-institute provenance and non-replication to l.421; limited allergic harms and unverified supply to l.423.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “immune cells”, “death rates”, “allergic” replace the ER’s T-lymphocyte and mortality register, and the function of the thymus is glossed inline.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	Refers only to “one long follow-up of adults past 60” — no name, year or sample size.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No fold-changes, percentages, risk ratios or confidence intervals appear.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All eight items map to the ER “Populations who should avoid Thymalin” list (l.305-312) inside that section.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All eight ER bullets are present, and the two absolute contraindications from the prescription-medication list (transplant immunosuppressants, checkpoint inhibitors) are covered by the transplant-recipient and checkpoint-inhibitor items.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Eight <li> elements inside the span (lines 579-604).
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 on the pregnancy bullet (“— listed as a contraindication in the product information…”) and the attributions “in the product information” and the leading “People with” are all 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).	🟢	Preserved: “on any maintenance immunosuppression, at any time post-transplant”, the four named autoimmune conditions, “any prior grade 3 or higher”, the CLL/MGUS pair, “under 14 years”, “severe enough to require an adrenaline autoinjector”.
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 ER identifies eight 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 eleven items map to the ER prescription, over-the-counter, supplement and other-intervention bullets (l.280-301).
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Eleven of the ER’s thirteen interaction bullets are carried; transplant immunosuppressants and immune checkpoint inhibitors are correctly omitted because both are absolute contraindications already in [stop_items].
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Eleven <li> elements inside the span (lines 612-625).
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 the drug or exposure name plus its parenthetical example list; the ER’s “Caution”/”Monitor” verdicts, mechanisms and consequences are all stripped, including the em-dash clause on the immunostimulant bullet.
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 six ER parenthetical drug lists are preserved intact, including the italicised Trametes versicolor and “growth hormone plus metformin”; the five ER bullets without parentheses carry none.
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 ER identifies thirteen such entries and the section is correspondingly populated.
9.8	If the section is left empty, an HTML comment inside the [caution_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g.	N/A	The section is not empty.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER Protocol section	🟢	All three cells draw on the ER Therapeutic Protocol bullets at l.328, 329, 332 and 334.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose/route/duration, repeat cadence, and administration pattern — the only three ER Protocol bullets that state an executable instruction; the remaining bullets are comparisons, pharmacology, or “no data” modifiers.
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 three or more actionable 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 populated; every sentence traces to the ER Protocol bullets, including the morning-injection rationale from the ER “Best time of day” bullet (l.332).

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	🟢	Within-course marker and inflammatory-phase change (ER l.363, l.160), the 6-8 year mortality horizon (ER l.363, l.168), and the burn graft/discharge timing (ER l.178).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered High (severe respiratory infection), Medium (mortality and age-related illness), Low (severe burns), 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	The ER supplies three or more time-to-effect aspects and 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.	🟢	All nine spans populated with ER-traceable content; the subs preserve the ER’s hedges (“Inferred from year-scale follow-up”, “small, unblinded single-centre series”).
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 (l.363), so the section is retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All nine benefit statements are the ER Expected Benefits sub-headings (l.158-210).
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present and populated (lines 545-569).
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 tier is a semicolon-separated run of bare ER headings; every “Magnitude” figure, mechanism sentence and study description from the ER is dropped.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	The ER’s parenthetical glosses (“pus-forming”, “a skin infection”, “bone infection”) are all stripped; the only retained parenthesis is the ER’s “⚠️ Conflicted” evidence flag rendered as “(conflicted)”, which items 1.2 and 1.3 require be carried.
12.5	If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing.	N/A	All four ER benefit tiers contain items, so no span needed hiding.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All six risk statements are the ER Potential Risks & Side Effects sub-headings (l.232-264).
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present (lines 637-653).
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 tier is a semicolon-separated run of bare ER headings; the ER’s mechanism paragraphs and “Magnitude” notes are dropped.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No frequency, grade or study parenthetical is carried; the only retained parenthesis is the ER’s “⚠️ Conflicted” evidence flag on the autoimmune risk, rendered as “(conflicted)” as items 1.2 and 1.3 require.
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”; line 637 correctly reads <span data-qrs-var="risks_high" style="display: none"></span> with the template <li> removed and no empty-state text.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	The table and cadence come from the ER Monitoring Protocol & Defining Success section (l.377-396).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All twelve ER biomarker rows are present in order, with the ER’s “Optimal Functional Range” values and “Why Measure It?” text carried verbatim into Target and Why.
14.3	[monitoring_cadence] is populated with the monitoring cadence/frequency derived from the ER Monitoring section. It is not left with placeholder text or empty.	🟢	Line 828-833 condenses ER l.379 and l.381: baseline, end of course, 4-6 weeks, every 6-12 months, autoimmune markers annually and on symptoms.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Drawn from the ER’s “Qualitative markers worth tracking alongside the laboratory panel” list (l.400-404).
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All five ER qualitative bullets are present in order, with the induration gloss retained in condensed form.

Issues 01/09/2026 00:25

Pass rate 100.00%. No issues found.

Issues 01/09/2026 00:15

1. 4.2 / 4.3 — Protocol cell labels invented: action_1_label, action_2_label and action_3_label (lines 449, 463, 479) read “Dose”, “Route & course” and “Repetition”, none of which is a bold label in the ER Therapeutic Protocol section, whose bullets are labelled “Standard course”, “Longevity schedule used by the developers”, “Best time of day” and so on.
2. 2.7 — Unglossed jargon “induration”: qualitative_item_5 (line 864) carries the technical term “induration” but drops the ER’s own plain-language gloss “(a hardened, thickened patch of skin)” from ER line 404.

Fixes 01/09/2026 00:15

1. 4.2 / 4.3 — Protocol cell labels taken from ER: Replaced the invented labels “Dose”, “Route & course” and “Repetition” with the ER Therapeutic Protocol bold labels “Standard course”, “Longevity schedule used by the developers” and “Single versus split dosing”, and re-cut the three value/sub pairs so each cell carries the content of its own ER bullet.
2. 2.7 — Unglossed jargon “induration”: Restored the ER’s plain-language gloss in qualitative_item_5, changing “redness, itching or induration” to “redness, itching or induration (hardened, thickened skin)”.