Audit: QRS - Alpha-GPC for Health & Longevity

Audit conducted on 06/09/2026 07:01 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 93
Passed 83
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. 🟢 Every span traced to ER: protocol cells to ER Therapeutic Protocol bullets, time cells to ER Practical Considerations / Expected Benefits, benefit and risk lines to ER tier headings, gates to Key Interactions & Contraindications, monitoring rows and cadence to the ER Monitoring Protocol & Defining Success table and prose, qualitative items verbatim from the same section.
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. 🟢 “the unresolved question is long-term artery risk” and “the evidence is thin” mirror the ER Conclusion’s “The unresolved question is long-term and vascular” and “In healthy adults the evidence is thinner”.
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 their absolute framing; “Pregnancy and breastfeeding” is carried as a stop item, not downgraded to a caution. Risk tiers match ER tiers exactly.
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. 🟢 Stop items come only from the ER’s “Populations who should avoid Alpha-GPC” list; caution items only from the ER interaction bullets. No Benefit- or Risk-Modifying Factor 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. 🟢 The QRS contains no PMIDs, citations, author names, NCT identifiers or brand names at all.
1.6 The QRS does not introduce new attributions. 🟢 Attribution-free throughout; “one trial”, “the healthy-adult trial” are unnamed and match ER phrasing.

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. 🟢 The ER’s sceptical, conflict-of-interest-aware register is carried through, including the closing At-A-Glance sentence on industry funding.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Doses, windows and biomarker targets are given concretely, with the limits stated rather than hidden.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 No imperatives; protocol cells describe what was tested (“The dose used in almost every clinical trial”).
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Descriptive throughout; the footer disclaimer is the template’s own fixed text.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No instances of “recommend”, “advise”, or “should” in the QRS body.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns anywhere in the file.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Acronyms are expanded to full terms (trimethylamine N-oxide, estimated glomerular filtration rate, thyroid-stimulating hormone) rather than left as TMAO/eGFR/TSH.
2.8 Information is presented in a concise and very compact manner 🟢 Gate items are bare facts; benefit and risk lines are tier headings only; monitoring rows carry a single clause each.
2.9 It DOES NOT address the reader directly 🟢 Confirmed by search: no “you”, “your” or “yours”.
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 biomarker targets (apolipoprotein B <80 mg/dL, high-sensitivity C-reactive protein <0.5 mg/L) are set to the optimizer standard, not the conventional lab cut-off.
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. 🟢 Three-times-daily dosing, an eight-marker panel and specialty trimethylamine N-oxide testing are presented without hedging on inconvenience.
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. 🟢 Content assumes access to laboratory testing and willingness to run a months-long trial before judging effect.
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 At-A-Glance separates the damaged-brain evidence from the thin healthy-adult evidence, which is the distinction that matters to this audience.
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; 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. 🟢 “Gastrointestinal upset”, “cholinergic overstimulation”, “ischaemic or haemorrhagic stroke”, “coronary revascularisation” — no consumer-grade substitutes.

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 strings match the template byte-for-byte (lines 445, 491, 541, 569, 588, 612, 637, 641-643, 770 and the four tier labels in each of the Benefits and Risks cards).
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 Every template variable is present; the repeatable marker_#* and qualitative_item# spans are instantiated as marker_1..8_* and qualitative_item_1..6 (64 spans total).
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 A full diff against the template shows differences only inside variable regions and the metadata block; all CSS, structural markup, the website="…" spans and the footer disclaimer 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 drawn on by the QRS is empty; every benefit and risk tier, both gate lists, the monitoring table and the qualitative list are populated in the ER.
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. 🟢 “Cognitive-decline protocol”, “Acute cognitive and performance protocol” and “Best time of day” are the ER’s bold labels verbatim (ER lines 320, 322, 328).
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Monitoring marker names are the ER table’s own row labels verbatim; the Time-to-Effect cell labels use the ER’s own wording for the three aspects the single “Time to effect” bullet covers.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 Unicode scan returns no emoji; the ER’s tier emoji and the “⚠️ 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. 🟢 Each section is condensed to its per-section budget rather than carried over: gate items are stripped to the bare fact, benefit and risk lines to tier headings only, monitoring rows to a single clause, and no section duplicates or extends the template’s fixed structure.

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 metadata comment opens immediately after <!doctype html> on line 1 and precedes every other comment and element.
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 --- on line 3 and closing --- on line 13; the “QRS — Metadata” caption on line 2 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; no metadata value is repeated in the head or 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, and that value contains a colon requiring YAML quoting; 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: alpha_gpc_2026-0906-0422_Opus_ER.md, matching the ER’s own filename frontmatter key.
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 top 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-0906-0647, correctly formatted.
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 with 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 context-window or other qualifier appended.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 Line 9: qrs_filename: alpha_gpc_2026-0906-0422_Opus_QRS.html, identical to the file’s name 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; no stray whitespace and no unnecessary 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 &) 🟢 Line 22: “Alpha-GPC for Health & Longevity - Quick Reference Sheet”, matching the ER’s 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., &amp; for &) 🟢 Line 417: “Alpha-GPC for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 Line 421: “09/06/2026”, the correct MM/DD/YYYY rendering of 2026-0906-0647.
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 is structurally identical to the template; no alternate-names line was carried over from the ER despite the ER listing six.

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 onto the ER Conclusion’s three paragraphs: mechanism, damaged-brain strength, healthy-adult weakness, short-term tolerability, vascular uncertainty, industry funding.
7.2 [at_a_glance] is no longer than 60 words 🟢 55 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each clause traces to a distinct ER Conclusion sentence (ER lines 449, 451, 453).
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms; “artery risk” is used in place of the ER’s vascular/trimethylamine N-oxide vocabulary.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No study names, years or sample sizes appear.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No effect sizes, hazard ratios or confidence intervals appear.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All six items come from the “Populations who should avoid Alpha-GPC” list in that ER section (ER lines 293-298).
8.2 [stop_items] represent the Contraindications from the ER 🟢 All six ER avoid-populations are present, none added.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Six discrete <li> elements inside the stop_items span (lines 572-583).
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. 🟢 ER trailing rationales (“because TMAO clearance is renal”, “given the unreplicated thyroid-stimulating hormone finding”, “where no safety data exist at supplemental doses”, “in whom choline loads worsen symptoms”) are all stripped; no dash-trailing clauses remain.
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). 🟢 “within 12 months”, “(<12 months)”, “stage 3b or worse” and “(estimated glomerular filtration rate <45 mL/min/1.73 m²)” are 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’s avoid-populations list uses no ranking notation inside parentheses; the only “>”-class symbols are numeric thresholds.
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 six such populations and the section is correspondingly populated, not 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, so no empty-state comment is required.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All nine items map one-to-one onto the nine interaction bullets at ER lines 273-289.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Complete set of nine; no overlap with the six contraindication entries.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Nine discrete <li> elements inside the caution_items span (lines 591-602).
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 ER bullet’s Severity/Consequence/Mitigation tail is stripped; the only hyphens remaining are inside compound words (“Over-the-counter”, “L-Carnitine”, “N-oxide”).
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 ER drug list is retained; the two four-drug lists are trimmed to three named examples each rather than dropped.
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 bullets use plain comma-separated drug lists in parentheses, 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 nine interactions and the section is correspondingly populated, not 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, so no empty-state comment is required.

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 ER lines 320, 322 and 328.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 The two dosing regimens the ER itself frames as the alternatives (“Neither is the default”) plus timing-of-day are the three decision-bearing aspects; the remaining ER bullets are genotype, sex and age caveats.
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 provides well more than three actionable aspects, so all three sets are used and none is left unfilled.
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 carry substantive ER-derived content; no placeholder text remains.

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 🟢 Cognitive decline (3 to 6 months), acute attention and explosive power are exactly the three aspects the ER’s “Time to effect” bullet distinguishes (ER line 379).
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Cognitive decline and acute attention both attach to the High-tier cognitive benefit and precede explosive power, which attaches to the Low 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, so 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 are populated; the sub-lines carry the ER’s own caveats (12-month significance, attention-only effect, six-day isometric measurement).
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 does provide time-to-effect information, so the section is correctly retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All seven benefit headings from the ER’s four tiers are represented.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present and populated (lines 543-562).
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 carries only the ER’s benefit headings, semicolon-separated; every Magnitude paragraph is excluded.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses appear in any benefit line; the ER’s “⚠️ Conflicted” marker on explosive power is correctly dropped.
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. N/A The ER populates all four benefit tiers, so no span needed hiding.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All five risk headings from the ER’s four tiers are represented.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present and populated (lines 614-631).
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. 🟢 Each tier carries only the ER’s risk headings; the hazard ratios and confidence intervals in the ER Magnitude paragraphs are excluded.
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 line; the ER’s “⚠️ Conflicted” marker on the stroke item is correctly dropped.
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 The ER populates all four risk tiers, so no span needed hiding.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Every row comes from the ER Monitoring Protocol & Defining Success biomarker table (ER lines 407-416).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All eight ER rows are present — trimethylamine N-oxide, homocysteine, estimated glomerular filtration rate, thyroid-stimulating hormone, apolipoprotein B, high-sensitivity C-reactive protein, blood pressure and standardised cognitive test score — with targets and rationales carried 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. 🟢 Lines 760-764 reproduce the ER’s baseline, 8-to-12-week recheck, 6-to-12-month repeat and 4-weeks-after-cessation schedule.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 All six items come from the ER’s “Qualitative markers worth tracking alongside the laboratory panel” list (ER lines 420-425).
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All six ER qualitative markers are present and carried verbatim; none omitted or added.

Issues 06/09/2026 07:01

Pass rate 100.00%. No issues found.

Issues 06/09/2026 06:54

  1. 2.7 — Unexpanded acronyms in gates: “eGFR” (line 577, Contraindications) and “TMAO” (line 596, Key Interactions) appear as bare acronyms that are never expanded anywhere in the QRS, while the same terms are spelled out in full in the Monitoring table and risk tiers (“Estimated glomerular filtration rate”, “Trimethylamine N-oxide”).

Fixes 06/09/2026 06:54

  1. 2.7 — Unexpanded acronyms in gates: Expanded “eGFR” to “estimated glomerular filtration rate” in the Contraindications item on chronic kidney disease, and replaced “other TMAO-lowering interventions” with “other interventions that lower trimethylamine N-oxide” in the Key Interactions item on allicin-containing garlic and resistant starch.