Audit: QRS - Royal Jelly for Health & Longevity

Audit conducted on 22/09/2026 19:19 using AI4L + evidence-mcp / Opus 5

Iterations

Summary

Items Count
Total 94
Passed 85
Failed 0
N/A 9
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 protocol, gate, benefit, risk, monitoring and qualitative string traces to ER lines 301–313, 335–345, 386, 410–430, 454–456.
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. 🟢 “(as a precaution)”, “(safety data insufficient)”, “Speculative: Stimulation of hormone-sensitive conditions” mirror the ER’s hedging.
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-populations stay in Contraindications; conflicted metabolic data stay “small and inconsistent”.
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. 🟢 Gates draw only from Key Interactions & Contraindications; tiers draw only from the graded benefit/risk sections.
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, NCT IDs, author names or brands appear anywhere in the QRS.
1.6 The QRS does not introduce new attributions. 🟢 No attributions 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. 🟢 Sober, evidence-weighted register matching the ER’s conclusion.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Presents a narrow, well-defined case for use alongside an explicit safety line.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Values and cadence are described, not prescribed.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No imperatives directed at a patient; footer disclaimer retained from template.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Uses “is typical”, “most commonly”, “commonly used” rather than recommendation verbs.
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 confined to the Monitoring table, where they name the assays themselves.
2.8 Information is presented in a concise and very compact manner 🟢 Gate items are noun phrases; protocol subs are one to two short sentences.
2.9 It DOES NOT address the reader directly 🟢 Confirmed — no “you”/”your” occurrences.
2.10 The target audience is health- and longevity-oriented adults who are risk-aware, proactive, and actively seeking to optimize health or apply the intervention under review. 🟢 Functional-optimal monitoring targets and allergy screening reflect this audience.
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. 🟢 Eight-marker baseline panel and 8–12 week rechecks assume a willing audience.
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 to general-population advice.
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. 🟢 Lede states the longevity claim is untested in people — the point that matters most to this audience.
2.14 The document’s own voice frames usage in longevity terms, not “anti-aging” (e.g., “anti-aging clinics”, “anti-aging community”, “anti-aging medicine”). Proper names that contain “anti-aging” (e.g., “American Academy of Anti-Aging Medicine”) are quoted verbatim. 🟢 Uses “healthy aging” and “longevity”; “anti-aging” does not appear.
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. 🟢 “Standard oral dose”, “dietary supplement”, “allergic reactions”; route stated as oral, not lay phrasing.

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 are byte-identical to the template.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All 38 template variables present; the repeatable marker_#_* and qualitative_item_# rows are expanded to 8 and 6 instances respectively.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 website="evidence_review", website="audit", website="full_review" and the footer disclaimer are untouched.

4. Formatting

# Description Result Comments
4.1 When the source ER section is empty, the QRS uses the ER’s own empty-state phrasing verbatim. Typical phrasings are “None documented in human trials to date” and “Not formally studied” N/A No source ER section mapped into 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 oral dose”, “Competing formulations”, “Best time of day” match ER lines 335, 337, 341 verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Protocol and monitoring labels are verbatim; time-to-effect cell labels name the ER’s own aspects (“menopausal”, “inflammatory”, “metabolic”) from ER line 386.
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 glycemic benefit was correctly dropped.
4.5 The QRS is designed to render on one A4 page. Any section that has more content in the ER than fits the per-section budget is condensed by the LLM, not extended onto a second page. 🟢 Single-line tier lists, six-item gates and an eight-row monitoring table fit the one-page budget.

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, 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. 🟢 Opens at line 3, closes 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 repeated in the body.
5.4 All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. 🟢 Only duration: "00:02" is quoted, correctly, because it contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 Line 4: er_filename: royal_jelly_2026-0731-0154_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.9.22, matching the prompt version.
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-0922-1917.
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 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 ten keys; no stray whitespace or quoting.

6. Page Title & Header

# Description Result Comments
6.1 [page_title] is set to the [canonical_topic] of the ER frontmatter followed by “ - Quick Reference Sheet” (e.g., “Intervention - Quick Reference Sheet”). The [canonical_topic] is HTML-entity-encoded as needed (e.g., &amp; for &) 🟢 Line 22: “Royal Jelly 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 &) 🟢 Line 417: “Royal Jelly for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 Line 421: “09/22/2026”, matching qrs_creation_date: 2026-0922-1917.
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 holds only the title and the template’s standard subline; the ER’s “Also known as” line was not carried over.

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 “Royal jelly is a milky secretion made by young honeybees, sold as a dietary supplement and traditional tonic for vitality and healthy aging.”
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Compresses ER lines 454–456: clearest benefit, oxidative-stress support, inconsistent metabolic effects, untested longevity claim, allergy hazard.
7.3 [at_a_glance] is no longer than 70 words 🟢 Exactly 70 words.
7.4 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Descriptor from ER lines 37/390; the four verdicts from ER lines 454–456.
7.5 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms; “oxidative damage”, “blood-sugar and cholesterol” used in place of MDA/TAC/glycemic/lipid.
7.6 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial identifiers or sample sizes.
7.7 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No numbers of any kind.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All six items trace to ER line 313 (“Populations who should avoid it”).
8.2 [stop_items] represent the Contraindications from the ER 🟢 Bee-product/pollen/honey allergy, uncontrolled or moderate-to-severe asthma, anaphylaxis history, hormone-sensitive cancers, pregnancy/breastfeeding, children — complete against ER line 313.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Six <li> elements at lines 576–581.
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. 🟢 Noun phrases only; the ER’s “because of the respiratory-allergy risk” rationale was dropped.
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). 🟢 “uncontrolled or moderate-to-severe” severity class, “(as a precaution)”, “(safety data insufficient)”, “(only under medical supervision)” 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 such populations and the section is correctly 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 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 trace to ER lines 301–309.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Anticoagulant, antihypertensive, antidiabetic, OTC, bee-product and additive-supplement interactions; no overlap with the avoid-populations in the stop gate.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Six <li> elements at lines 589–600.
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. 🟢 The ER’s INR case report, vessel-relaxing mechanism and hypoglycemia rationale were all stripped.
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 exemplars retained verbatim: warfarin; lisinopril, amlodipine; metformin, glibenclamide, insulin; propolis, bee pollen, honey; coenzyme Q10, garlic, omega-3 fatty acids; berberine, cinnamon.
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 several interactions and the section is correctly 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 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 section, lines 335–345.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Dose, formulation choice and timing are the three decisions a user must make; the remaining ER bullets are population modifiers, not actions.
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 at least three distinct 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 carry ER-sourced content; no placeholders remain.

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 🟢 Symptom relief, inflammatory markers and metabolic markers — the three aspects named in ER line 386, with the metabolic subgroup detail from ER line 114.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Menopausal symptoms (Medium, strongest signal) → inflammatory markers (Medium) → metabolic markers (Low).
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 Three distinct aspects are available; 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. 🟢 “Several weeks”, “8+ weeks”, “8+ weeks” with ER-sourced subs at lines 506, 519–520, 533–534.
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 (line 386), so the section is correctly retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All ten entries map to the ER benefit headings at lines 163–221.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present at lines 545–566.
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. 🟢 Benefit headings only; the ER’s magnitude lines (0.73 SD, −4 mg/dL, 1–2 percentage points) are absent.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheticals carried over; the ER’s “⚠️ Conflicted” marker on the glycemic item was dropped.
12.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. 🟢 The ER has no High-tier benefit; benefits_high carries style="display: none" at line 545 with no empty-state text.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All six entries map to the ER risk headings at lines 243–283.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present at lines 612–625.
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. 🟢 Headings only; the ER’s case-report counts and at-risk-group notes are absent.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 “(Topical Use)” and “(Rare)” from ER lines 259 and 273 are correctly stripped.
13.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. N/A The ER populates all four risk tiers; no sub-section is empty.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Rows mirror the ER biomarker table at lines 412–421.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All eight ER markers present with targets and rationales verbatim, including “Serum IgE / allergy history — Not a numeric range”.
14.3 [monitoring_cadence] is populated with the monitoring cadence/frequency derived from the ER Monitoring section. It is not left with placeholder text or empty. 🟢 Lines 742–744 reproduce the ER’s baseline / 8–12 week / 6–12 month schedule and the 4–8 week medication caveat from ER line 410.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Derived from the ER’s “Qualitative markers of success” list, lines 425–430.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All six ER bullets present, including the allergy early-warning item verbatim.

Issues 22/09/2026 19:19

Pass rate 100.00%. No issues found.