Audit: QRS - Wellmune for Health & Longevity
Audit conducted on 16/09/2026 03:25 using AI4L / Opus 5
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. | 🟢 | Every populated variable traces to ER text: protocol actions to ER lines 297–302, time-to-effect to ER line 334, benefits to ER lines 147–199, risks to ER lines 216–250, gates to ER lines 264–281, markers and cadence to ER lines 355–366, qualitative items to ER lines 370–375, at-a-glance to ER lines 392–398. |
| 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 ER phrasing is carried through, e.g. “No trial has compared timings” (QRS line 484) mirrors ER line 302; “no trial measured a symptom endpoint earlier” (QRS line 519) mirrors ER line 337. |
| 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”). | 🟢 | All five ER avoid-populations remain hard contraindications; all ten ER caution/monitor interactions remain in the Key Interactions gate. No directional shift found. |
| 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. | 🟢 | Gate content is drawn solely from ER Key Interactions & Contraindications; no Benefit- or Risk-Modifying Factor (ER lines 204–209, 255–259) appears in any gate or risk tier. |
| 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, citations, author names, NCT identifiers or product brand names anywhere in the body. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions of any kind are present beyond the template’s AI4L link and model name. |
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. | 🟢 | Measured, hedged, evidence-first register throughout, matching the ER. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Tier-ranked benefits and risks plus concrete doses, durations and marker targets give an objective, actionable read. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Statements are descriptive of what trials did (“The dose used in the majority of published trials”, QRS line 456), not instructions. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No imperative clinical directives; the monitoring cadence describes what was done rather than instructing the reader. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No occurrence of “recommend”, “advise”, “should” or “must” in the document body. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns anywhere in the document. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms are confined to the Monitoring table, where they are the ER’s own biomarker names. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Benefits and risks reduce to one line per tier; gate items are stripped to the key fact. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed — no direct address. |
| 2.10 | The target audience is health- and longevity-oriented adults who are risk-aware, proactive, and actively seeking to optimize health or apply the intervention under review. | 🟢 | Functional marker targets (hs-CRP below 1.0 mg/L, HbA1c 4.8–5.4%) and the funding-conflict note address a risk-aware optimiser. |
| 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. | 🟢 | An eight-marker baseline panel and daily symptom logging assume high willingness to act. |
| 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 (fungal-assay interference, calcineurin-inhibitor window, HOMA-IR) is beyond 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. | 🟢 | The at-a-glance separates the durable symptom-burden finding from the weaker prevention claim and flags sponsor-dominated evidence. |
| 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 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)”; “oral” / “administered orally” not “taken by mouth” / “given by mouth”; “injection” not “shot”; “adverse event” not “bad reaction”). This holds on EVERY surface, including the QRS lede — the stricter plain-language bar (see 2.7) does not license lay phrasing for route of administration. Direct quotes from sources are exempt. | 🟢 | No “pill”, “shot”, “by mouth” or “bad reaction”. Clinical register is used throughout (e.g. “immunoglobulin E”, “calcineurin inhibitor”, “insulin resistance”). |
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 byte-identical to the template (QRS lines 445, 491, 542, 571, 595, 622, 645, 649–651, 781 and the four tier labels in each of Benefits and Risks). |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All 34 template variable names are present; the repeatable marker_#_* and qualitative_item_# rows are instantiated as marker_1–8 and qualitative_item_1–6. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | A structural diff against the template shows the head/style block identical apart from page_title, and the body skeleton identical apart from the repeated marker and qualitative rows. The website="evidence_review", website="audit" and website="full_review" spans and the footer disclaimer 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 that maps to a QRS variable is empty; the ER contains no empty-state phrasing of this kind. The High risk tier carries an explanatory paragraph (ER line 218) rather than an empty state, and is handled under 13.5. |
| 4.2 | Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label. | 🟢 | Protocol labels “Standard immune dose”, “Higher doses by indication” and “Best time of day” are verbatim ER bold labels (ER lines 297, 298, 302); all eight Monitoring marker names are verbatim ER Biomarker column values (ER lines 359–366). |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | No label is altered. The three Time-to-Effect labels (“Infection symptoms”, “Hay fever symptoms”, “Insulin resistance”) name the three aspects the ER’s single Time to effect bullet enumerates (ER line 334), which supplies no per-aspect bold label. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji characters present; the ER’s 🟩/🟥/🟨 tier markers and ⚠️ conflict flags were correctly dropped. |
| 4.5 | The QRS is designed to render on one A4 page. Any section that has more content in the ER than fits the per-section budget is condensed by the LLM, not extended onto a second page. | 🟢 | Every section is condensed rather than transcribed: benefits and risks collapse to one line per tier, gate items are stripped to the key fact, protocol and time subs run one to two sentences, and the cadence paragraph is reduced to a single sentence pair. No section carries ER prose at full length. |
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 comment opens at QRS line 2, immediately after <!doctype html> on line 1, and closes at line 14 before any other content. |
| 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 --- at line 3, closing --- at 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. | 🟢 | It is inside an HTML comment and is not duplicated in the header, footer or any other element. |
| 5.4 | All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. | 🟢 | Only duration: "00:03" is quoted, and it contains a colon requiring YAML quoting. All other values are bare and trimmed. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Line 4: er_filename: wellmune_2026-0916-0009_Opus_ER.md, matching the source ER’s own filename field (ER line 17). |
| 5.6 | Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” | 🟢 | Line 5: qrs_prompt_version: 26.9.11, matching the 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-0916-0312, in the required 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 plus version number, with no trailing qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9: qrs_filename: wellmune_2026-0916-0009_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 &) |
🟢 | QRS line 22: Wellmune for Health & Longevity - Quick Reference Sheet, matching ER canonical_topic (ER line 8) 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 &) |
🟢 | QRS line 417: Wellmune for Health & Longevity. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | QRS line 421: 09/16/2026, the correct reformatting of qrs_creation_date: 2026-0916-0312. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | QRS 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 (QRS lines 415–428) is structurally identical to the template; the ER’s “Also known as” line (ER line 30) was 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 |
🟢 | All four sentences map onto ER Conclusion paragraphs (ER lines 392, 394, 396, 398), preserving their order and weighting. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 59 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Non-absorption and first-line priming → ER line 392; symptom-burden versus prevention → ER line 392; mood, hay fever, blood pressure and waist size at higher doses → ER line 394; safety least contested → ER line 396; sponsor-dominated evidence → ER line 398. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms. Plain substitutions are used throughout (“first-line defence cells”, “cold symptoms”, “hay fever”, “waist size”). |
| 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 numeric results; the ER’s odds ratios and percentages are omitted. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All five items map to the ER’s “Populations who should avoid Wellmune” list (ER lines 277–281). |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All five ER avoid-populations are present, none added: yeast allergy, transplant recipients, active fungal workup, active moderate-to-severe IBD, pregnancy. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Five well-formed <li> elements inside the stop_items span (QRS lines 573–591). |
| 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 dashes or trailing clauses. The ER’s rationale “for whom no controlled safety data exist at supplemental doses” (ER line 281) and the calcineurin-inhibitor gloss (ER line 278) are correctly stripped. |
| 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). | 🟢 | The 12-month transplant window, the calcineurin-inhibitor condition, the “moderate-to-severe” severity class, the CDAI > 220 and partial Mayo ≥ 6 thresholds, and the immunoglobulin E / skin-prick confirmation are all preserved. |
| 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 contraindication 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 five 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 empty. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All ten items map to the ER’s interaction bullets (ER lines 264–273). |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | All ten ER interaction bullets are present and none duplicates a contraindication; the echinocandin entry is a distinct ER bullet from the fungal-workup contraindication. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Ten well-formed <li> elements inside the caution_items span (QRS lines 597–613). |
| 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 “— caution:” / “— monitor:” clause and its mitigation sentence is stripped; no dashes or trailing rationale 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). | 🟢 | All six ER example-drug lists are preserved intact (immunosuppressants, corticosteroids, checkpoint inhibitors, echinocandins, antihypertensives, NSAIDs, antihistamines, competing immune supplements); only the explanatory gloss on checkpoint inhibitors is trimmed. |
| 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 list uses no ranking notation inside parentheses; all parenthetical content is already comma-separated. |
| 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. |
| 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 action sets trace to ER Therapeutic Protocol bullets (ER lines 297, 298, 302). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Standard dose, dose escalation by indication, and administration timing are the three actionable bullets; the remaining ER bullets are comparative, pharmacokinetic or modifier content rather than implementation steps. |
| 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 at least three 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 action variables carry substantive ER-derived content; none is a placeholder. |
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 | 🟢 | Infection symptoms at 12 weeks, hay fever at 4 weeks and insulin resistance at 8 weeks are the three clinical endpoints in ER line 334; the 10–14 day biomarker change is folded into the first sub rather than occupying a cell. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Infection symptoms (ER High tier) first, then hay fever and insulin resistance (both ER Medium tier) in the ER’s own within-tier order. |
| 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 more than three 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 time variables carry substantive ER-derived content; the durations match ER lines 334 and 337 exactly. |
| 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 explicit time-to-effect data (ER line 334), so the section is correctly retained. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | All eight benefit statements correspond to the eight ER Expected Benefits sub-headings (ER lines 149–199). |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans present and populated (QRS lines 544–564). |
| 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-joined list of the ER sub-headings alone; all magnitude paragraphs, funding notes and mechanism prose are omitted. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses appear in any benefits item. |
| 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 benefits span needs hiding. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | All five risk statements correspond to the five ER risk sub-headings (ER lines 222–250). |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans present (QRS lines 624–639). |
| 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 reduces to the ER sub-headings alone; the EFSA reference, positive-predictive-value figures and Dectin-1 mechanism prose are all omitted. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses appear in any risks item. |
| 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 (ER line 218); QRS line 624 is <span data-qrs-var="risks_high" style="display: none"></span> with no empty-state text. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | All rows and the cadence come from ER Monitoring Protocol & Defining Success (ER lines 353–366). |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All eight ER table rows are present in ER order, with Optimal Functional Range and Why Measure It? carried across verbatim; only the Context/Notes column is dropped. |
| 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. |
🟢 | QRS lines 771–775 state baseline before starting, repeat at 12 weeks, then every 6–12 months, with the fungal-marker re-check condition — matching ER lines 353 and 355. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | All six items come from the qualitative-marker list in ER Monitoring Protocol & Defining Success (ER lines 370–375). |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All six ER qualitative markers are present verbatim and in ER order (QRS lines 784–813). |
Issues 16/09/2026 03:25
Pass rate 100.00%. No issues found.
Issues 16/09/2026 03:16
- 1.1 / 1.3 / 7.3 — At-a-glance overstates safety: Line 437 states “Safety is uncontested”, while the ER hedges at line 396 with “Safety is the least contested part”; the QRS converts a relative judgement into an absolute one.
Fixes 16/09/2026 03:16
- 1.1 / 1.3 / 7.3 — At-a-glance safety claim rehedged: Changed “Safety is uncontested” to the ER’s own wording “Safety is the least contested part”, and trimmed “in people” from the preceding sentence to keep the lede at 59 words, within the 60-word limit.