Audit: QRS - Serrapeptase for Health & Longevity

Audit conducted on 14/08/2026 14:08 using AI4L / Opus 5

Iterations

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 span traced to ER source: protocol cells to ER Therapeutic Protocol, time cells to ER Practical Considerations and Expected Benefits, gates to Key Interactions & Contraindications, tiers to Expected Benefits / Potential Risks & Side Effects, table and cadence to Monitoring Protocol & Defining Success.
1.2	Where the ER uses cautious phrasing (“not formally studied”, “None documented in human trials to date”, “theoretical concern”, “data are limited”), the QRS uses the same phrasing.	🟢	Speculative tiers carry the ER’s own speculative headings; no ER hedge is dropped or converted into a firmer statement.
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”).	🟢	“Pregnancy or breastfeeding” stays in the Contraindications gate, not the Key Interactions gate; the surgery window stays absolute.
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.	🟢	Gate content comes only from Key Interactions & Contraindications; no Benefit-Modifying Factors or Risk-Modifying Factors bullets appear anywhere in the QRS.
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, no NCT identifiers, no author names, no brand names anywhere in the QRS.
1.6	The QRS does not introduce new attributions.	🟢	No attributions of any kind present.

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.	🟢	Matches the ER’s measured, sceptical register — a real short-term anti-swelling effect inside a thin evidence base.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Concrete doses, timings, thresholds and markers give the reader something to act on while the evidence limits stay visible.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Content is stated as what trials used and what markers track, not as instructions issued to a patient.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperatives in QRS-authored content; the gates are descriptive lists of populations and agents.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No “recommended”, “should”, or “advised” in any populated span.
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	🟢	Technical terms are limited to unavoidable ones (marker names, drug classes); the At-A-Glance stays fully plain.
2.8	Information is presented in a concise and very compact manner	🟢	Tier lists are semicolon-separated headings only; gate items are single facts with their qualifiers.
2.9	It DOES NOT address the reader directly	🟢	Confirmed — no direct address.
2.10	The target audience is health- and longevity-oriented adults who are risk-aware, proactive, and actively seeking to optimize health or apply the intervention under review.	🟢	Activity-unit conversions, empty-stomach windows and a six-marker panel address exactly that reader.
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 eight-hourly empty-stomach dosing and repeat blood panels are presented without dilution.
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.	🟢	No simplification down to a general-population register.
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 longevity-specific claims (arterial plaque, biofilms, amyloid) are surfaced and correctly parked in Speculative.
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.	🟢	“anti-aging” does not occur; “age-related amyloid aggregates” follows the ER 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)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt.	🟢	Clinical register throughout the body (“gastrointestinal discomfort”, “mucociliary clearance”, “hypersensitivity reactions”).

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 headings, gate heads, tier labels and column headers byte-identical to [qrs_template].
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 template span names present; the repeatable marker_#* and qualitative_item# rows are expanded to 6 and 5 instances respectively.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Structural diff against [qrs_template] with variable payloads masked shows no change outside the metadata block, the two display:none tier spans, and the repeated monitoring/qualitative rows.

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 ER section drawn on by the QRS is empty.
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.	🟢	“Standard dose”, “Best time of day” and “Pre-existing conditions” are the ER’s own bold labels; interaction items reuse the ER’s bold interaction labels verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Monitoring marker names are verbatim from the ER biomarker table; time-cell labels are lifted from the phrasing of the ER Time to effect bullet.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji in the file; the ER’s “⚠️ Conflicted” marker on the swelling benefit is correctly not carried over.
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.	🟢	Tiered sections are reduced to bare headings, gate items to fact plus qualifier, and protocol subs to one or two clauses; no section carries elaboration beyond what other checklist items mandate.

---

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.	🟢	Single comment spanning lines 2–14, immediately after the doctype.
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 “—” at line 3, closing “—” at line 13.
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 echoed into the header or footer.
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" is quoted, correctly so because the value contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: serrapeptase_2026-0814-1145_Opus_ER.md.
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 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)	🟢	Line 6: qrs_creation_date: 2026-0814-1359.
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” — single word, no version.
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” — nickname plus version, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the actual filename 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 or 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., & for &)	🟢	Line 22: “Serrapeptase 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., & for &)	🟢	Line 417: “Serrapeptase for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “08/14/2026”, matching qrs_creation_date 2026-0814.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “Opus 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.	🟢	Header carries only the title and the template subline; the ER’s “Also known as” line is not carried over.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Four sentences condensing the ER Conclusion: what it is, what it does, what it does not, and how good the evidence is.
7.2	[at_a_glance] is no longer than 60 words	🟢	59 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause maps to a distinct Conclusion sentence (Japanese prescription origin, swelling/stiffness effect, plaque and biofilm claims, conflicted evidence base).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	“protein-cutting enzyme”, “arterial deposits”, “bacterial films” replace metalloprotease, plaque and biofilm; no acronyms present.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial names, years, sample sizes or p-values.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numeric results of any kind.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All seven items come from the ER’s “Populations who should avoid Serrapeptase” list plus its absolute surgical stop-point.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All seven ER avoid-population bullets are represented, none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Seven <li> elements inside the span, lines 542–548.
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.	🟢	“Anyone with…” stems dropped, and the ER’s rationale clause “on absence of safety data rather than observed harm” is stripped from the pregnancy item; no trailing dash 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).	🟢	Platelet threshold 100 × 10⁹/L, the 14-day/7-day surgical window, the INR target above 2.0 and the 90-day gastrointestinal-bleed window 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 uses no ranking notation in this section.
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 seven such populations and the section is populated accordingly.
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.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All six items come from the ER’s interaction bullets.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Six of the ER’s seven interaction bullets carried over; “Scheduled surgery or invasive procedures” correctly excluded because it appears in the Contraindications gate.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Six <li> elements inside the span, lines 556–561.
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 caution level, consequence, mitigation clause and the trial citation on proteolytic enzymes are stripped; only label plus drug list remains.
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).	🟢	All six named drug/supplement lists preserved in full, with the ER’s italics on Ginkgo biloba retained.
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 uses no ranking notation in this section.
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 seven interactions and the section is populated accordingly.
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.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER Protocol section	🟢	All three cells trace to the ER Therapeutic Protocol bullets.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose, timing and condition-driven duration — the three bullets that determine what is actually taken, when, and for how long; “Total daily range” and “Split versus single dosing” are folded into the relevant subs rather than displacing them.
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 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 spans populated; the activity-unit conversion, the empty-stomach window and the three indication-specific regimens are all traceable to ER bullets.

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	🟢	Post-surgical swelling, ear-nose-throat symptoms and airway mucus — the three onset windows named in the ER Time to effect bullet, with carpal tunnel folded into the third sub.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Cell 1 is the Medium-tier swelling benefit; cells 2 and 3 are the first two Low-tier benefits in ER order.
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 four 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 spans populated; “Day 3”, “Day 3–4” and “4 weeks” match the ER Practical Considerations and Expected Benefits wording.
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 a dedicated Time to effect bullet; the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All ten items are the ER’s benefit sub-headings, tier for tier.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present, lines 521–532.
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.	🟢	Bare headings only; the ER’s “⚠️ Conflicted” qualifier, magnitude figures and confidence intervals are all dropped.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses in any benefit item.
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.	🟢	The ER has no High-tier benefit; [benefits_high] carries style="display: none" at line 521 with the untouched template placeholder inside.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All nine items are the ER’s risk sub-headings, tier for tier.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present, lines 573–584.
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.	🟢	Bare headings only; the ER’s Magnitude paragraphs, case-report details and PMID links are all dropped.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses in any risk item.
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.	🟢	The ER has no High-tier risk; [risks_high] carries style="display: none" at line 573 with the untouched template placeholder inside.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Table rows reproduce the ER biomarker table’s Biomarker, Optimal Functional Range and Why Measure It? columns.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All six ER biomarkers present: hs-CRP, absolute eosinophil count, ESR, fibrinogen, INR with prothrombin time, and ALT, with targets 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.	🟢	Line 670 carries baseline, 4-week, 12-week and 6-month intervals plus the antithrombotic clotting recheck and the symptom-triggered immediate test, all from the ER’s second monitoring paragraph.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	The five items are the ER’s qualitative-marker bullets that follow the biomarker table.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All five listed: swelling/circumference, range of motion, 0–10 pain, sputum and cough, and the stop-signal symptom set.

Issues 14/08/2026 14:08

Pass rate 100.00%. No issues found.

Issues 14/08/2026 14:02

1. 4.2 / 4.3 — Invented Protocol cell label: action_3_label is “Course length” (QRS line 466), a label with no counterpart in the ER Therapeutic Protocol bullet list; the ER bullet its content is drawn from is “Pre-existing conditions:” (ER line 361).
2. 10.4 — Protocol value sourced outside Protocol section: action_3_value “5 days to 6 weeks” (QRS line 469) comes from the ER Risk Mitigation Strategies and Discontinuation & Cycling sections (ER lines 326, 366), not from the ER Therapeutic Protocol section required by this item.

Fixes 14/08/2026 14:02

1. 4.2 / 4.3 — Protocol cell label made verbatim: Changed action_3_label from the invented “Course length” to the ER’s own bullet label “Pre-existing conditions” (ER line 361).
2. 10.4 — Protocol value re-sourced from Protocol section: Replaced action_3_value “5 days to 6 weeks” with “Condition drives duration more than dose” from the ER Therapeutic Protocol bullet, and trimmed the now-duplicated lead clause from action_3_sub.