Audit: QRS - Modafinil for Health & Longevity

Audit conducted on 10/25/2026 01:19 using AI4L / Opus 5.5

Iterations

Summary

Items	Count
Total	94
Passed	84
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.	🟢	Lede, Protocol, Time to effect, Benefits, Risks, gates, markers, cadence and qualitative items all trace to ER text (e.g., Therapeutic Protocol lines 385, 387, 390; Practical Considerations line 421; Monitoring lines 437–458). ALT row is supported by ER line 445 (“pair with ALP and ALT (alanine aminotransferase, a liver-injury enzyme)”).
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.	🟢	“(theoretical)” kept on every theoretical interaction; “combined use has not been studied” (Alcohol); “could shift” (Warfarin); “may rise” (CYP2D6 item).
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”).	🟢	Lede, gates, Protocol, Time to effect and Monitoring match ER strength; tiers match ER tiers.
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.	🟢	Gates draw only from Key Interactions & Contraindications; Benefits/Risks only from their ER sections.
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.	🟢	None 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.	🟢
2.2	The tone of the QRS is expert, accessible, objective, and data-driven	🟢
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢
2.4	The QRS avoids language that implies medical or clinical advice	🟢
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢
2.6	The QRS never addresses the reader directly — it presents evidence, not guidance	🟢	No second-person address.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms are ER labels or contraindication qualifiers carried verbatim (e.g., CYP3A4 substrates, left ventricular hypertrophy).
2.8	Information is presented in a concise and very compact manner	🟢
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.	🟢
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.	🟢
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.	🟢
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.	🟢	Lede notes lost sleep “matters most for longevity strategies resting on sleep” and the small effect in rested adults.
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.	🟢
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.	🟢

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”	🟢
3.2	Every element carrying a data-qrs-var attribute in [qrs_template] is present in the QRS with the same name	🟢	All 38 template names present; # patterns expanded to marker_1–8 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	🟢	Diff against template shows only variable content, the style="display:none" on the unused time_3 cell (required by 11.3), the expanded # rows, and the workflow metadata fields (duration, git_user, git_issue).

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.	🟢
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 and interaction labels match ER bold labels (example lists trimmed, glosses dropped).
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢
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 clauses, glosses, untrimmed long example lists or repetitions found.

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.	🟢
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.	🟢
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.	🟢
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:02" is quoted (contains a colon).
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢
5.6	Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]”	🟢	26.10.24
5.7	Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430)	🟢	2026-1025-0054
5.8	The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]”	🟢
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.10	The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]”	🟢
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
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢

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 &)	🟢
6.2	[header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &)	🟢
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	10/25/2026
6.4	[header_subline_model] is set to [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.	🟢

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	🟢	“Modafinil, a prescription medication that promotes wakefulness, treats disorders of excessive daytime sleepiness and is also used for clearer focus.”
7.2	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢
7.3	[at_a_glance] is no longer than 70 words	🟢	69 words.
7.4	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Motivation lines 37/39; Conclusion lines 474/476.
7.5	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢
7.6	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢
7.7	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢
8.2	[stop_items] represent the Contraindications from the ER	🟢	All 7 “Populations who should avoid” items (ER lines 357–363) present.
8.3	Individual [stop_items] are formatted as <li></li>	🟢
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.	🟢	Rationales (“owing to serious rash risk”, “given postmarketing psychiatric reactions…”) stripped.
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).	🟢	“(contraindicated)”, “under 17 years”, “Uncontrolled”, “Active” 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.	N/A	ER uses no ranking notation.
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.	🟢	Not empty; ER names populations.
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	Section is not empty.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER Key Interactions & Contraindications section	🟢
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All 17 ER interactions (8 prescription, 3 OTC, 3 supplements, 3 other) present.
9.3	Individual [caution_items] are formatted as <li></li>	🟢
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.	🟢
9.5	Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely).	🟢	Example lists trimmed but kept; contraceptive time window and “(theoretical)” preserved.
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	ER uses 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.	🟢	Not empty; ER names interactions.
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	Section is not empty.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER Therapeutic Protocol section	🟢
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from that section	🟢	Label regimen, cognitive-use doses, best time of day.
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	ER has more than three aspects.
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from that section.	🟢

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	🟢	Alertness (within hours) and cognitive performance (single dose) are the ER’s time-to-effect aspects.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢
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.	🟢	time_3 cell empty and hidden.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢
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	ER provides time-to-effect information (line 421).

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢
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.	🟢
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢
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.	N/A	All four tiers have items.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢
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.	🟢
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢
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.	N/A	All four tiers have items.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring Protocol & Defining Success section	🟢
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 7 ER table markers plus ALT (named in the GGT row notes).
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”	🟢
14.4	[monitoring_cadence] is populated with the monitoring cadence/frequency derived from that section. It is not left with placeholder text or empty.	🟢
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	ER names biomarkers.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring Protocol & Defining Success section	🟢
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 …	🟢	All 6 ER qualitative markers present.
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	ER names qualitative markers.

Issues 10/25/2026 01:19

Pass rate 100.00%. No issues found.

Issues 10/25/2026 01:15

1. 8.5 — Severity class dropped: The first contraindication at line 540, “Known hypersensitivity to modafinil or armodafinil”, omits the ER bullet’s parenthetical severity class “(contraindicated)”.

Fixes 10/25/2026 01:15

1. 8.5 — Severity class restored: Changed the first contraindication from “Known hypersensitivity to modafinil or armodafinil” to “Known hypersensitivity to modafinil or armodafinil (contraindicated)”, restoring the ER’s parenthetical.

Issues 10/25/2026 01:11

1. 14.2 — ALT marker missing: The ER Monitoring section names ALT (alanine aminotransferase, a liver-injury enzyme) as a marker to pair with GGT and ALP (ER line 445), but the QRS Monitoring table (lines 608-686) has no ALT row.

Fixes 10/25/2026 01:11

1. 14.2 — ALT marker added: Inserted an ALT row in the Monitoring table (target “Not specified in the ER”, why “Liver-injury enzyme, paired with GGT and ALP”) after ALP and renumbered the following markers to 6–8.

Issues 10/25/2026 01:07

1. 1.4 / 11.1 / 11.3 — Steady state as time-to-effect: The third Time to effect set (time_3, lines 503–509) shows “Steady state / 2–4 days / Of daily use; half-life about 12–15 hours”, a pharmacokinetic fact from the ER’s “Half-life” bullet, while the ER states “no build-up period is needed for wakefulness”; the ER gives only two time-to-effect aspects, so the third set should be left empty and hidden with style=”display:none”.

Fixes 10/25/2026 01:07

1. 1.4 / 11.1 / 11.3 — Steady state set hidden: Emptied the time_3 label, value and sub spans (“Steady state / 2–4 days / Of daily use; half-life about 12–15 hours”) and hid the third Time to effect set with style=”display:none”, since the ER gives only two time-to-effect aspects.

Issues 10/25/2026 01:05

1. 2.7 — Specialist term in sub: The Cognitive performance time-to-effect sub at line 498 uses “executive function”, a term the ER itself glosses as “(planning and self-control)”; it is free text, not an ER label.
2. 4.5 — Benefit repeated in timing: The time_2_sub at line 498 “Small gains in attention, executive function and memory” restates the High benefit “small gains in cognitive performance in rested adults” (line 520) instead of giving timing information.

Fixes 10/25/2026 01:05

1. 2.7 / 4.5 — Time-to-effect cognitive sub: Replaced time_2_sub “Small gains in attention, executive function and memory; clearest on complex tasks” with “Trials measured gains after one dose; clearest on complex tasks”, removing the jargon and the repeated benefit statement.

Issues 10/25/2026 01:01

1. 1.2 / 1.3 — Cognitive hedge stripped: The Time to effect cell time_2 (line 498) reads “Attention, executive function and memory; clearest on complex tasks”, dropping the ER’s “modestly improve” / “real but small average effect” (ER line 160), which strengthens the claim where no tier label carries it.

Fixes 10/25/2026 01:01

1. 1.2 / 1.3 — Cognitive hedge restored: Changed time_2_sub from “Attention, executive function and memory; clearest on complex tasks” to “Small gains in attention, executive function and memory; clearest on complex tasks”, restoring the ER’s small-effect hedge.

Issues 10/25/2026 00:57

1. 4.5 — Repetition in time cell: Time to effect cell 3 (lines 506-509) pairs the value “Single dose” with the sub “Single 100–200 mg doses modestly improve…”, repeating the value and restating Protocol cell 2 (“Single 100 or 200 mg dose”, line 456).
2. 11.2 — Time sets misordered: “Steady state” (time_2, line 492), a pharmacokinetic aspect tied to no benefit, is placed ahead of “Cognitive performance” (time_3, line 503), which belongs to a High-tier benefit.

Fixes 10/25/2026 00:57

1. 4.5 — Repetition in time cell: Replaced the cognitive cell sub “Single 100–200 mg doses modestly improve attention, executive function and memory in rested adults” with “Attention, executive function and memory; clearest on complex tasks”, removing the repeat of the value and of Protocol cell 2.
2. 11.2 — Time sets misordered: Swapped the two cells so “Cognitive performance” (High-tier benefit) is now time_2 and “Steady state” is time_3.