Audit: QRS - Pramiracetam for Health & Longevity
Audit conducted on 21/08/2026 19:12 using AI4L / Opus 5
Summary
| Items | Count |
|---|---|
| Total | 93 |
| Passed | 85 |
| Failed | 0 |
| N/A | 8 |
| 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 span traces to ER text: at-a-glance to Conclusion, protocol cells to Therapeutic Protocol, time cells to Practical Considerations and Expected Benefits, gates to Key Interactions & Contraindications, tiers to the ER benefit/risk headings, markers and cadence to Monitoring Protocol & Defining Success. |
| 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. | 🟢 | “Small controlled studies suggest”, “healthy adults have never been tested”, “Side effects look mild”, “Observed in animal work only”, “the concern is mechanistic” all mirror the ER’s hedging. |
| 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”). | 🟢 | “Pregnancy and breastfeeding” remains under Contraindications, not Key Interactions; speculative tiers stay speculative. |
| 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 Pramiracetam” list; Key Interactions only from the ER interaction bullets. No Benefit- or Risk-Modifying Factor content appears in 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. | 🟢 | No PMIDs, NCT IDs, expert names, or brand names appear anywhere in the QRS; the only study reference is “the head-injury trial”, which the ER uses for the same 400 mg three-times-daily fact. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | The single attribution (“drawn from the online nootropic community rather than from a regulatory dossier”, action_3_sub) restates the ER Attribution of each approach bullet. |
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. | 🟢 | Sceptical-but-neutral register of the ER Conclusion is carried through, including the conflict-of-interest and supply-quality framing. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Targets, thresholds, and cadence are given as actionable data without exhortation. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Statements are descriptive (“Divided dosing is standard in every human study”), not prescriptive. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No imperatives in any authored span; the only directive sentence is the fixed template footer disclaimer. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | Marker rows state what a value means, not what to do about it. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronoun occurs in any authored span. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms are confined to marker names and drug names where precision is required; at-a-glance is fully plain. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Gate items are single clauses; benefit and risk tiers are single semicolon-separated lines. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed across header, at-a-glance, protocol, gates, cards, and qualitative list. |
| 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 (not conventional) biomarker targets and a self-directed monitoring cadence address exactly this audience. |
| 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 nine-marker baseline panel plus repeat validated cognitive testing assumes that willingness. |
| 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. | 🟢 | No simplified “ask your doctor” framing; the sheet assumes lab access and self-tracking. |
| 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 foregrounds the two points that matter for a healthy self-experimenter: untested in healthy adults, and supply quality as the dominant hazard. |
| 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 in the QRS. |
| 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. | 🟢 | “oral dose”, “plasma concentration”, “sleep-onset difficulty”, “hypersensitivity”, “antiplatelet”. The plain-language wording in at-a-glance is required by item 7.4 and is ER-verbatim. |
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” | 🟢 | Verified at lines 446, 492, 543, 601, 627, 786 (headings), 565 and 579 (gates), 606/611/617 and 549/554 (tier labels), 631–633 (table headers). |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | 67 variable spans present, with every indexed family complete and gap-free: action_1–3 and time_1–3 (label/value/sub), benefits and risks × 4 tiers, stop_items, caution_items, marker_1–9 (name/target/why), monitoring_cadence, qualitative_item_1–6, plus the four header/title spans. No duplicates. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | The non-variable template elements are untouched: <span website="evidence_review"> (line 423), <span website="audit"> (426), <span website="full_review"> (440), the footer disclaimer (830–833), and the full inline stylesheet and override link. |
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 drawn on by the QRS is empty; absent benefit/risk tiers are handled under items 12.5 and 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. | 🟢 | action_1_label “Approved European regimen”, action_2_label “Best time of day”, action_3_label “Competing approach — acute, task-linked dosing” are verbatim ER bold labels (ER lines 311, 319, 315). |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Marker names reproduce the ER biomarker column exactly (“Prothrombin time / INR”, “TSH with free T4”, “Delayed-recall score on a validated memory test”); tier labels are the fixed template set. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji characters in the file; tiering is conveyed by <strong> labels and the .benefits / .risks CSS palettes. |
| 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 against its ER source rather than transcribed: six benefit subsections with magnitude paragraphs reduce to two tier lines, ten interaction bullets lose their rationale and mitigation clauses, and the nine-row biomarker table drops the ER’s Context/Notes column. |
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 spanning lines 2–14, immediately after <!doctype html> at 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 --- at line 3, closing --- at line 13; the preamble text “QRS — Metadata (invisible, parsed by audit tooling)” precedes the opening delimiter. |
| 5.3 | The metadata is not visible in any rendered view of the QRS and is not surfaced by any other element on the sheet. | 🟢 | Enclosed in an HTML comment; none of its values are echoed except the two that the header legitimately requires (date and model). |
| 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; all other values are bare and untrimmed of nothing. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Line 4: er_filename: pramiracetam_2026-0821-1739_Opus_ER.md. |
| 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-0821-1847. |
| 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 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, no qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9: qrs_filename: pramiracetam_2026-0821-1739_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 plus the three provenance keys (duration, git_user, git_issue); consistent and clean. |
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: Pramiracetam 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 417: Pramiracetam for Health & Longevity. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: 08/21/2026, correctly derived from qrs_creation_date: 2026-0821-1847. |
| 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. | 🟢 | The header carries only the title and the fixed subline; the ER’s “Also known as” list (CI-879, Amacetam, Pramistar, …) is correctly absent. |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Compresses all four Conclusion paragraphs — mechanism, thin human evidence, sponsor conflict, mild side effects, supply hazard — into one paragraph. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | Exactly 60 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Maps to ER lines 441 (fat-soluble relative, choline uptake), 443 (small controlled studies, delayed recall, already-impaired memory, healthy adults untested, two owning companies), and 445 (mild side effects, supply the larger hazard). |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms. “the brain’s main memory chemical” replaces acetylcholine and “raw material” replaces precursor, both taken from the ER’s own plain-language Conclusion. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial name, year, n, or p-value; “small controlled studies” is generic. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No numbers of any kind appear in the paragraph. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All seven items come from the “Populations who should avoid Pramiracetam” list at ER lines 279–287. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All seven ER avoid-populations are present, none added: renal, haemorrhagic stroke/ulcer/bleeding disorder, Huntington’s, hypersensitivity, hepatic, pregnancy/breastfeeding, age under 16. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Seven discrete <li> elements at lines 568–574 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. | 🟢 | Every ER trailing clause is stripped: “a class contraindication carried over from piracetam labelling”, “on absence of safety data”, “per European product information”, and the glosses “(estimated kidney filtration rate)” and “(the most advanced grade of liver dysfunction)”. No dash-trailing content 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). | 🟢 | The renal thresholds (CrCl <20 mL/min, eGFR <30 mL/min/1.73 m²), the “within 6 months” stroke window, and the “Child-Pugh Class C” severity class are all retained, normalised into parentheses. |
| 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-populations list contains no ranking notation; thresholds are written out in words (“below 20 mL/min”). |
| 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 seven such populations, and the section is correctly 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 come from the interaction bullets at ER lines 259–277. |
| 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 represented one-for-one, and none duplicates an entry in the Contraindications gate. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Ten discrete <li> elements at lines 582–591 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. | 🟢 | Every “Caution/Monitor” verdict, mechanism sentence, and “Mitigation:” clause from the ER bullets is stripped; each item is reduced to the drug-class name plus its example list. |
| 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 drug-example parenthetical is retained; a small number are trimmed to fit the budget (acenocoumarol, desiccated thyroid extract, dimenhydrinate, omberacetam, choline bitartrate), with at least three exemplars kept in each list and none dropped entirely. |
| 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 parentheticals are already plain comma-separated drug lists with no ranking notation. |
| 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 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 lines 311–323. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Dose (the only regimen with a regulatory dossier), timing (the driver of the most reported adverse effect), and the competing acute pattern — the three bullets that actually change what a user does. |
| 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 well over 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 spans populated: labels are ER bold labels, values are “1,200 mg” / “Morning and early afternoon” / “400–600 mg, task-linked”, subs carry the divided-dosing, peak-plasma, and community-attribution detail. |
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 | 🟢 | Delayed recall at 2–4 weeks (ER line 368), post-concussion symptoms at 30 days (ER line 153), and acute memory tasks at 1–2 hours (ER line 368) — the only three time horizons the ER states. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered by benefit weight: delayed verbal recall (the ER’s first-listed Low benefit and the compound’s central claim), then post-concussion recovery (a later Low benefit), then the acute window, which rests on animal data only and carries no human benefit tier. |
| 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 sets are used. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | All nine spans populated, each sub naming the evidence basis (10-day dosing before testing, active comparator rather than placebo, animal work only). |
| 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, so the section is correctly retained. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | All five entries are the ER’s Expected Benefits subsection headings from lines 139–169. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans present at lines 545–558. |
| 12.3 | Items are as concise as possible. No explanations, no elaborations, no effect sizes, no qualifiers, no attributions, no citations, no study details, no mechanistic explanations, etc. Just the key fact. | 🟢 | Each tier is a semicolon-separated list of bare benefit names; the ER’s Magnitude paragraphs, sample sizes, PMIDs, and the “⚠️ Conflicted” marker on hypoxic protection are all dropped. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses occur in either benefits span. |
| 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 or Medium benefit tier; benefits_high (line 545) and benefits_medium (line 546) are empty and carry style="display: none". |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | All eight entries are the ER’s Potential Risks & Side Effects subsection headings from lines 195–237. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans present at lines 603–621. |
| 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. | 🟢 | The ER’s mislabelling figures (75%, four-fold), the “>1,200 mg daily” threshold, the thromboxane mechanism, and the 18-month exposure limit are all omitted, leaving bare risk names. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses occur in any risks span. |
| 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 has no High risk tier; risks_high (line 603) is empty and carries style="display: none". |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Rows and cadence come from the ER Monitoring Protocol & Defining Success section, lines 396–410. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All nine ER table rows appear, in ER order: eGFR, cystatin C, serum creatinine, platelet count, PT/INR, ALT, TSH with free T4, homocysteine, delayed-recall score — with targets and “Why” text matching the ER. |
| 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. |
🟢 | Lines 776–779 reproduce the ER’s full schedule: baseline panel and cognitive test, retest at 4 weeks, renal/platelet/clotting recheck at 8–12 weeks, full panel every 6–12 months, or sooner on bruising, persistent headache, or sleep disruption. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Taken from the “Qualitative markers” list at ER lines 414–419. |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All six ER qualitative markers appear in ER order, verbatim: retrieval ease, sustained attention, sleep-onset latency, headache pattern, bruising/bleeding, and externally observed irritability. |
Issues 21/08/2026 19:12
Pass rate 100.00%. No issues found.
Issues 21/08/2026 19:04
- 1.3 — At-a-glance softens sponsor conflict: [at_a_glance] (line 437) states “most evidence came from the two companies that owned it”, weakening the ER Conclusion’s “Almost all of that evidence was produced or funded by the two companies that owned the compound” (ER line 443).
- 4.2 / 4.3 — Antihistamine interaction label reworded: The caution item at line 588 reads “Sedating anticholinergic antihistamines (diphenhydramine, doxylamine)”, paraphrasing the ER’s bold label “Sedating antihistamines with anticholinergic action” (ER line 269) instead of carrying it over verbatim.
Fixes 21/08/2026 19:04
- 1.3 — At-a-glance sponsor conflict restored: Changed “most evidence came from the two companies that owned it” to “almost all evidence came from the two companies that owned it”, matching the ER Conclusion; “point to” was tightened to “suggest” so the summary stays at 60 words.
- 4.2 / 4.3 — Antihistamine interaction label verbatim: Replaced the paraphrased caution item “Sedating anticholinergic antihistamines” with the ER’s bold label “Sedating antihistamines with anticholinergic action”, keeping the trimmed example list.
Issues 21/08/2026 18:57
- 1.1 — Unsupported human-negative claim: [time_3_sub] (line 533) states “no human study has measured an acute single-dose effect”, an absolute claim the ER never makes; the ER only reports the 1–2 hour finding “in animal work” and attributes the acute pattern to that animal finding (ER lines 315, 368).
- 4.2 — Protocol label truncated: [action_3_label] (line 478) reads “Competing approach” instead of the ER’s verbatim bold label “Competing approach — acute, task-linked dosing” (ER line 315).
Fixes 21/08/2026 18:57
- 1.1 — Unsupported human-negative claim: Rewrote [time_3_sub] from “Observed in animal work only; no human study has measured an acute single-dose effect.” to “Observed in animal work only; the acute, task-linked pattern rests on that animal finding.”, which is literally supported by ER line 315.
- 4.2 — Protocol label truncated: Restored [action_3_label] to the ER’s verbatim bold label, changing “Competing approach” to “Competing approach — acute, task-linked dosing”.
Issues 21/08/2026 18:52
- 4.2 / 4.3 — Invented protocol cell label:
action_1_label(line 450) reads “Daily dose”, a label with no counterpart in the ER; the cell’s content derives from the ER bullet “Approved European regimen:” (ER line 311), whose bold label must be used verbatim.
Fixes 21/08/2026 18:52
- 4.2 / 4.3 — Invented protocol cell label: Replaced
action_1_label“Daily dose” with the ER’s verbatim bold label “Approved European regimen” (ER line 311), and trimmed the now-redundant phrase “the approved European regimen” fromaction_1_sub.