Audit: QRS - PE-22-28 for Health & Longevity
Audit conducted on 11/14/2026 13:39 using AI4L + evidence-mcp / Opus 5.5
Summary
| Items | Count |
|---|---|
| Total | 97 |
| Passed | 87 |
| 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. | 🟢 | All protocol doses (3.0 µg/kg × 4 days; single 3.0–4.0 µg/kg), the route, the time-to-effect values, the four monitoring markers with their ranges, the cadence, the six contraindications, the nine theoretical interactions, and all benefit/risk items trace to ER Therapeutic Protocol, Practical Considerations, Monitoring Protocol & Defining Success, Key Interactions & Contraindications, Expected Benefits and Potential Risks & Side Effects. |
| 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. | 🟢 | Hedges are carried on every surface that must carry them: lede (“Everything known comes from cells and mice”, “no safety work exists in any species”), Protocol subs (“no validated human equivalent exists”), Time to effect (“Unknown”, “No human time course has been measured”), Monitoring cadence (“No cadence rests on evidence”), and the “Theoretical (inferred from mechanism)” sub-heading over the interaction list. |
| 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”). | 🟢 | The ER’s avoid-list is carried as Contraindications without softening; no “unknown” is upgraded to a positive claim; the mouse-only basis of every dose is kept in the sub cells. |
| 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 PE-22-28”; interactions only from the ER’s theoretical-interaction list; no Benefit- or Risk-Modifying Factor appears anywhere on the sheet. |
| 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 PMID, citation, author name, NCT identifier or brand name appears in the QRS at all. |
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. | 🟢 | Flat, evidentiary register matching the ER’s “laboratory hypothesis rather than a usable one” framing. |
| 2.2 | The tone of the QRS is expert, accessible, objective, and data-driven | 🟢 | Doses, ranges and time courses are given with their species and basis. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | No instruction is issued to the reader; the Monitoring cadence is prefaced by “No cadence rests on evidence”. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | Items are stated as populations, markers and measures, not as directions to a patient. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No “recommended”, “should”, “advised” or “consider” anywhere in the variable content. |
| 2.6 | The QRS never addresses the reader directly — it presents evidence, not guidance | 🟢 | No second-person pronoun on the sheet; gate items use “Anyone with …” as in the ER. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms retained are ER labels carried verbatim (sinus node disease, syncope, methylxanthines, insulin secretagogues); the lede uses plain wording throughout. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Gate, Benefit and Risk items are reduced to the key fact; the lede is 63 words. |
| 2.9 | 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 addresses the decision an informed self-experimenter faces: no human data, research-chemical supply, inferred hazards. |
| 2.10 | The target audience is willing to employ lifestyle and behavioral changes as well as follow protocols that may be inconvenient, costly, or require effort. | 🟢 | Electrocardiogram, fasting glucose, HbA1c and weekly structured mood scoring are presented without hedging on effort. |
| 2.11 | 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 assumes familiarity with biomarker tracking and rodent-vs-human evidence grading. |
| 2.12 | 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. | 🟢 | Benefits sit entirely in Speculative, risks in Low/Speculative, and the lede states the absence of human and safety data — the weighting this audience needs. |
| 2.13 | 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 title carries the ER’s “for Health & Longevity”. |
| 2.14 | 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. | 🟢 | “Intraperitoneal injection”, “intraperitoneally”, “oral tube feeding” and “oral gavage” are the ER’s own formal terms; no colloquial route wording appears, including in the lede. |
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 headings, gate heads, tier labels and the three column headers are byte-identical to the template (QRS lines 452, 502, 544, 568, 587, 625, 648, 652–654, 718). |
| 3.2 | Every element carrying a data-qrs-var attribute in [qrs_template] is present in the QRS with the same name | 🟢 | Scripted comparison: all 40 template names present; the only additions are the prescribed numbered expansions of marker_#_* (1–4) and qualitative_item_# (1–6). |
| 3.3 | Everything outside the data-qrs-var spans — markup, text, styles, comments — is as in the template; spans that no checklist item addresses are left unchanged as well | 🟢 | Scripted diff with span contents masked shows only prettier line-wrapping whitespace, the prescribed style="display:none" attributes, and the repeated marker rows / qualitative <li> items. Styles, comments, footer and website="…" spans are unchanged. |
4. Formatting
| # | Description | Result | Comments |
|---|---|---|---|
| 4.1 | An empty ER section never produces visible empty-state text in the QRS: the corresponding region is hidden or left empty. Phrases such as “None documented in human trials to date” or “Not formally studied” appear only where the ER uses them for a fact the QRS carries over. | 🟢 | The ER’s empty “Documented interactions:” group yields an empty caution_items span holding only an HTML comment (line 590); the empty High/Medium/Low benefit tiers and High/Medium risk tiers are hidden, not filled with empty-state text. |
| 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 “Published four-day regimen”, “Published regimen, acute” and “Route” are the ER’s bold labels verbatim (ER lines 302–310); interaction and contraindication items reuse the ER’s bold labels. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Only optional glosses inside parentheses were trimmed (e.g., “(SSRIs — drugs that raise serotonin, e.g., fluoxetine, sertraline)” → “(e.g., fluoxetine, sertraline)”); at least one example is kept in every list and the retained words are the ER’s own, unshortened. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | Scripted scan finds no emoji codepoint in the file; the ER’s 🟩/🟨/🟥 and ⚠️ markers were not carried over. |
| 4.5 | The QRS is designed to render on one A4 page. It fails this item only for one of four things: a trailing clause after a dash, an optional gloss, an example list left untrimmed, or a repetition. Nothing else is cut to fit. | 🟢 | No trailing dash clause in any gate, benefit or risk item; glosses dropped; example lists are the ones 9.7 requires preserved; no repeated content across cards. |
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. | 🟢 | Single comment at 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 title text sits on line 2 before 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. | 🟢 | It is an HTML comment and no sheet element repeats its 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:04", which contains a colon and therefore requires quoting. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Line 4: er_filename: pe_22_28_2026-1027-0351_Opus_ER.md, matching the audited ER. |
| 5.6 | Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” | 🟢 | Line 5: qrs_prompt_version: 26.11.9, matching this 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-1114-1333, 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 the full name without the version number, with all remaining words joined by hyphens (e.g., Opus, Sonnet, Grok, Gemini-Flash, GPT); when the full name has no version number or is “Unknown”, the nickname equals the full name | 🟢 | “Opus 5.5” minus the version yields “Opus”, exactly as stated. |
| 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. |
| 5.11 | The full name of the AI consists of the model name (the word or words directly before the version number, leaving out the first if there is more than one, e.g., Claude Opus 5.5 → Opus 5.5), the model version number and the variant (if any) as stated in the system prompt or developer instructions of the creating model, with every word capitalized and without product, effort or pricing names (e.g., Opus X.Y, Sonnet X.Y, Grok X.Y, Gemini X.Y Flash, GPT X.Y), the model name alone when the system prompt or developer instructions name a model without a version number (e.g., Grok), or “Unknown” when neither the system prompt nor the developer instructions of the creating model name a model | 🟢 | “Opus 5.5” is name + version, capitalized, with no product, effort or pricing name attached. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9: qrs_filename: pe_22_28_2026-1027-0351_Opus_QRS.html, matching the file on disk. |
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 21: “PE-22-28 for Health & Longevity - Quick Reference Sheet”, matching 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 423: “PE-22-28 for Health & Longevity”. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 427: “11/14/2026” from 2026-1114-1333. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Line 431: “Opus 5.5”, matching the frontmatter. |
| 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’s subline; the ER’s “Also known as” names are not carried over. |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] opens by saying what the intervention is — its kind (e.g., dietary supplement, prescription medication, peptide, plant, procedure, practice) — and what it is used for, in plain language, before any verdict on the evidence | 🟢 | Opens “PE-22-28 is a laboratory-made seven-amino-acid peptide, sold as a research chemical, built to block a potassium channel … with mood as the intended target” — kind and purpose before any evidence verdict. |
| 7.2 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Mirrors the Conclusion’s three load-bearing points: laboratory origin and target, cells-and-mice-only record with no human or safety data, and “laboratory hypothesis rather than a usable one”. |
| 7.3 | [at_a_glance] is no longer than 70 words | 🟢 | Scripted count: 63 words. |
| 7.4 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Seven-amino-acid fragment and channel target (ER 426, 36); research-chemical sale (ER 38, 342); cells-and-mice record and no registered human study (ER 426); no safety work in any species (ER 426); closing verdict (ER 430). |
| 7.5 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronym appears; “potassium channel that keeps nerve cells quiet” replaces the ER’s TREK-1/K2P naming. |
| 7.6 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No study, year or sample size is named. |
| 7.7 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No numeric effect or statistic appears. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All six items come from that section’s “Populations who should avoid PE-22-28” list (ER lines 262–274). |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All six ER populations are present, none added: epilepsy/prior seizure, prior stroke or TIA, sinus node disease/bradycardia/syncope, inherited channel disorder or ventricular fibrillation, pregnancy/breastfeeding/conception, chronic pain. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Six <li> elements inside the stop_items span (lines 571–582). |
| 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. | 🟢 | Each item is the ER’s bold label alone; the “Inferred from …; no human data” rationale and all citations are stripped, and no item carries a dash clause. |
| 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 threshold qualifier “(resting heart rate below 50 beats per minute)” is kept intact; only the plain-language glosses “(weak natural pacemaker)”, “(fainting)” and “(channelopathy)” were trimmed, which 4.5 permits. |
| 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 avoid-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 six such populations and the section is populated accordingly, not 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 left empty. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All nine items come from that section’s theoretical-interaction list (ER lines 244–260). |
| 9.2 | [caution_items] represent the ER’s documented interactions — the items under its “Documented interactions:” label — excluding any that are already listed as Contraindications and any entry phrased as no interaction found | 🟢 | The ER’s only documented-interaction entry is “None identified. No human interaction or pharmacokinetic study … has been published” (ER line 240), so the span is correctly left with no item. |
| 9.3 | [caution_theoretical_items] represent the ER’s theoretical interactions — the items under its “Theoretical interactions (inferred from mechanism, not studied in humans):” label | 🟢 | All nine ER entries are present in ER order: SSRIs, methylxanthines, riluzole, mood stabilizers, volatile anesthetics, polyunsaturated fatty acids, quercetin, insulin secretagogues, other stacked peptides. |
| 9.4 | The ER placeholder “None identified” is never an item | 🟢 | “None identified” does not appear anywhere in the QRS. |
| 9.5 | Individual [caution_items] and [caution_theoretical_items] are formatted as <li></li>. The template’s bold “Theoretical (inferred from mechanism)” sub-heading is the only marker of the second list’s status: no item carries “(theoretical)”, “inferred from” or a mechanism clause | 🟢 | Nine <li> elements (lines 600–614); no item carries “(theoretical)”, “inferred from” or a mechanism clause, and the template sub-heading is intact at line 597. |
| 9.6 | 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-class label with its examples; the ER’s IC50 values, “Inferred additive blockade” clauses, consequences and citations are stripped, and no dash clause remains. |
| 9.7 | Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely). | 🟢 | Every example list is preserved: fluoxetine/sertraline, caffeine/theophylline, lithium/valproate/carbamazepine, sevoflurane/isoflurane/halothane, EPA and DHA from fish oil plus α-linolenic acid, glipizide/repaglinide, Selank/Semax. |
| 9.8 | 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. |
| 9.9 | If the ER’s theoretical group is empty, the whole Theoretical block — the caution_theoretical span with its sub-heading and list — is hidden with style="display:none", not removed: its spans stay in place, empty. |
N/A | The ER’s theoretical group holds nine entries, so it is not empty. |
| 9.10 | 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 not empty: the ER’s nine mechanism-inferred interactions are carried under the Theoretical sub-heading. |
| 9.11 | 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, and the Theoretical block is hidden per 9.9. E.g. | N/A | The section is not left empty. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Therapeutic Protocol section |
🟢 | All three sets come from ER lines 302–310 (“Published four-day regimen”, “Published regimen, acute”, “Route”). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from that section | 🟢 | The repeated-dose schedule, the acute dose, and the route — the only three implementable parameters the ER actually sources; remaining bullets are unsourced figures, pharmacokinetics or modifier discussion. |
| 10.3 | If fewer than three distinct actionable implementation aspects are mentioned in the ER, the unused sets are left empty and hidden with style="display:none", not filled with placeholder text or empty-state phrasing. |
N/A | The ER provides three or more distinct 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 that section. | 🟢 | All nine fields carry ER-derived content (lines 456–497), including the mouse basis and the oral-gavage comparison. |
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 | 🟢 | Behavior within hours, neurogenesis markers at four days, and the unknown human time course — the whole content of the ER’s “Time to effect” bullet (ER line 358). |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Depression-related behavior (the ER’s leading Speculative benefit) first, neurogenesis/synapse formation second, the human unknown last. |
| 11.3 | If fewer than three distinct time-to-effect aspects are mentioned in the ER, the unused sets are left empty and hidden with style="display:none", not filled with placeholder text or empty-state phrasing. |
N/A | Three distinct aspects exist 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 fields populated from ER line 358 (lines 508–536). |
| 11.5 | If the ER provides no information on time to effect at all, the whole Time to effect block (its subhead and all three sets) is hidden with style="display:none", not removed: its spans stay in place, empty. |
N/A | The ER does provide time-to-effect information. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | The four Speculative items match the ER’s four Speculative sub-headings (ER lines 134–148). |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans present (lines 546–561) with the ER’s grading: High, Medium and Low empty, Speculative populated. |
| 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. | 🟢 | Four semicolon-separated phrases only; “roughly doubled new-cell labeling”, “⚠️ Conflicted”, species notes and citations are all dropped. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical content remains in the Benefits card. |
| 12.5 | If a tier (high, medium, low, speculative) has no items, its span is hidden with style="display:none", not filled with “None documented in human trials to date” or similar empty-state phrasing. |
🟢 | benefits_high, benefits_medium and benefits_low carry style="display:none" with their placeholders emptied (lines 546–554), matching the ER’s “No benefit reaches High/Medium/Low”. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | The Low item and all seven Speculative items match the ER’s sub-headings (ER lines 182–216). |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans present (lines 627–642) with the ER’s grading: High and Medium empty, Low and Speculative populated. |
| 13.3 | Items are as concise as possible. No explanations, no elaborations, no effect sizes, no qualifiers, no attributions, no citations, no study details, no mechanistic explanations, etc. Just the key fact. | 🟢 | “Infection, contamination and mislabeled material” plus seven short phrases; the ER’s “Magnitude:” paragraph, “Net:” judgments and citations are dropped. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical content remains in the Risk card; the ER’s “⚠️ Conflicted” markers are not carried over. |
| 13.5 | If a tier (high, medium, low, speculative) has no items, its span is hidden with style="display:none", not filled with “None documented in human trials to date” or similar empty-state phrasing. |
🟢 | risks_high and risks_medium carry style="display:none" with emptied placeholders (lines 627–632), matching the ER’s “No risk reaches High/Medium”. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring Protocol & Defining Success section |
🟢 | Table and cadence both come from ER lines 384–395. |
| 14.2 | All measurable/quantifiable biomarkers from that section are listed, one table row per marker; the template’s # row is the pattern, repeated with # replaced by 1, 2, 3 … in the data-qrs-var names |
🟢 | All four ER biomarkers appear as four rows with marker_1_* … marker_4_* names following the template row pattern. |
| 14.3 | [marker_#name] is the marker, [marker#target] its target value or range as given in the ER, [marker#_why] its purpose in a few words; a target the ER does not give is written “Not specified in the ER” | 🟢 | Names and “Why” strings are the ER’s verbatim; targets 60–100 bpm, 70–99 mg/dL, 4.0–5.6% and “No established target — track change from the individual’s own baseline” match the ER column. |
| 14.4 | [monitoring_cadence] is populated with the monitoring cadence/frequency derived from that section. It is not left with placeholder text or empty. | 🟢 | Lines 716–720 carry the ER’s baseline-then-1-week-and-4-week rhythm/glucose schedule, weekly mood score and stop triggers, prefaced by “No cadence rests on evidence”. |
| 14.5 | If the ER names no measurable biomarker, the table is hidden with style="display:none" and the single # row is left as in the template |
N/A | The ER names four measurable biomarkers. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring Protocol & Defining Success section |
🟢 | All six items come from the ER’s “Qualitative markers worth tracking alongside the table” list (ER lines 399–404). |
| 15.2 | All subjective/qualitative markers from that section are listed, one <li> per marker; the template’s # item is the pattern, repeated with # replaced by 1, 2, 3 … |
🟢 | Six <li> items with qualitative_item_1 … qualitative_item_6 (lines 728–751), one per ER marker. |
| 15.3 | If the ER names no qualitative marker, the card’s list is hidden with style="display:none" and the single # item is left as in the template |
N/A | The ER names six qualitative markers. |
Issues 11/14/2026 13:39
Pass rate 100.00%. No issues found.