Audit: QRS - P21 for Health & Longevity

Audit conducted on 02/10/2026 02:47 using AI4L / Opus 5.5

Iterations

Summary

Items Count
Total 94
Passed 88
Failed 0
N/A 6
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 doses, durations, thresholds, ranges, labels and lede statements trace to ER Conclusion, Therapeutic Protocol, Practical Considerations, Risk Mitigation and Monitoring sections
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 interaction; “human onset is unknown”, “no data exist”, “theoretical tumor and pregnancy concerns” carried over
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”). 🟢 Avoid/Caution/Monitor severities match ER verbatim; appetite risk framed as “possible”, consistent with ER “unconfirmed for P21”
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 from “Populations who should avoid P21”, interactions from the interaction list, tiers match ER tiers
1.5 PubMed IDs, study citations, expert names, clinical trial identifiers (NCT*), and brand names appear in the QRS only if they appear in the source ER for the same fact. 🟢 Only “Peptide Initiative” and “Biomogging” named, both attached to the same regimens in the ER; no PMIDs or NCT IDs
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. 🟢  
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢  
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 🟢 Regimens framed as “as listed by” community sources
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 🟢  
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical terms limited to ER labels carried verbatim; marker names glossed (e.g., “ALT (liver enzyme)”)
2.8 Information is presented in a concise and very compact manner 🟢  
2.9 It DOES NOT address the reader directly 🟢  
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. 🟢  
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. 🟢  
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. 🟢  
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. 🟢  
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” wording
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)”; “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. 🟢 “Intranasal or subcutaneous injection”, “oral use”

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 labels unchanged
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All template variables present; marker_# and qualitative_item_# expanded to 9 and 7 rows
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Diff against template shows only variable spans and metadata changed; website spans and footer 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” 🟢 Empty ER tiers are hidden per 12.5/13.5; no deviating empty-state text introduced
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. 🟢 “Community intranasal regimen”, “Community subcutaneous regimen”, “Route” and all interaction labels verbatim
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. 🟢 No emojis; ⚠️ markers from ER headings stripped
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 tier lists and short gate items

5. Metadata

# Description Result Comments
5.1 The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content. 🟢 Lines 2-14
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” 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.1
5.7 Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) 🟢 2026-1002-0232
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 just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) 🟢 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 [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.5
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢  
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. 🟢  

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 &) 🟢 “P21 for Health & Longevity - Quick Reference Sheet”
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢  
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 10/02/2026
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Opus 5.5
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 🟢 Opens “P21 is a small laboratory-made peptide … of interest for protecting memory and brain function with age”
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. 🟢 Conclusion paragraphs 1-4 and Sourcing and Quality
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 5 “Populations who should avoid P21” entries, verbatim
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. 🟢  
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). 🟢 ER items carry no parentheticals
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. 🟢 Section populated
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 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 8 interactions that change use are listed; aerobic exercise (“no mitigation is needed”) omitted
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. 🟢 Label plus severity only
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 drug lists 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. 🟢 Section populated
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 not empty

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 ER Therapeutic Protocol
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Intranasal regimen, subcutaneous regimen, route (with dosing frequency and time of day)
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 ER provides more than three aspects
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol 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 🟢 ER gives two time-to-effect aspects; both used
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 P21 rodent memory/pathology effects first, parent Peptide 6 second
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. 🟢 time_3 cell empty and display: none
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 does not provide any information on time to effect, the section is removed completely from the Protocol Panel N/A ER provides time-to-effect information

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Speculative headings verbatim; “Not Central” early-life item excluded
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 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. 🟢 High, Medium, Low spans hidden

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 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. 🟢 High and Medium spans hidden

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢  
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All 7 table biomarkers plus body weight and cognitive test from the section text
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. 🟢 Verbatim ER cadence

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢  
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All 7 qualitative markers, verbatim

Issues 02/10/2026 02:47

Pass rate 100.00%. No issues found.

Issues 02/10/2026 02:44

  1. 1.3 — Route presented as established: Protocol cell 3 (lines 469-472) states “Intranasal or subcutaneous injection” and “one daily dose” as the route and dosing, whereas the ER says only that community users mostly choose these routes and that community protocols use one daily dose.

Fixes 02/10/2026 02:44

  1. 1.3 — Community-practice qualifier restored: Changed action_3_sub to open with “Mostly chosen by community users;” and replaced “one daily dose” with “community protocols use one daily dose”, matching the ER Route and Single or split dose bullets.

Issues 02/10/2026 02:41

  1. 1.1 / 7.4 — Unavailability overstated as nonexistence: At a Glance (line 433) says “no pharmaceutical-grade product exists”; the ER only states that no pharmaceutical-grade product “is available” (Conclusion) / “is commercially available” (Sourcing and Quality).

Fixes 02/10/2026 02:41

  1. 1.1 / 7.4 — Unavailability overstated as nonexistence: Changed At a Glance from “no pharmaceutical-grade product exists” to “no pharmaceutical-grade product is available”, matching the ER Conclusion wording.

Issues 02/10/2026 02:39

  1. 7.2 — At-a-glance omits key takeaway: The [at_a_glance] (line 433) omits the Conclusion’s execution-relevant point that nearly all evidence comes from the developer’s single laboratory and no pharmaceutical-grade product exists, and states “it improved memory” as fact where the ER says “reported benefits”.

Fixes 02/10/2026 02:39

  1. 7.2 — At-a-glance key takeaway added: Rewrote [at_a_glance] to frame animal findings as “reported” by studies nearly all from the developer’s laboratory and to add that no pharmaceutical-grade product exists (68 words).

Issues 02/10/2026 02:37

  1. 1.2 — Cautious timing qualifier dropped: action_3_sub (QRS line 472) says “morning dosing is common practice” without the ER’s “No data exist” qualifier (ER line 288, Time of day).

Fixes 02/10/2026 02:37

  1. 1.2 — Cautious timing qualifier restored: Changed action_3_sub from “one daily dose, morning dosing is common practice” to “one daily dose; time of day: no data exist, morning dosing is common practice”, restoring the ER’s “No data exist” qualifier.

Issues 02/10/2026 02:33

  1. 2.7 — Unexplained specialist terms in Monitoring: “CNTF-class appetite loss” (line 653), “Serum BDNF” / “P21 raises BDNF” (lines 658, 664) and “Plasma p-tau217” (line 669) are given without the plain-language explanation the ER provides.
  2. 4.3 / 12.3 — Benefit label altered with qualifier: The speculative benefit “Recovery After Brain Injury” (ER line 163) appears as “Recovery After Brain Injury with parent Peptide 6” (QRS line 525), which changes the ER heading and adds a qualifier.

Fixes 02/10/2026 02:33

  1. 2.7 — Glossed Monitoring specialist terms: Changed marker_6_why from “CNTF-class appetite loss” to “the parent protein caused appetite loss”, added “(brain growth factor)” to Serum BDNF and reworded its Why, and added “(blood form of tau, an Alzheimer-linked protein)” to Plasma p-tau217.
  2. 4.3 / 12.3 — Restored verbatim benefit label: Changed “Recovery After Brain Injury with parent Peptide 6” to the ER heading “Recovery After Brain Injury”.