Audit: QRS - Pancragen for Health & Longevity

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

Summary

Items	Count
Total	93
Passed	85
Failed	0
N/A	8
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 cell traces to the ER: Protocol cells to ER:265/267/271, time cells to ER:316/298, benefits to ER:142/152/156, risks to ER:190/196/204/208, gates to ER:230-247, monitoring to ER:346-355, qualitative to ER:359-363.
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.	🟢	Cautious ER phrasing is carried over: “No timing comparison has been tested” (ER:271), “No adverse event has been systematically recorded in any human study” (ER:385), “No functional target is established” (ER:353).
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”).	🟢	No claim is strengthened or softened; “partially retained three weeks after the last dose” (ER:298) is rendered as “3 weeks, partial” with the qualifier intact.
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 Pancragen” list; 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.	🟢	No PMIDs, study citations, author names or NCT identifiers appear. The generic drug names in Key Interactions all appear in the ER for the same interaction (ER:230-236).
1.6	The QRS does not introduce new attributions.	🟢	No new attributions; the institute reference in action_1_sub mirrors ER:265.

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 QRS mirrors the ER’s measured, source-skeptical tone (single institute, no independent replication).
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Expert, objective and data-driven throughout, while still presenting an actionable protocol and monitoring path.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Presents evidence and observed practice; no prescriptive instruction to a patient.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No clinical advice framing; the gates and monitoring rows state facts and ranges rather than directives.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Wording presents information (“Commercial capsules are labeled at…”, “Primate work showed…”) rather than recommending or advising.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person address anywhere in the document.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Plain language is used throughout, with drug-class names retained only where 9.5 requires them.
2.8	Information is presented in a concise and very compact manner	🟢	All cells are single facts or one-to-two short sentences.
2.9	It DOES NOT address the reader directly	🟢	Confirmed — no “you” or “your” 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 is pitched at risk-aware self-directed readers: certificate-of-analysis-grade sourcing concerns, biomarker targets, course structure.
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.	🟢	Assumes willingness to run pre-course panels, course-based dosing and repeat testing.
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 written for a general-population reader; the monitoring panel and gate detail presume active engagement.
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.	🟢	Framing reflects the audience: the At-A-Glance leads with the single-institute evidence base, which is the decisive signal for this readership.
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 term “anti-aging” does not appear; the document’s own voice uses longevity framing.
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 terminology is used (“adverse event”, “intramuscularly”, “oral capsules”, “hypersensitivity”); 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 headings verified against the template: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”, “Contraindications”, “Key Interactions”, “Marker”/”Target”/”Why”, and the visible tier labels “Medium”, “Low”, “Speculative”.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 non-indexed template spans are present, plus the indexed expansions marker_1..8_(name\|target\|why) and qualitative_item_1..5; the three website=”…” spans are present and empty as in the template.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	A full diff against the template shows changes confined to variable regions and the metadata block; CSS, structure and footer are byte-identical.

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 QRS section draws on an empty ER section; the empty benefit/risk tiers are governed by 12.5 / 13.5 (display:none), not by empty-state phrasing.
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.	🟢	Protocol labels are ER bold labels verbatim: “Standard course as used by practitioners” (ER:265), “Published research dosing differs from commercial dosing” (ER:267), “Best time of day” (ER:271); time_3_label is “Effect persistence after stopping” (ER:298). Key Interactions carry the ER bold labels verbatim (ER:230-238).
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	No label is paraphrased or abbreviated. The time_1 / time_2 labels are covered by 11.4 (“meaningful content derived from the ER”), not by the verbatim-label rule, since the ER supplies no separate bold label for each.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No 🟩 / 🟥 / 🟨 or any other emoji appears; tiers are conveyed by bold labels and CSS.
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.	🟢	Every section is materially condensed against the ER: 11 Protocol bullets reduced to 3 cells, interaction bullets stripped of Severity/Consequence/Mitigation, the four-paragraph Conclusion reduced to 59 words. No section is carried over at ER length.

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.	🟢	The metadata comment spans lines 2-14 and is the first element after <!doctype html>.
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.	🟢	YAML is delimited by “—” at line 3 and line 13; the preceding “QRS — Metadata” text sits outside the 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.	🟢	The block is inside an HTML comment and is not surfaced by any rendered element.
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.	🟢	All values trimmed; the only quoted value is duration: “00:03”, which requires quoting because it contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	er_filename: pancragen_2026-0901-0120_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), matching the QRS.md version badge.
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-0901-0407 (line 6), in 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]”	🟢	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 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]”	🟢	qrs_creator_ai_fullname: Opus 5 (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 5” is nickname plus version number, with no additional qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	qrs_filename: pancragen_2026-0901-0120_Opus_QRS.html (line 9), 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 frontmatter keys; no stray whitespace or unnecessary quoting.

#	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 `&`)	🟢	Pancragen for Health & Longevity - Quick Reference Sheet (line 22), with the ampersand entity-encoded.
6.2	[header_topic] is set to the [canonical_topic] of the ER `frontmatter`, with HTML entities encoded as needed (e.g., `&` for `&`)	🟢	header_topic is “Pancragen for Health & Longevity” (line 417), matching canonical_topic in the ER frontmatter.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	header_subline_date is 09/01/2026 (line 421), the MM/DD/YYYY form of qrs_creation_date 2026-0901-0407.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	header_subline_model is “Opus 5” (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.	🟢	The header carries only the template subline; no badge, version stamp, AKA line (the ER’s alternate_names are omitted), audit date or variant marker.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER `Conclusion` section	🟢	at_a_glance condenses the ER Conclusion (ER:381-387): mechanism claim, the single human study plus animal and cell work, single-institute provenance, and the absence of systematic adverse-event recording.
7.2	[at_a_glance] is no longer than 60 words	🟢	59 tokens by word count, within the 60-word limit.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause maps to a distinct Conclusion passage: ER:381 (peptide and gene claim, the one controlled study), ER:383 (one institute that developed and licenses it), ER:385 (no adverse event systematically recorded).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms or specialist classifications; “four-amino-acid peptide” and “adjust which genes pancreatic tissue reads” are the plain-language forms used in the ER Conclusion.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial name, year or sample size appears.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No effect size, relative risk or statistic appears.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER `Key Interactions & Contraindications` section	🟢	All six items come from “Populations who should avoid Pancragen” in the ER Key Interactions & Contraindications section (ER:240-247).
8.2	[stop_items] represent the Contraindications from the ER	🟢	All six ER contraindications are represented, one-to-one.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Each item is a discrete <li> inside the stop_items span (lines 569-574).
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.	🟢	Rationale clauses are stripped: “given the complete absence of reproductive toxicity data”, “where insulin-producing cell mass is destroyed rather than aged”, “found on imaging or biopsy”, “(inactive ingredients)”. 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).	🟢	Qualifiers preserved: “at any stage”, “HbA1c below 6.5% while on insulin or a sulfonylurea”, “active or within the preceding 90 days”, “pre-cancerous pancreatic changes”.
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 contraindication bullets use no ranking notation inside parentheses.
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 section is not empty, and the ER does identify populations that should avoid the intervention, so the emptiness condition is correctly not invoked.
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 — six contraindications are listed.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER `Key Interactions & Contraindications` section	🟢	All five items come from the ER Key Interactions & Contraindications section (ER:230-238).
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All five ER interaction bullets are represented; none duplicates a contraindication.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Each item is a discrete <li> inside the caution_items span (lines 582-604).
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 are stripped from all five items, as are the ER’s mechanistic glosses (“mimicking a gut hormone that stimulates insulin release”, “making the kidney excrete glucose”, “a second insulin-releasing class”).
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 drugs are preserved for every class: glimepiride/glipizide/glibenclamide, repaglinide/nateglinide, semaglutide/liraglutide, empagliflozin/dapagliflozin, aspirin/salsalate, and the five named supplements.
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 no ranking notation inside parentheses.
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 section is not empty, and the ER does identify interactions that change how the intervention is used, so the emptiness condition is correctly not invoked.
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 — five interactions are listed.

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 section (ER:265, 267, 271).
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER `Protocol` section	🟢	The three most actionable Protocol aspects are covered: the standard course, timing of administration, and the research-versus-commercial dosing gap. The remaining bullets (half-life, split dosing, polymorphisms, sex, age, baseline biomarkers) are non-actionable or null findings.
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 Protocol section supplies more than three actionable aspects; 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.	🟢	All nine action_# fields 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	🟢	The three aspects are the human measurement interval (days to weeks, ER:316), the within-course primate change (10 days, ER:316/144), and post-course persistence (3 weeks partial, ER:298).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered from the human Medium-tier benefit outward to the primate and post-course observations.
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; 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 time_# fields carry substantive ER-derived 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 time-to-effect information (Practical Considerations, ER:316; Discontinuation & Cycling, ER:298).

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER `Expected Benefits` section	🟢	Both entries come from the ER Expected Benefits section (ER:142, 152, 156).
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	benefits_high, benefits_medium, benefits_low and benefits_speculative are all present (lines 546-559).
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.	🟢	Both entries are bare ER benefit headings; the supporting paragraphs, Magnitude blocks and citations are omitted.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content appears in either benefit entry.
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.	🟢	benefits_high and benefits_low are set to display:none (lines 546, 553); neither carries empty-state phrasing.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER `Potential Risks & Side Effects` section	🟢	Both entries come from the ER Potential Risks & Side Effects section (ER:190, 196, 204, 208).
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	risks_high, risks_medium, risks_low and risks_speculative are all present (lines 615-628).
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.	🟢	Both entries are bare ER risk headings; the Magnitude figures (7.7-14.4% purity, 2.16-8.95 EU/mg) and citations are omitted.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content appears in either risk entry.
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.	🟢	risks_high and risks_medium are set to display:none (lines 615-616); neither carries empty-state phrasing.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER `Monitoring` section	🟢	The table mirrors the ER Monitoring Protocol & Defining Success biomarker table (ER:346-355).
14.2	All measurable/quantifiable biomarkers from the `Monitoring` section are listed	🟢	All eight ER biomarker rows are present: fasting glucose, HbA1c, fasting insulin, HOMA-IR, C-peptide, amylase and lipase, eGFR and liver enzymes, hsCRP — with targets and rationales carried over unchanged.
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.	🟢	monitoring_cadence (lines 760-764) condenses the ER cadence paragraph (ER:344) plus the pre-course panel (ER:342/252); no placeholder remains.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER `Monitoring` section	🟢	All five items come from the qualitative markers listed in the ER Monitoring Protocol & Defining Success section (ER:359-363).
15.2	All subjective/qualitative biomarkers from the `Monitoring` section are listed	🟢	All five ER qualitative markers are present, one-to-one and unabridged.

Issues 01/09/2026 04:20

Pass rate 100.00%. No issues found.

Issues 01/09/2026 04:12

10.4 — Non-Protocol content in action_1_sub: The second sentence of action_1_sub (QRS line 456), “Courses end abruptly with no dose reduction step.”, is taken from the ER Discontinuation & Cycling section (“No tapering protocol”, ER line 294) rather than from the ER Therapeutic Protocol section that this item requires the action cells to be derived from.

Fixes 01/09/2026 04:12

10.4 — Non-Protocol content in action_1_sub: Replaced “Courses end abruptly with no dose reduction step.” with “following the protocols of the institute that licenses the commercial product”, so action_1_sub now draws solely on the ER Therapeutic Protocol bullet “Standard course as used by practitioners”.