Audit: QRS - Clubmoss for Health & Longevity
Audit conducted on 17/08/2026 15:12 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. | 🟢 | Spot-checked every populated span against the ER: protocol cells vs Therapeutic Protocol, gates vs Key Interactions & Contraindications, tiers vs Expected Benefits / Potential Risks & Side Effects, table vs the Monitoring Protocol & Defining Success biomarker table, at-a-glance vs Conclusion. No unsupported claim found. |
| 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 carried over, e.g. time_3_sub keeps “nothing in the human record suggests a residual benefit” (ER line 354) and action_1_sub keeps “Neither approach is the default” (ER line 323). |
| 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”). | 🟢 | No strengthening or softening. Pregnancy/breastfeeding stays an absolute contraindication (ER line 288); prescription cholinesterase inhibitors stay in the STOP gate, not the caution gate (ER line 268). |
| 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. | 🟢 | No cross-category relabelling. All nine stop_items and all seven caution_items trace to Key Interactions & Contraindications; nothing from Benefit-Modifying Factors or Risk-Modifying Factors was promoted into a gate. |
| 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 contains no PubMed IDs, study citations, author names, NCT identifiers or brand names. Drug names in the gates (donepezil, verapamil, etc.) are generic names taken verbatim from the ER bullets. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions of any kind appear in the QRS. |
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, evidence-weighted register, including its explicit conflict framing (medium-tier benefit, Western trial missed its endpoint). |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Expert and data-driven (thresholds, ranges, target values) while remaining accessible; the at-a-glance paragraph is plain-language. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Presents thresholds and observations; no imperatives directed at a reader. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | Uses agentless constructions (“are corrected first”, “are treated first”, “is checked”). No prescriptive clinical instruction. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | Information is stated, not recommended or advised. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns anywhere in the file; qualitative_item_5 refers to “the user”, not “you”. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Plain language throughout; technical terms appear only where they are the ER’s own decision-gate vocabulary (GOLD stage, atrioventricular block, eGFR). |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Every cell is a compressed fragment; gate items and tier items are single clauses. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed: no direct address to the reader. |
| 2.10 | The target audience is health- and longevity-oriented adults who are risk-aware, proactive, and actively seeking to optimize health or apply the intervention under review. | 🟢 | Content assumes a proactive user running baseline labs, cycling, and tracking a cognitive test. |
| 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. | 🟢 | Protocol and monitoring assume willingness to run an eight-marker blood panel, repeat cognitive testing and observe planned wash-out weeks. |
| 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. | 🟢 | Not pitched at the general population; no simplified “ask your doctor” framing replaces the data. |
| 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. | 🟢 | Captures the audience-specific split: the intermittent nootropic regimen (this audience’s use case) is presented alongside the Chinese clinical regimen, with “Neither approach is the default”. |
| 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; framing is longevity/cognition. |
| 2.15 | The document’s own voice uses formal clinical and scientific terminology, not colloquial or consumer-grade language (e.g., “oral medication” not “pill(s)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt. | 🟢 | Formal register in the QRS’s own voice. The at-a-glance wording “stomach upset”, “slower pulse”, “broken sleep” is the ER’s own Conclusion phrasing (ER line 448), which item 7.4 additionally requires to stay plain-language. |
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 labels verified in source: “Protocol” (line 440), “Time to effect” (477), “Benefits” (519), “Risk & Side Effects” (572), “Monitoring” (591), “Qualitative Assessment” (699), “Contraindications” (537), “Key Interactions” (553), tier labels High/Medium/Low/Speculative, and the Marker/Target/Why headers (595-597). |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | Programmatic comparison against [qrs_template]: all 34 distinct template variable names are present; the only additions are the repeatable marker_#* and qualitative_item# rows the template defines as repeatable. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | A structural diff against the template (variable regions masked) shows no change outside the frontmatter, the title, and the variable spans themselves. The <span website="..."> hooks 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 ER section feeding a QRS region is empty; the Conclusion, Therapeutic Protocol, Key Interactions & Contraindications, Expected Benefits, Potential Risks & Side Effects and Monitoring Protocol & Defining Success sections all carry content. The empty High benefit tier is governed by item 12.5, not by 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. | 🟢 | Every cell whose ER source is a discrete “Label: content” bullet uses that bold label verbatim: “Nootropic intermittent dosing”, “Best time of day”, “Baseline biomarkers” (ER lines 321, 325, 339). Monitoring row labels are the ER biomarker-table names verbatim. The Time-to-Effect cells subdivide a single ER bullet (“Time to effect:”, ER line 374), whose label is already the fixed section subhead, so no 1:1 bullet-to-cell label mapping exists there; section 11 governs those cells. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | No label is paraphrased or abbreviated relative to an available ER bullet label; the Protocol and Monitoring labels are exact. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | A Unicode scan of the file returns no emoji; the ER’s tier emoji (🟩/🟥/🟨) and the ⚠️ Conflicted markers 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. | 🟢 | Content is condensed rather than extended: gate items are stripped to the key fact, tier items to a single clause, and the multi-sentence ER bullets are cut to two or three short sentences per protocol cell. No overflow section or continuation content was added. |
5. Metadata
| # | Description | Result | Comments |
|---|---|---|---|
| 5.1 | The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content. | 🟢 | The metadata comment opens at line 2, immediately after <!doctype html> on line 1, and precedes the template comment on line 16 and the <html> element on line 17. |
| 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 preceding text “QRS — Metadata (invisible, parsed by audit tooling)” sits outside the YAML block. |
| 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 inside an HTML comment and no element on the sheet repeats any of its values apart from the title/header, which are separate variables. |
| 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 are trimmed and unquoted except duration: "00:03", which contains a colon and therefore requires quoting. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Line 4: er_filename: clubmoss_2026-0825-1314_Opus_ER.md, which is the ER audited against. |
| 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 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-0817-1445, in YYYY-MMDD-HHMM form. |
| 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 additional qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9: qrs_filename: clubmoss_2026-0825-1314_Opus_QRS.html, identical to 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: no leading/trailing whitespace and no unnecessary quoting on any key. |
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: <title>Clubmoss & Longevity... — reads “Clubmoss for Health & Longevity - Quick Reference Sheet”, matching the ER canonical_topic with the ampersand entity-encoded. |
| 6.2 | [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &) |
🟢 | Line 417: Clubmoss for Health & Longevity, the ER canonical_topic with & encoding. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: 08/17/2026, the MM/DD/YYYY form of qrs_creation_date 2026-0817. |
| 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 holds only the title and the standard subline; no badge, version stamp, AKA line (the ER’s seven alternate names are not carried over), audit date or variant marker. |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Condenses the ER Conclusion (lines 444-448) into three clauses: what the substance is, what the pooled evidence shows and where it failed, and what sits against it. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | Counted programmatically: 57 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Compound-not-plant and the acetylcholine mechanism from ER line 444; pooled benefit in the impaired plus the failed Western trial from ER line 446; the side-effect list and label mismatch from ER line 448. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms and no technical classifications; “acetylcholinesterase inhibitor” is rendered as “slows removal of the brain chemical carrying memory and attention signals”, and “purified compound” replaces the alkaloid nomenclature. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial name, year, sample size or p-value; “the one carefully run Western study” is the ER’s own unnamed description. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No effect size, weighted mean difference, hazard ratio, confidence interval or percentage appears. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All nine items trace to the ER Key Interactions & Contraindications section — eight to the “Populations who should avoid Clubmoss” list (ER lines 288-295) and one each to the absolute-contraindication bullets at ER lines 268, 274 and 284. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All eight ER avoid-population bullets are represented, plus the two bullets flagged “Absolute contraindication” and the contraindicated occupational-pesticide scenario. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Lines 540-548: nine discrete <li> elements inside the stop_items span. |
| 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. | 🟢 | Trailing rationale stripped throughout: the pregnancy bullet’s “— no reproductive safety data exist…” and the anesthesia bullet’s “cholinesterase inhibition prolongs paralysis” are gone. No item carries an em-dash, en-dash or hyphen-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). | 🟢 | Thresholds and severity classes preserved: “below 50 beats per minute”, “within the past 90 days”, “GOLD stage III or higher”, “below 30 mL/min/1.73 m²”, “within one week of planned general anesthesia”, “during application seasons”. Only the ER’s glossary parentheticals (the GOLD and eGFR definitions) were dropped. |
| 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 Key Interactions & Contraindications section uses no ranking notation such as “>” inside parentheses; its parentheticals are drug lists and glossary definitions. |
| 8.7 | The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no population, condition, or scenario for which the intervention should be avoided, deferred, or used only under specialist supervision. |
🟢 | The section is populated, and correctly so — the ER names an explicit avoid-population list. |
| 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, so no explanatory HTML comment is required. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All seven items trace to the caution bullets of the ER Key Interactions & Contraindications section (ER lines 270-284). |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | The seven ER bullets marked “Caution” are all present, and the two “Absolute contraindication” bullets (prescription cholinesterase inhibitors, succinylcholine/neuromuscular blockers) are correctly excluded from this gate and placed in Contraindications instead. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Lines 556-562: seven discrete <li> elements inside the caution_items span. |
| 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. | 🟢 | All mechanistic rationale and mitigation clauses stripped, e.g. “mutual antagonism… Mitigation: the two are separated by treatment goal” reduced to the drug class alone. No dash-trailing clauses remain. |
| 9.5 | Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely). | 🟢 | Every ER example-drug list is preserved in full: oxybutynin/tolterodine/scopolamine/diphenhydramine/tricyclics, verapamil/diltiazem/digoxin, ibuprofen/naproxen, diphenhydramine/doxylamine, alpha-glycerophosphocholine/citicoline/choline bitartrate, and the three botanicals with their ER italics intact. |
| 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 | No ranking notation inside parentheses appears in the ER’s interaction bullets. |
| 9.7 | The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no interaction, additive effect, or exposure that changes how the intervention is used. |
🟢 | The section is populated, and correctly so — the ER names nine interaction bullets. |
| 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, so no explanatory HTML comment is required. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Protocol section |
🟢 | All three action cells derive from the ER Therapeutic Protocol section (ER lines 319-341). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Covers dose regimen, timing, and pre-start correction of reversible causes — the three decisions that must be made before and at first use. |
| 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 supplies well over three actionable aspects, and all three cell 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 ER-derived content; no placeholder or empty-state text remains. |
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 of measurable cognitive change, onset of acute effects, and loss of effect after stopping — the three time horizons the ER quantifies (ER lines 327, 354, 374). |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered by magnitude of the related benefit: the cognitive-score gain (the primary claimed benefit) first, the acute cholinergic/nootropic effect second, and the fade after discontinuation last. |
| 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 distinct time-to-effect aspects, and all three cell 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 ER-derived content (4-16 weeks, 1-2 hours, days after stopping) with supporting detail from the ER. |
| 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 (ER lines 327, 354, 374), so the section is correctly retained in the Protocol panel. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | The three populated tiers mirror the ER Expected Benefits headings at Medium, Low and Speculative. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four variables are present at lines 521-530. |
| 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 bare noun phrase; the ER’s mechanistic and trial detail (weighted mean differences, the Chinese risk-of-bias caveat, the ex vivo soman study) is absent. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses remain; the ER’s citation parentheticals and effect-size parentheticals were 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. | 🟢 | The ER has no High-tier benefit, and line 521 sets <span data-qrs-var="benefits_high" style="display: none"></span> with no empty-state text. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | All four tiers mirror the ER Potential Risks & Side Effects headings, including both Low-tier entries and all three Speculative entries. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four variables are present at lines 574-585. |
| 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 bare descriptor; the ER’s incidence figures, hazard ratios and the Department of Defense product-analysis detail are absent. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical content remains in any risk 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. | N/A | All four risk tiers carry at least one ER item, so no span needs to be hidden. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | The table and cadence derive from the ER Monitoring Protocol & Defining Success section (ER lines 402-415). |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All eight ER biomarkers are present with their exact optimal ranges and “Why Measure It?” text: resting heart rate, vitamin B12, homocysteine, TSH, HbA1c, ALT, eGFR and MoCA score. |
| 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 693 carries the full cadence — baseline, heart rate at one and four weeks, cognitive test at four and twelve weeks, blood panel every 6-12 months — condensed from ER line 404. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | The six items derive from the qualitative-marker list in the ER Monitoring Protocol & Defining Success section (ER lines 419-424). |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All six ER qualitative markers are carried over, in ER order, with only the trailing full stops removed. |
Issues 17/08/2026 15:12
Pass rate 100.00%. No issues found.
Issues 17/08/2026 15:06
- 4.2 / 4.3 — Protocol cell labels invented: The three Protocol cell labels — “Dose” (line 444), “Timing” (line 455) and “Before starting” (line 466) — are invented rather than taken verbatim from the ER’s bold bullet labels “Nootropic intermittent dosing”, “Best time of day” and “Baseline biomarkers” in
Therapeutic Protocol; line 450 additionally re-orders the ER label into “Intermittent nootropic dosing”.
Fixes 17/08/2026 15:06
- 4.2 / 4.3 — Protocol cell labels made verbatim: Replaced the invented Protocol cell labels with the ER’s own bold bullet labels from
Therapeutic Protocol— “Dose” to “Nootropic intermittent dosing”, “Timing” to “Best time of day”, and “Before starting” to “Baseline biomarkers”. - 4.3 — ER label no longer paraphrased: Rewrote the opening of [action_1_sub] from “Intermittent nootropic dosing, only on days requiring sustained focus.” to “Taken only on days requiring sustained focus.”, removing the re-ordered copy of the ER label.
Issues 17/08/2026 14:55
- 1.3 — Hedge flattened to absolute: [time_3_sub] (QRS line 511) states “The gain fades within days of stopping, with no residual benefit”, strengthening the ER’s evidence-scoped wording “Nothing in the human record suggests a residual benefit persists after discontinuation” (ER line 354).
Fixes 17/08/2026 14:55
- 1.3 — Hedge restored in time_3_sub: Changed “The gain fades within days of stopping, with no residual benefit.” to “The gain fades within days of stopping; nothing in the human record suggests a residual benefit.” to match the ER’s evidence-scoped wording.
Issues 17/08/2026 14:52
- 2.5 — Imperative in protocol value: [action_3_value] (line 469) reads “Correct reversible causes”, an instruction to the reader rather than presented information; the ER states the same fact passively (“Low vitamin B12, elevated homocysteine and untreated thyroid dysfunction are corrected before starting”, ER line 339).
Fixes 17/08/2026 14:52
- 2.5 — Imperative in protocol value: Changed [action_3_value] from “Correct reversible causes” to “Reversible causes corrected”, matching the ER’s passive framing and removing the instruction to the reader.