Audit: QRS - Piracetam for Health & Longevity

Audit conducted on 03/07/2026 01:12 using AI4L / Opus 4.8

Iterations

Summary

Items	Count
Total	91
Passed	91
Failed	0
N/A	0
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 QRS content traces to the ER (benefits, risks, gates, protocol, monitoring).
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.	🟢	Speculative tiers and “unproven for long-term brain protection” mirror ER caution.
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 (pregnancy, severe renal impairment) carried at full strength.
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 come from ER Key Interactions & Contraindications; risks from Potential Risks & Side Effects.
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, or expert names introduced; drug/brand names (warfarin, etc.) match ER.
1.6	The QRS does not introduce new attributions.	🟢	No new attributions.

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.	🟢	Tone matches the ER’s balanced, evidence-graded framing.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Meets tone requirement.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Presents evidence, not prescriptions.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No advice language; footer disclaimer preserved.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Content is descriptive.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No direct address.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Plain-language throughout the visible content.
2.8	Information is presented in a concise and very compact manner	🟢	Compact card/table layout.
2.9	It DOES NOT address the reader directly	🟢	No second-person address.
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.	🟢	Framing targets 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.	🟢	Consistent with audience.
2.12	The document is NOT written for the general population, who are unwilling to employ lifestyle and behavioral changes or follow protocols that may be inconvenient, costly, or require effort.	🟢	Not general-population framed.
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.	🟢	Longevity framing (e.g., “unproven for long-term brain protection”) is audience-appropriate.
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.	🟢	No “anti-aging” phrasing; uses “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.	🟢	Uses clinical register (e.g., “gastrointestinal disturbance”, “antiplatelet effect”).

3. Template Integrity

#	Description	Result	Comments
3.1	The following labels and headings on the QRS are fixed and not modified: Card and section headings: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”; Gate headings: “Contraindications”, “Key Interactions”; Tier labels: “High”, “Medium”, “Low”, “Speculative”; Table column headers in Monitoring: “Marker”, “Target”, “Why”	🟢	All fixed headings and labels present and unmodified.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All template variable regions present; marker_# and qualitative_item_# instantiated as needed.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Non-addressed spans unchanged.

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”	🟢	No empty ER sections applied here; all populated sections have content.
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.	🟢	Benefit/risk tier labels and marker names align with ER.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Labels preserved.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji indicators in the QRS.
4.5	The QRS is designed to render on one A4 page. Any section that has more content in the ER than fits the per-section budget is condensed by the LLM, not extended onto a second page.	🟢	Content condensed to single-page layout.

---

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.	🟢	Metadata comment is the first element after <!doctype html> (lines 2-14).
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.	🟢	--- on lines 3 and 13 delimit the YAML block.
5.3	The metadata is not visible in any rendered view of the QRS and is not surfaced by any other element on the sheet.	🟢	Inside HTML comment; not rendered.
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.	🟢	Values trimmed; duration: "00:00" correctly quoted (contains colon).
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	er_filename: piracetam_2026-0703-0004_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 (line 5) matches QRS.md version.
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-0703-0108 (line 6).
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 (line 7).
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 single-word.
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 4.8 (line 8).
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 4.8” is nickname + version, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	qrs_filename: piracetam_2026-0703-0004_Opus_QRS.html (line 9).
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.	🟢	Values clean and consistent.

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 &)	🟢	“Piracetam 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., & for &)	🟢	“Piracetam for Health & Longevity” (line 417).
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	“07/03/2026” matches 2026-0703 (line 421).
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	“Opus 4.8” (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.	🟢	Only the standard subline; no extra header content.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Condenses the ER Conclusion (lines 450-454).
7.2	[at_a_glance] is no longer than 60 words	🟢	50 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Safety record, mixed evidence, myoclonus, childhood spells, memory gains, unproven longevity — all in Conclusion.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	“nootropic” and plain terms only; no specialist acronyms.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial citations.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No statistics.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	Derived from ER line 316 (populations who should avoid).
8.2	[stop_items] represent the Contraindications from the ER	🟢	All five ER contraindications represented.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Each item is a separate <li> (lines 542-546).
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.	🟢	Items are concise; ER’s “(worsening has been reported)” dropped for Huntington disease.
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).	🟢	“eGFR <30 mL/min” threshold and “end-stage kidney disease” 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.	🟢	No ranking notation to normalize; “<30” is a plain threshold and retained.
8.7	If no [stop_items] are present the section is left empty	🟢	Contraindications present, so condition does not require empty state.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	Derived from ER lines 304-314.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Six interactions listed; no contraindication duplicated.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Each interaction a separate <li> (lines 554-559).
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.	🟢	Severity/Consequence/Mitigation clauses stripped; only the agent classes retained.
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 example drug lists preserved (warfarin/apixaban/clopidogrel; ibuprofen/naproxen; alpha-GPC/citicoline; etc.).
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.	🟢	No ranking notation present; items are plain comma-separated lists.
9.7	If no [caution_items] are present the section is left empty	🟢	Interactions present, so condition does not require empty state.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER Protocol section	🟢	Derived from ER Therapeutic Protocol (lines 336-348).
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Standard dose, dosing schedule, and timing are the key actionable aspects.
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.	🟢	All three sets have distinct real content; condition not triggered.
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section.	🟢	All three action sets fully populated from the ER.

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	🟢	Myoclonus, cognitive support, and personal-trial windows drawn from ER line 387.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Myoclonus (High) first, cognitive support (Medium) second, personal trial third.
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.	🟢	Three distinct aspects present; condition not triggered.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All three time sets populated from the ER.
11.5	If the ER does not provide any information on time to effect, the section is removed completely from the Protocol Panel	🟢	ER provides time-to-effect info (line 387), so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	Derived from ER Expected Benefits (lines 160-212).
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four tier variables populated per ER tiers.
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.	🟢	Benefit items are terse key facts; the ER’s “⚠️ Conflicted” qualifier is correctly dropped from the Medium item.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content retained in the benefit items.
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.	🟢	All four tiers have content in the ER, so no display:none required.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	Derived from ER lines 230-284.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four tier variables populated per ER tiers.
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.	🟢	Items are terse key facts (e.g., “Central nervous system overstimulation”).
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheticals retained in risk items.
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.	🟢	All four tiers have ER content; no display:none required.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Derived from ER Monitoring Protocol & Defining Success (lines 407-421).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All five ER table biomarkers listed (eGFR, creatinine, BUN, CBC/platelets, body weight).
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.	🟢	Cadence populated (baseline, ~3 months, then every 6–12 months) from ER lines 411-413.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Derived from ER qualitative markers (lines 425-428).
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All four ER qualitative markers listed (cognitive clarity/memory, sleep quality, mood/anxiety, energy/headache), lines 666-675.

Issues 03/07/2026 01:12

Pass rate 100.00%. No issues found.