Audit: QRS - Phenylpiracetam for Health & Longevity

Audit conducted on 04/09/2026 18:01 using AI4L / Opus 5

Iterations

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.	🟢	Every populated span traces to ER text: protocol cells to Therapeutic Protocol, time cells to Practical Considerations and Expected Benefits, gates to Key Interactions & Contraindications, markers to the Monitoring Protocol table.
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.	🟢	“no trial has tested healthy people” (time_3_sub) mirrors ER line 176; “Long-term use is unstudied” mirrors ER line 442; marker_4_target keeps “No established target”.
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”).	🟢	Contraindications retain absolute framing; “Side effects look mild and reversible” is bounded by the closing “Long-term use is unstudied”, matching ER lines 442.
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 Phenylpiracetam” list; Key Interactions only from the ER’s interaction bullets; no Benefit- or Risk-Modifying Factor is surfaced as 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 carries no PMIDs, no NCT identifiers, no author names and no brand names.
1.6	The QRS does not introduce new attributions.	🟢	No attributions of any kind appear; “Standard Russian clinical course” is the ER’s own bold label (ER line 317).

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.	🟢	Reserved, sceptical register matching the ER’s treatment of the Russian-only evidence base.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Numeric targets and dose ranges throughout, paired with plain-language framing in At-A-Glance.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Statements are descriptive (“the trials used”, “Onset is under an hour”), not directive.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	Monitoring cadence and protocol cells are phrased impersonally and passively; no prescriptive instruction to a reader.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No “should”, “recommended” or “advised” appears in the QRS’s own voice.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronoun appears anywhere in the document.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Jargon is confined to unavoidable biomarker names (ALT, eGFR, HbA1c, TSH, MFI-20) in the Monitoring table.
2.8	Information is presented in a concise and very compact manner	🟢	Tier lines are semicolon-joined single items; gate items are noun phrases; marker “Why” cells are single clauses.
2.9	It DOES NOT address the reader directly	🟢	Confirmed: no direct address anywhere in the QRS.
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 reader who will source, dose, cycle and lab-monitor an unapproved compound.
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.	🟢	An 11-marker laboratory panel, twice-weekly home blood pressure and continuous wearable sleep tracking are presented without dilution.
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.	🟢	Functional optimal ranges (ALT 10–20 U/L, TSH 0.5–2.0 mIU/L) are used rather than conventional population reference ranges.
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 unregulated supply, the doping ban and the absent long-term data — the decision points that matter to a self-directed optimiser.
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.	🟢	“anti-aging” does not occur; the title uses “Health & Longevity”.
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 throughout (“adverse effect”, “myocardial infarction”, “hepatic impairment”); the plain wording in At-A-Glance (“memory drug”, “sleeplessness”) is ER-verbatim from the Conclusion and is required there by item 7.4.

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 verbatim (lines 444, 484, 529, 588, 610, 768, 550, 565, 614–616); tier labels High/Medium/Speculative intact, with Low correctly suppressed under item 12.5.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 template span names verified present by set comparison; the only additions are the repeated marker_#* and qualitative_item# instances the template defines as repeatable rows.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The three non-variable spans (website="evidence_review", website="audit", website="full_review") are byte-identical to the template; head, CSS and structure diff clean apart from populated values.

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	The only empty ER section mapping to a QRS variable is Expected Benefits → “Low”, and the ER supplies no empty-state phrasing there; item 12.5 governs that case instead.
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 “Standard Russian clinical course”, action_2_label “Best time of day”, action_3_label “Single versus split dosing” are the ER’s bold labels verbatim (ER lines 317, 323, 327).
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	All 11 marker names reproduce the ER biomarker table’s first column verbatim (ER lines 398–408).
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji characters occur in the QRS; tiering is carried 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.	🟢	Each section is condensed to its minimum: tiers collapsed to single semicolon-joined lines, gate items reduced to noun phrases, marker “Why” cells to one clause each.

---

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; the next comment (“QRS (Quick Reference Sheet) — blank template”) follows at line 16.
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 sits on line 2.
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 entirely within an HTML comment; no metadata value is echoed into the body.
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; all other values are bare and trimmed.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: phenylpiracetam_2026-0904-1454_Opus_ER.md, matching the ER’s own filename frontmatter value.
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 head 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-0904-1756, correct 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 carrying 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 with no trailing qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9: qrs_filename: phenylpiracetam_2026-0904-1454_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 including the git_user and git_issue additions; no stray whitespace or redundant 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., & for &)	🟢	Line 22: “Phenylpiracetam for Health & Longevity - Quick Reference Sheet” against ER canonical_topic “Phenylpiracetam for Health & Longevity”; ampersand correctly 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: “Phenylpiracetam for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “09/04/2026”, the correct MM/DD/YYYY rendering of qrs_creation_date 2026-0904-1756.
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 block (lines 415–428) is structurally identical to the template; the ER’s “Also known as” line was not carried over.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	All five clauses map to the ER Conclusion (lines 438–442): origin and potency, fatigue signal, evidence provenance, side-effect profile, supply and doping hazards.
7.2	[at_a_glance] is no longer than 60 words	🟢	58 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	“month-long courses” → ER line 440; “Russian, industry-linked and unrepeated” → ER line 440; “mild and reversible… sleeplessness and irritability” → ER line 442; supply and doping → ER line 442.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “asthenia” is rendered as “persistent fatigue” and “racetam” as “relative of the first memory drug”.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial name, year, cohort size or p-value appears.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	The 16.3-point MFI-20 fall and the 5.5% adverse-event rate from the ER are deliberately omitted.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All eight items derive from the “Populations who should avoid Phenylpiracetam” list at ER lines 286–295.
8.2	[stop_items] represent the Contraindications from the ER	🟢	Eight ER bullets, eight QRS items, in ER order; the MAOI bullet (ER line 268, “absolute contraindication”) is correctly represented here rather than under Key Interactions.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Lines 553–560: eight 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.	🟢	Definitional glosses stripped: “(heart attack)”, “(chest pain at rest)”, “(irregular heartbeat)”, “the most advanced grade of liver failure” and the eGFR expansion are all removed; no dash-trailing clause remains.
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).	🟢	“at or above 180/110 mmHg”, “within 90 days”, “Child-Pugh Class C”, “eGFR below 30 mL/min/1.73 m²”, “in or near a manic phase”, “under 18 years of age” and “within two weeks of stopping one” all retained.
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 uses no ranking notation inside parentheses anywhere in Key Interactions & Contraindications.
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 eight such populations, and the section is correctly populated rather than left empty.
8.8	If the section is left empty, an HTML comment inside the [stop_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g.	N/A	The section is not empty.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All nine items derive from the interaction bullets at ER lines 266–284.
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 appear; the MAOI bullet is correctly excluded because it is already a contraindication item.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Lines 568–578: nine 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 text is stripped; the “Choline donors” item retains only “no interaction risk”, which is that bullet’s key fact (ER line 280) and not an elaboration.
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 named example list is preserved; only the longest lists are trimmed for budget (lisdexamfetamine, higenamine), consistent with the item’s explicit allowance.
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 parentheses are plain comma-separated drug lists; no ranking notation is used.
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 interactions, and the section is correctly populated rather than left 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 317, 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 administration, and single-versus-split dosing are the three decisions that determine how the compound is actually taken.
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 eleven bullets, well above three; 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 cells populated; values carry the ER’s figures verbatim (100–200 mg/30 days, before 12:00, 200 mg single or split).

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	🟢	Fatigue at 30 days (ER line 366), stroke recovery over three courses in one year (ER line 154), and subjective stimulation within about an hour (ER line 366).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered High (persistent fatigue) → Medium (recovery after brain injury) → Speculative (subjective alertness), matching the ER’s benefit tiers.
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 at least three distinct time-to-effect aspects; no set is unused.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All nine cells populated with ER-traceable content; no placeholder text remains.
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 at line 366, so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All eight listed benefits are the ER’s Expected Benefits sub-headings (ER lines 144–188).
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present at lines 531, 534, 538 and 539.
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 semicolon-joined list of ER sub-headings; the 16.3-point MFI-20 magnitude, the 549-patient pooled cohort and the p < 0.0001 figure are all excluded.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	“(Asthenia)” is stripped from the High tier; no parenthetical survives in any tier.
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’s “Low 🟩” benefit tier is empty (ER lines 170–171) and benefits_low is correctly set to style="display: none" 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 six listed risks are the ER’s Potential Risks & Side Effects sub-headings (ER lines 212–248).
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present and populated at lines 590, 594, 598 and 601.
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 5.5% adverse-event rate, the 75% mislabelling figure and the 1998 doping-ban date are all excluded; each tier is a bare sub-heading list.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content appears in any risk tier.
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 ER risk tiers carry at least one entry, so no span needs suppressing.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Every row derives from the ER Monitoring Protocol & Defining Success biomarker table (ER lines 396–408).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All 11 ER biomarkers present in ER order: seated blood pressure, resting heart rate, sleep time/onset, MFI-20, ALT, eGFR, fasting glucose, HbA1c, TSH, ferritin, vitamin B12.
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 759–762 reproduce the ER’s ongoing-monitoring paragraph (ER line 394): twice weekly vitals, day-30 fatigue re-score, six-monthly panel where courses recur, continuous wearable sleep tracking.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	All five items come from the qualitative-marker list at ER lines 412–416.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All five ER qualitative markers reproduced verbatim and in ER order.

Issues 04/09/2026 18:01

Pass rate 100.00%. No issues found.