Audit: QRS - P7C3 for Health & Longevity

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

Iterations

Summary

Items	Count
Total	94
Passed	89
Failed	0
N/A	5
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.	🟢
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.	🟢
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”).	🟢
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.	🟢
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.	🟢
1.6	The QRS does not introduce 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	🟢
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	🟢
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.	🟢
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.	🟢

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	All “…” from the [qrs_template] are present in the the QRS.	🟢	All template spans present; marker_# and qualitative_item_# expanded to 1–5 and 1–4.
3.3	Spans that are not addressed in a checklist item are left 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”	🟢
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.	🟢
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. 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.	🟢

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.	🟢
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]”	🟢
5.7	Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430)	🟢
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)	🟢
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)	🟢
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., & 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]	🟢
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	🟢
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	🟢	70 words (wc -w).
7.4	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢
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	🟢
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).	🟢
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.	🟢	ER contraindication list contains no ranking notation; no bare symbols carried through.
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.	🟢
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	Contraindications section is populated with five ER populations; not left 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	🟢
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).	🟢
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.	🟢	ER interaction list contains no ranking notation; no bare symbols carried through.
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.	🟢
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	Key Interactions section is populated with eight ER interactions; not left empty.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER Protocol section	🟢
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢
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 Therapeutic Protocol lists more than three distinct aspects (no-human-regimen statement, primate regimen, rodent range, route, split dosing, etc.); all three sets are used.
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	🟢
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢
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	ER Practical Considerations gives exactly three time-to-effect aspects (5–15 days, about 30 days, weeks to months); 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.	🟢
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 (Practical Considerations, line 371); section retained.

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 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 set to style=”display: none”; only Speculative populated.

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, Medium, Low spans set to style=”display: none”; only Speculative populated.

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	🟢
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.	🟢

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	🟢

Issues 11/10/2026 02:58

Pass rate 100.00%. No issues found.

Issues 11/10/2026 02:54

1. 1.1 / 1.3 — Safety-record qualifier dropped: At a Glance (line 433) says “no human dose, safety record or approved product”, while the ER Conclusion (line 440) says “no safety record in people”; omitting “in people” strengthens the claim, since an animal safety record (primate toxicology) exists.
2. 9.5 — Named example drugs dropped: Interaction lists (lines 554–558) omit ER-named examples voriconazole (CYP2C19), tizanidine (CYP1A2), esomeprazole (OTC) and nicotinamide mononucleotide (Vitamin B3 forms), the last being directly relevant to a longevity audience.

Fixes 11/10/2026 02:54

1. 1.1 / 1.3 — Safety-record qualifier restored: Changed At a Glance ending from “no human dose, safety record or approved product” to “no dose, safety record or approved product for humans”, and “not a supplement or licensed medicine” to “neither supplement nor licensed medicine” to stay within 70 words.
2. 9.5 — Named example drugs restored: Re-added ER-named examples voriconazole (CYP2C19 substrates), tizanidine (CYP1A2 substrates), esomeprazole (Over-the-counter medications) and nicotinamide mononucleotide (Vitamin B3 forms).

Issues 11/10/2026 02:51

1. 2.13 — Audience framing dropped from lede: The at_a_glance (line 433) omits the ER Conclusion’s audience framing (“For someone focused on long-term health, P7C3 is an open research story rather than an available option”, ER line 440), so the takeaway is not framed for the longevity-oriented audience.

Fixes 11/10/2026 02:51

1. 2.13 — Audience framing added to lede: Replaced “Still an open research story” with “For longevity-focused adults, an open research story” and “human safety record” with “safety record” in at_a_glance, adding the ER Conclusion’s audience framing within 70 words.

Issues 11/10/2026 02:50

1. 2.7 — Unexplained jargon in Monitoring: marker_2_why (line 619) reads “Safety check; hepatic clearance, a rise would pause or stop use”, using the clinical term “hepatic clearance” where plain language (liver clearance) is available.

Fixes 11/10/2026 02:50

1. 2.7 — Unexplained jargon in Monitoring: Changed marker_2_why from “Safety check; hepatic clearance, a rise would pause or stop use” to “Safety check; cleared by the liver, a rise would pause or stop use”.

Issues 11/10/2026 02:47

1. 9.5 — GLP-1 drug class dropped: In Key Interactions (line 557) the ER item “glucagon-like peptide-1 agonists (semaglutide)” is reduced to bare “semaglutide”, dropping the drug class that determines whether the interaction applies, while “sulfonylureas (glipizide, glibenclamide)” keeps its class.

Fixes 11/10/2026 02:47

1. 9.5 — GLP-1 drug class restored: Changed “semaglutide” to “glucagon-like peptide-1 agonists (semaglutide)” in the Glucose-lowering drugs and supplements interaction item, matching the ER wording.

Issues 11/10/2026 02:44

1. 1.1 — Inaccurate p-tau217 gloss: Monitoring marker_5_name (QRS line 646) calls p-tau217 the “blood form of the tau protein”, whereas the ER (line 405) defines it as “a phosphorylated form of the tau protein measurable in blood”.
2. 9.5 — Parenthetical drug examples dropped: The Glucose-lowering item (QRS line 557) drops the ER’s sulfonylurea examples “glipizide, glibenclamide” (ER line 273) entirely, and the Over-the-counter item (QRS line 556) drops the ER parenthetical “(acetaminophen)” (ER line 271).

Fixes 11/10/2026 02:44

1. 1.1 — Corrected p-tau217 gloss: Changed marker_5_name from “Plasma p-tau217 (blood form of the tau protein)” to “Plasma p-tau217 (a phosphorylated form of the tau protein)”, matching the ER definition.
2. 9.5 — Restored parenthetical drug examples: Added “(glipizide, glibenclamide)” after sulfonylureas in the Glucose-lowering item and “(acetaminophen)” after paracetamol in the Over-the-counter item.

Issues 11/10/2026 02:41

1. 4.5 — Content exceeds one A4 page: The 14-item Speculative benefits list (line 531), eight Key Interactions with full example-drug lists (lines 554-561) and multi-line protocol sub-texts (lines 450, 472) together render at roughly 1.5 A4 pages instead of being condensed to the one-page budget.
2. 12.3 — Benefit items carry qualifiers: benefits_speculative (line 531) keeps context qualifiers such as “in aged and diseased brains”, “after head injury” and “after optic nerve injury” instead of just the key fact.

Fixes 11/10/2026 02:41

1. 4.5 — Condensed to one-page budget: Trimmed the Key Interactions example-drug lists to representative entries with labels kept verbatim (e.g., dropped voriconazole, tizanidine, esomeprazole, the sulfonylurea names and “oncology agents in this class”), and shortened the action_1 and action_3 protocol sub-texts.
2. 12.3 — Stripped benefit qualifiers: Removed context qualifiers from benefits_speculative (“in aged and diseased brains”, “after head injury”, “after optic nerve injury”, “aged”), keeping only the key facts.

Issues 11/10/2026 02:38

1. 1.3 — Safety record claim overstated: At a Glance (line 433) says “no human dose, safety record or approved product”, while the ER Conclusion limits this to “no safety record in people”; animal toxicology does exist.
2. 4.5 — Content exceeds one page: Long Key Interactions items (lines 554-561), a 14-item Benefits list (line 531) and verbose Protocol, marker and cadence texts (lines 450, 613, 659) push the sheet well beyond one A4 page without further condensation.

Fixes 11/10/2026 02:38

1. 1.3 — Safety record claim qualified: Changed At a Glance ending from “no human dose, safety record or approved product” to “no human dose, human safety record or approved product”, matching the ER’s “no safety record in people”.
2. 4.5 — Condensed content for page budget: Shortened action_1_sub, the Speculative benefits list, the Over-the-counter and NAMPT inhibitor interaction items, marker_1_why, marker_2_name, marker_2_why, monitoring_cadence and qualitative_item_1, keeping all items, examples and cautious qualifiers.

Issues 11/10/2026 02:35

1. 2.7 — Specialist terms on sheet: marker_2_why (line 619) reads “clearance is hepatic” and benefits_speculative (line 531) reads “neuroprotective concentrations”; both are specialist phrasing where plain equivalents exist.

Fixes 11/10/2026 02:35

1. 2.7 — Specialist terms replaced: Changed marker_2_why “clearance is hepatic” to “the liver clears the compound” and benefits_speculative “neuroprotective concentrations” to “nerve-protective concentrations”.

Issues 11/10/2026 02:32

1. 2.7 — Avoidable jargon in Benefits: The Speculative benefits list (line 531) keeps specialist terms “hippocampal neurons”, “retinal ganglion cells” and “ischaemic stroke” where plain-language equivalents exist, unlike neighbouring items that were already rephrased plainly.

Fixes 11/10/2026 02:32

1. 2.7 — Plain-language benefit terms: In the Speculative benefits list, replaced “hippocampal neurons” with “brain cells”, “ischaemic stroke” with “stroke”, and “retinal ganglion cells” with “retinal nerve cells”.

Issues 11/10/2026 02:29

1. 2.7 — Unexplained p-tau217 jargon: Monitoring marker_5_name (line 646) reads “Plasma p-tau217” with no plain-language gloss, unlike the other markers; the ER explains it as a phosphorylated form of the tau protein measurable in blood.
2. 14.2 — AST and bilirubin omitted: The ER Monitoring table pairs ALT with AST (aspartate aminotransferase) and bilirubin, but neither biomarker appears in the QRS Monitoring table (lines 611–621).

Fixes 11/10/2026 02:29

1. 2.7 — Glossed p-tau217 marker: Changed marker_5_name from “Plasma p-tau217” to “Plasma p-tau217 (blood form of the tau protein)”, following the ER’s own explanation.
2. 14.2 — Added AST and bilirubin: Changed marker_2_name to “ALT (alanine aminotransferase), paired with AST (aspartate aminotransferase) and bilirubin” and scoped the target to “ALT 7–56 U/L”, since the ER gives no range for the paired tests.

Issues 11/10/2026 02:26

1. 2.7 — Unexplained NAD⁺ acronym: Monitoring marker_1_name (line 602) reads “Blood NAD⁺ metabolite panel” with no plain-language gloss, although the ER explains NAD⁺ as the energy-transfer coenzyme (ER lines 67, 401).

Fixes 11/10/2026 02:26

1. 2.7 — Unexplained NAD⁺ acronym: Changed marker_1_name from “Blood NAD⁺ metabolite panel” to “Blood NAD⁺ (energy-transfer coenzyme) metabolite panel”, using the ER’s own gloss.