Audit: QRS - Bromantane for Health & Longevity

Audit conducted on 15/08/2026 02:49 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 93
Passed 86
Failed 0
N/A 7
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 numeric values (50–100 mg, 28 days, 2.75/4.0 h, day 3, 1 month, 2 months, all biomarker ranges, BP >160/100, ALT >3× ULN, Hb <11 g/dL, WBC <3.0 × 10⁹/L) match the ER verbatim.
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. 🟢 “appears to raise the brain’s own dopamine production” carried over verbatim from the ER Conclusion; “unknown consequences of sustained dopamine-synthesis upregulation” retains the ER’s hedge.
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/conception/breastfeeding remains an absolute contraindication; “Blood and liver changes at supratherapeutic doses” retains the dose qualifier rather than overstating.
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 and interactions come only from the ER Key Interactions & Contraindications section; benefit/risk tiers map one-to-one onto the ER tiers.
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 PMIDs, citations, expert names, NCT identifiers or brand names.
1.6 The QRS does not introduce new attributions. 🟢 No attributions of any kind are present.

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. 🟢 Mirrors the ER’s sceptical-but-fair register, including the provenance caveat in At-A-Glance.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Benefits, protocol and monitoring are presented as actionable data; limitations are stated without alarm.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Declarative throughout (“Single morning dose”, “Peak blood levels …”).
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No imperatives in any authored variable region.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Protocol cells state the registered regimen rather than instructing.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns in any authored content.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Retained technical terms (cytopenias, Child-Pugh Class B or C) are decision-gate thresholds required by 8.5 and are accompanied by numeric definitions.
2.8 Information is presented in a concise and very compact manner 🟢 Every item is a single clause; no elaborations.
2.9 It DOES NOT address the reader directly 🟢 Confirmed across header, At-A-Glance, protocol, gates, cards and table.
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. 🟢 Monitoring cadence, certificate-of-analysis-grade sourcing concerns and anti-doping gating all assume a proactive user.
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. 🟢 Twice-weekly BP tracking and end-of-course blood work are presented without hedging on effort.
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 simplification toward casual use; the 28-day cap and cycling logic are retained.
2.13 Framing, takeaways, and risk/benefit weighting throughout the document reflect this audience, including where an intervention’s signal for the average person differs from its signal for this audience. 🟢 The anti-doping consequence is elevated to the High risk tier and to At-A-Glance, which is the audience-specific decision driver.
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. 🟢 “Longevity” used in the title and header; “anti-aging” does not appear.
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. 🟢 “By mouth”, “supratherapeutic”, “thermoregulatory”, “cytopenias” — all taken from the ER’s own register.

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 verified verbatim (lines 440, 477, 519, 537, 552, 573, 592, 596–598, 678).
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 Complete and internally consistent set of 58 spans: page_title, header_topic/subline_date/subline_model, at_a_glance, action_1–3 (label/value/sub), time_1–3 (label/value/sub), benefits_×4, stop_items, caution_items, risks_×4, marker_1–6 (name/target/why), monitoring_cadence, qualitative_item_1–6.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Template-owned regions (footer disclaimer, website= spans, CSS block, subline scaffolding) 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 mapped by the QRS is empty.
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 Russian regimen”, “Best time of day”, “Single versus split dosing”, “Time to effect”, “Effect outlasts the course” all match the ER bold labels verbatim; all six marker names match the ER biomarker table verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 No invented labels; “Durability of effect” preserves the ER heading’s leading words unchanged within the micro-label cell budget.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji present; the ER’s ⚠️ 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. 🟢 Every section is inside the template’s per-section budget: 3 protocol cells, 3 time cells, 3 benefit lines, 4 risk lines, 6 monitoring rows, 6 qualitative lines, gates at 8/9 single-clause items.

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, immediately after 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 “—” line 3, closing “—” line 13; the “QRS — Metadata” text precedes it.
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; no duplicate rendering elsewhere.
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, correctly so because it contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: bromantane_2026-0815-0002_Opus_ER.md (line 4).
5.6 Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” 🟢 qrs_prompt_version: 26.7.02 matches 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) 🟢 qrs_creation_date: 2026-0815-0242.
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢 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) 🟢 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]” 🟢 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]” 🟢 qrs_filename: bromantane_2026-0815-0002_Opus_QRS.html matches 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 eight keys; no stray whitespace or quoting.

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., &amp; for &) 🟢 “Bromantane for Health & Longevity - Quick Reference Sheet” (line 22).
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 “Bromantane for Health & Longevity” (line 417).
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 2026-0815-0242 → “08/15/2026” (line 421).
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 “Opus 5” (line 425).
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 ER’s “Also known as” line (Ladasten, Bromantan, …) is correctly absent; header contains only title and template subline.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Distils the Conclusion’s mechanism claim, benefit signal, provenance limitation and the anti-doping exclusion.
7.2 [at_a_glance] is no longer than 60 words 🟢 57 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each clause maps to ER Conclusion lines 436–440, with the two-week trace window corroborated at ER line 199.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms; “persistent exhaustion” used in place of asthenia/neurasthenia.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial names, years or sample sizes.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No percentages or statistics.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All eight items trace to ER lines 265 and 285–291.
8.2 [stop_items] represent the Contraindications from the ER 🟢 The ER’s seven “Populations who should avoid Bromantane” entries plus the MAOI bullet the ER labels an “absolute contraindication”.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Eight <li> elements inside the span (lines 540–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 trailing clause “— non-monotonic animal litter-size effects and zero human data” was stripped from the pregnancy item; no dash-trailing explanation remains anywhere.
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). 🟢 Child-Pugh Class B or C, ALT >3× ULN, BP >160/100 mmHg, Hb <11 g/dL and WBC <3.0 × 10⁹/L all preserved.
8.6 When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol. 🟢 The ER uses no ranking notation; thresholds are rendered as plain prose (“above three times the upper reference limit”).
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 the ER does identify such populations — constraint satisfied.
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 nine items trace to ER lines 263–281.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Nine of the ER’s ten interaction bullets; the MAOI bullet is correctly excluded because it appears under Contraindications.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Nine <li> elements inside the span (lines 555–563).
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. 🟢 The ER’s “— caution / — monitor” suffixes and all Consequence/Mitigation prose were stripped.
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). 🟢 Named exemplars retained for all seven items where the ER supplies them (levodopa/pramipexole/bupropion/selegiline/amantadine, haloperidol/risperidone/metoclopramide, warfarin/ciclosporin/hormonal contraceptives, caffeine/pseudoephedrine/phenylephrine, diphenhydramine/doxylamine, L-Tyrosine/L-Phenylalanine/Mucuna pruriens, Rhodiola/Panax ginseng/high-dose ginkgo).
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. 🟢 The ER uses no ranking notation; all parentheticals are plain comma-separated lists.
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 the ER does identify such interactions — constraint satisfied.
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 trace to the ER Therapeutic Protocol bullets at lines 315, 323 and 327.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Dose and course length, timing of day, and single-versus-split dosing are the three execution-determining decisions in the ER protocol.
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 more than three actionable aspects; no set is unused.
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 substantive ER-derived content; no placeholders.

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 (day 3), persistence after stopping (1 month), and absence of tolerance (2 months) are the ER’s three temporal findings.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Sets 1 and 2 attach to the Medium-tier antiasthenic benefit; set 3 attaches to the Low-tier durability benefit.
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 Three distinct aspects are present; no set is unused.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 Values and subs match ER lines 368, 348 and 163.
11.5 If the ER does not provide any information on time to effect, the section is removed completely from the Protocol Panel N/A The ER provides explicit time-to-effect data (ER line 368).

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All seven benefit items match the ER’s #### benefit headings at lines 133–173.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present (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. 🟢 Bare ER headings only; no Magnitude figures (76.0%/90.8%, 1.3–1.6×) carried over.
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.
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; benefits_high is empty with style="display: none" (line 521).

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All nine risk items match the ER’s #### risk headings at lines 197–245.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present and populated (lines 575–586).
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 Magnitude figures (3% adverse events, 0.8% discontinuation, −34.9%/+45.1%/−44.2%, 14-day window) are all omitted.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses appear in any 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 tiers carry items in the ER; no sub-section is empty.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Rows match the ER Monitoring Protocol & Defining Success biomarker table (ER lines 396–403).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All six ER biomarkers present — hemoglobin, white blood cell count, ALT, AST, prolactin, resting blood pressure — with targets and rationale verbatim.
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. 🟢 Baseline, end-of-course, 6–12 month repeat interval, twice-weekly BP/HR and the one-week post-stop check all carried over from ER line 394.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Matches the ER’s weekly-tracking list at lines 407–412.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All six items present verbatim, none dropped.

Issues 15/08/2026 02:49

Pass rate 100.00%. No issues found.