Audit: QRS - Cortexin for Health & Longevity
Audit conducted on 01/09/2026 01:14 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. | 🟢 | Protocol cells trace to ER lines 348, 350, 358; time cells to ER 383, 385, 405; benefit and risk items to the ER Expected Benefits and Potential Risks & Side Effects headings; monitoring rows to the ER biomarker table (ER 437–446); cadence to ER 433. |
| 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 “No established functional target — track change from the individual’s own baseline” is carried for markers 9 and 10; the ER’s tier hedging is preserved by the tier labels. |
| 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 absolute (pregnancy, breastfeeding, hypersensitivity); the ≥180/110 mmHg threshold and INR >3.0 qualifier are unchanged. |
| 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 only from the ER’s “Populations who should avoid Cortexin” list; interactions only from the ER interaction bullets; no Benefit- or 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 or NCT identifiers appear. Named agents (valproate, carbamazepine, sertraline, escitalopram, amlodipine, lisinopril, procaine, diphenhydramine, pseudoephedrine, caffeine, Rhodiola rosea, Cerebrolysin, Cellex, citicoline, Ginkgo biloba, warfarin, apixaban) all appear in ER 299–317 for the same interaction. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions of any kind are present outside the template’s own AI4L link. |
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, evidence-weighted register matching the ER, including the ER’s own caveat that almost all research comes from one region. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Tiered benefits and risks, quantified monitoring targets and a plain-language At-A-Glance combine expert framing with accessibility. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Content is stated as evidence and observed practice, not instruction. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No imperative or prescriptive verbs appear in the content spans; gates and cadence are presented as facts drawn from the ER. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No instances of “should”, “recommended”, “advised” or equivalent in any populated span. |
| 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 | 🟢 | Remaining technical terms (“asthenia”, “geroprotective”, “transmissible spongiform encephalopathy”) are the ER’s own verbatim section headings, required by items 12.3 and 13.3; the At-A-Glance is fully de-jargoned. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Every gate, benefit and risk item is a bare noun phrase; monitoring “why” cells are single clauses. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed by full-text scan: no “you”, “your”, “we” or “our”. |
| 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. | 🟢 | Protocol, monitoring panel and qualitative tracking list assume a self-directed, risk-aware adult. |
| 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. | 🟢 | A 10-day daily intramuscular injection course and a 10-marker monitoring panel are presented 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. | 🟢 | Content density, biomarker targets and injection logistics are pitched well above 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. | 🟢 | At-A-Glance and time_3 both foreground the key audience-specific finding — that without brain disease work-capacity gains fade within about two months. |
| 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 ER’s “geroprotective effect on the aging brain” heading is carried verbatim. |
| 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. | 🟢 | “intramuscularly”, “injection”, “hypersensitivity”, “anaphylaxis”, “glycated hemoglobin” throughout; the plain-language At-A-Glance wording is mandated by item 7.4. |
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 match the template byte for byte (QRS lines 440, 477, 519, 539, 552, 574, 597–599, 723). |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | Programmatic comparison against the template: 0 missing, 0 extra; indexed placeholders expanded to marker_1–10 and qualitative_item_1–5. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | A full diff against the template shows differences only inside the metadata block and the populated variable spans; all CSS, structure, comments and the 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; the only unpopulated tier (risks High) is governed by item 13.5, which mandates hiding rather than empty-state phrasing. |
| 4.2 | Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label. | 🟢 | “Standard adult course”, “High-dose regimen”, “Best time of day”, “Time to effect”, “Cycling is built into the design” and “Effect duration between cycles” are the ER’s bold labels verbatim (ER 348, 350, 358, 383, 385, 405). |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | No invented labels; gate and tier item text derives from the ER’s own bold labels and section headings. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | Character-level scan returns no emoji; the ER’s “⚠️ Conflicted” markers were correctly dropped from the anxiety/depression and seizure items. |
| 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 item is reduced to a bare noun phrase; interaction drug lists are trimmed from three named agents to one or two, and monitoring “why” cells to single clauses. The 10 monitoring rows and 10 interaction items are mandated by items 14.2 and 9.2 and cannot be reduced further without breaching them. |
5. Metadata
| # | Description | Result | Comments |
|---|---|---|---|
| 5.1 | The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content. | 🟢 | Lines 2–14; the only preceding line is the doctype. |
| 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 “QRS — Metadata” caption precedes the opener. |
| 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. | 🟢 | The block is an HTML comment; the only values echoed on the sheet are the creation date and model name, which items 6.3 and 6.4 explicitly require. |
| 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 nine values are trimmed; only duration: "00:04" is quoted, correctly, because it contains a colon. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Line 4: er_filename: cortexin_2026-0831-2218_Opus_ER.md, matching the ER frontmatter filename value. |
| 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-0107, 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” — single word, no version. |
| 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, no context-window or other qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9: qrs_filename: cortexin_2026-0831-2218_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; git_user: evipedia-5 and git_issue: 5675 are correctly unquoted. |
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: “Cortexin for Health & Longevity - Quick Reference Sheet”; ampersand correctly 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: “Cortexin for Health & Longevity”, matching ER frontmatter canonical_topic. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: 09/01/2026, correctly derived from qrs_creation_date 2026-0901-0107. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Line 425: “Opus 5”, matching the frontmatter value. |
| 6.5 | No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. | 🟢 | Header holds only the title and the template subline; the ER’s “Also known as” line (ER 32) 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 |
🟢 | Five clauses map one-to-one onto ER 478–484: what it is and how it is given, strongest evidence, the healthy-adult picture, harms, and the evidence-base caveat. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | Word count verified programmatically: exactly 60 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | “cattle brain cortex … short courses” ER 478; “stroke caused by a blocked artery” ER 478; “consistent but small” ER 478; “fade within about two months” ER 480; “harms few, mostly allergic” ER 482; “one region” ER 484. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | “ischemic stroke” rendered as “a stroke caused by a blocked artery”, “cognitive screens” as “thinking-test gains”, “chronic cerebrovascular disease” as “brain blood flow is long reduced”; no acronyms present. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No author names, years, sample sizes or p-values. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | Only the qualitative “consistent but small”; no numeric effect estimates. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All six items map to the “Populations who should avoid Cortexin” list at ER 319–326. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All six ER entries are present, none added: pregnancy, breastfeeding, hypersensitivity, procaine hypersensitivity, uncontrolled hypertension, therapeutic anticoagulation. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Six <li> elements at QRS lines 542–547. |
| 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 em-dash clauses (“— contraindicated in labeling for absence of clinical data”, “— labeling directs stopping breastfeeding…”) are stripped; no dash-led clause remains in any item. |
| 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). | 🟢 | “any trimester”, “(persistently ≥180/110 mmHg) until controlled”, “international normalized ratio above 3.0 (intramuscular route)” and “where procaine is the diluent” are all retained. |
| 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 list. |
| 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 six such populations, and the section is correspondingly populated rather than 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 interaction bullets at ER 299–317. |
| 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 carried. The procaine-diluent and anticoagulant entries are distinct ER bullets (ER 305, 317) from the corresponding contraindication populations (ER 324, 326), so no true duplicate is present. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Ten <li> elements at QRS lines 555–564. |
| 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 item is a class label plus example agents; the ER’s “Caution.”/”Monitor.” rationale sentences and the Khabirov citation are stripped. No dash-led clauses. |
| 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). | 🟢 | Example drug lists are retained for all ten items, trimmed from three named agents to one or two for the page budget, never dropped entirely; the ER’s unparenthesised “Additive supplement effects” bullet gains its named examples from the ER body text. |
| 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; 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 interactions, and the section is correspondingly populated rather than empty. |
| 9.8 | If the section is left empty, an HTML comment inside the [caution_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. | N/A | The section is not 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 bullets at ER 348, 350 and 358. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Standard adult course, high-dose regimen and timing are the three aspects a non-acute reader can act on; the split-dose and intravenous regimens are acute-stroke inpatient variants and the remaining bullets are explicit null findings (half-life, pharmacogenetics, sex-based dosing). |
| 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 contains thirteen bullets, well above three, and all three action sets are populated. |
| 10.4 | All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. |
🟢 | All nine fields carry ER-derived content: “10 mg intramuscularly once daily” / “10 consecutive days; 1–2 mL saline or water” (ER 348), “20 mg daily for 10 days” / “Symptom and sleep benefit dose-dependent” (ER 350), “Morning” / “Sleep and fatigue outcomes improved on morning dosing” (ER 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 | 🟢 | Onset within the course (ER 405), the cycling schedule (ER 383) and effect duration between cycles (ER 385) — the three timing bullets that carry actionable content, against null bullets such as “No withdrawal syndrome” and “No taper required”. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Onset first, as it applies across all benefit tiers including the High-tier stroke recovery; the cycling schedule next, tied to “the trials showing the largest effects” (ER 383); duration last, tied to the Low-tier work-capacity benefit (ER 385). |
| 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 timing aspects and all three sets are populated. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | All nine fields carry ER-derived content: “During the 10-day course” / “Largest gains at course end”; “Two courses, 10 days apart” / “Or repeat courses at six months”; “Fades over roughly two months” / “In adults without neurological disease” (ER 480 generalises the finding to adults without neurological disease). |
| 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 an explicit “Time to effect” bullet at ER 405, so the section is correctly retained. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | All thirteen items are the ER’s own benefit subsection headings (ER 137–213), tier for tier. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans present and populated at QRS lines 521–532. |
| 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 item is a bare noun phrase; every Magnitude: figure from the ER (1–4 point screen gains, 2.8-fold vs 1.3-fold, 86.5–93.6%) is correctly omitted. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses appear in any benefit item; the ER’s “⚠️ Conflicted” markers on the anxiety/depression and epilepsy headings are also stripped. |
| 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 (1 High, 4 Medium, 5 Low, 3 Speculative), so no tier needs hiding. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | All seven items are the ER’s own risk subsection headings (ER 241–279), tier for tier. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans present at QRS lines 576–587. |
| 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 item is a bare noun phrase; the “below 1 in 10,000” frequency class and the 17–24% adverse-event tally are correctly omitted. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses in any risk item; the ER’s glossary parentheses (anaphylactic shock, angioedema, urticaria, prions) are stripped along with the “⚠️ Conflicted” marker. |
| 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 237); the [risks_high] span at QRS line 576 carries style="display: none" with no empty-state text. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Table rows and cadence derive from the ER Monitoring Protocol & Defining Success section (ER 433–446). |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All ten rows of the ER biomarker table are carried in ER order, with ranges intact (MoCA 26–30, MMSE 28–30, BP 110–125/70–80 mmHg, eosinophils 0.0–0.15 ×10⁹/L, IgE <60 IU/mL, HbA1c 4.8–5.4%, hsCRP <1.0 mg/L, homocysteine <8 µmol/L, NSE and MFI as own-baseline tracking). |
| 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 line 717 condenses ER 433: “Baseline, day 10, 4–6 weeks, then before each repeat course at 3–6 month intervals; blood count and metabolic panel annually, or immediately if a reaction occurs”. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | The five items are the ER’s qualitative marker bullets at ER 450–454. |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All five are carried verbatim and in ER order: sleep quality and sleep latency, daytime energy and endurance, word-finding and recall, mood and anxiety after day 14, injection-site comfort and early allergic signs. |
Issues 01/09/2026 01:14
Pass rate 100.00%. No issues found.