Audit: QRS - Mung Bean Extract for Health & Longevity

Audit conducted on 15/08/2026 02:10 using AI4L / Opus 5

Iterations

Summary

Items	Count
Total	93
Passed	86
Failed	0
N/A	7
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 dose, contraindication, interaction, benefit, risk, biomarker target and qualitative marker traces to a literal ER passage (ER lines 293-325, 349-353, 406, 434-454).
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.	🟢	“Claimed for the pigment extract, resting on internal bioassay only” mirrors ER line 406; “Caution, on theoretical grounds only” mirrors ER line 309.
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”).	🟢	Caution/Monitor designations and the absolute allergy contraindication are carried at the ER’s own strength.
1.4	The QRS does not relabel an ER fact under a different decision category. A “Benefit-Modifying Factor” from ER section is not surfaced as a “Caution”; a “Risk-Modifying Factor” is not surfaced as a “Side Effect”; etc.	🟢	Contraindications come from the ER’s “Populations who should avoid” list, Key Interactions from the interaction bullets, benefits/risks from their own graded 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.	🟢	The QRS contains no PMIDs, citations, expert names, NCT identifiers or brand names.
1.6	The QRS does not introduce new attributions.	🟢	No attribution appears that is not in the ER; the vendor claim is attributed exactly as the ER attributes it.

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, evidence-limited framing.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Quantified doses, targets and cadence are given without hedging or exhortation.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Presents protocols and markers descriptively.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperatives directed at a reader; gates are stated as facts.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No “recommend”, “advise”, or “should” constructions in the QRS voice.
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 appear only where precision is required in gates and biomarker rows, matching the ER.
2.8	Information is presented in a concise and very compact manner	🟢	Items are reduced to key facts; mechanistic rationale from the ER is stripped throughout.
2.9	It DOES NOT address the reader directly	🟢	Confirmed: no direct address in any span.
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.	🟢	Optimal functional ranges and a screening-first framing address 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.	🟢	Multi-marker baseline testing, IgE screening and trough monitoring are presented without softening.
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.	🟢	Content assumes willingness to test, monitor and titrate.
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.	🟢	At-A-Glance leads with the absence of human testing of the marketed form, which is the decision-relevant 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.	🟢	“Longevity” is used in the title; “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)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt.	🟢	“Oral medication”, “prescription medication”, “adverse” register maintained; 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 headings, gate headings, tier labels and column headers match the template exactly.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	Variable-name set diffed against the template: identical, with marker_# expanded to 9 rows and qualitative_item_# to 5 items.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Non-variable markup, the website=”…” spans, styles and footer disclaimer are byte-identical to the template.

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 relied 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.	🟢	Protocol labels (“Standard extract protocol”, “Protein isolate protocol”, “Whole-food alternative”) and interaction labels are carried from the ER bold labels.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Only the parenthetical example lists inside interaction labels are trimmed, which item 9.5 expressly permits; no label is renamed.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji characters present; the ER’s ⚠️ Conflicted markers were dropped rather than carried.
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 condensed to the minimum compatible with the completeness requirements of items 8.2, 9.2, 12.2, 13.2, 14.2 and 15.2.

---

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.	🟢	Opening “—” line 3, closing “—” 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 visible markup other than the required header date/model.
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:04" is quoted, which is required by its colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: mung_bean_extract_2026-0815-0002_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 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)	🟢	Line 6: qrs_creation_date: 2026-0815-0148.
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” is a single word with 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” carries no additional qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the file’s own name.
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.	🟢	Confirmed across all eleven keys.

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 &)	🟢	“Mung Bean Extract 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 &)	🟢	“Mung Bean Extract for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	08/15/2026 from 2026-0815-0148.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	“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 markup is structurally identical to the template.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Condenses ER lines 478-482: what the product is, the single human trial, the untested marketed form, and the dominant risk.
7.2	[at_a_glance] is no longer than 60 words	🟢	60 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each of the four clauses maps to a distinct sentence in the ER Conclusion.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “plant pigments”, “protein drink” and “seed-coat product” replace flavone and isolate terminology.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	Refers to “one small controlled trial” without name, year or size.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numbers of any kind appear.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	Drawn from “Populations who should avoid Mung Bean Extract”, ER lines 313-325.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All six ER avoidance populations are present, in ER order.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Six <li> elements inside the span.
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.	🟢	No dashes or trailing rationale; the ER’s “on the basis that no safety data exist” clause is stripped from the pregnancy item.
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).	🟢	“any interval post-transplant”, “neutrophils below 1,000/µL”, “over 65”, “under 5”, “absolute” and the sprout/kill-step qualifier 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.	🟢	The ER uses no ranking notation; all parentheticals are plain comma-separated lists.
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 six 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	🟢	Drawn from ER lines 293-311.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Nine of the ER’s ten interaction bullets appear; the calcineurin-inhibitor bullet is correctly omitted as it is already a contraindication.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Nine <li> elements inside the span.
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.	🟢	Each item is label plus gate level only; every ER rationale and mitigation sentence is 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).	🟢	Every drug list is retained, trimmed only of salt forms and the ER’s inline explanatory clause.
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.	🟢	No ranking notation in the ER; all lists are plain comma-separated.
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 identifies ten 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	🟢	Drawn from the ER Therapeutic Protocol bullets, lines 349-353.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Standard extract protocol, protein isolate protocol and whole-food alternative are the ER’s three dosing routes.
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 provides three distinct aspects and 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.	🟢	Doses (250-500 mg, 10-15 g, 50-100 g dry weight) and their qualifiers match the ER verbatim.

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	🟢	Six weeks for the endothelial result (ER line 406), 8-12 weeks for long-term blood sugar marker turnover (ER line 434), and the 2-3 day vendor claim (ER line 406).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Medium-graded endothelial benefit first, Low-graded glycemic second, ungraded vendor claim last.
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 exist and 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 carry ER-derived content; no placeholder 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 and the section is retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	Every listed benefit corresponds to an ER Expected Benefits heading.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present with the ER’s tier assignments preserved.
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.	🟢	Reduced to the ER headings; all Magnitude paragraphs and citations are stripped.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any benefits span.
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 grades no benefit High; [benefits_high] carries style="display: none" and no empty-state text.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All nine listed risks correspond to ER Potential Risks & Side Effects headings.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present with the ER’s tier assignments preserved.
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.	🟢	Reduced to the ER headings; Magnitude figures such as the 5-6 log increase and the ⚠️ Conflicted marker are stripped.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any risks span.
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	All four risk tiers carry at least one ER item.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Drawn from the ER Monitoring Protocol & Defining Success table, lines 436-446.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All nine ER table rows are present with matching optimal ranges.
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.	🟢	Baseline, 8-12 weeks, then every 6 months, plus the transplant-specific schedule, all from ER line 434.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Drawn from the ER’s qualitative marker list, lines 450-454.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All five ER qualitative markers are present.

Issues 15/08/2026 02:10

Pass rate 100.00%. No issues found.

Issues 15/08/2026 02:03

1. 4.5 — Sheet overflows one A4 page: Estimated rendered height is roughly twice the ~1030 px A4 print budget; the Key Interactions gate (nine items, several wrapping to three lines), the nine-row Monitoring table (six rows wrapping to two lines) and the Protocol sub-lines (up to four lines per cell) are carried at close to full ER length rather than condensed to the per-section budget.

Fixes 15/08/2026 02:03

1. 4.5 — Protocol sub-lines condensed: Trimmed action_1_sub (“taken as one or two capsules” dropped), action_2_sub and action_3_sub, and shortened time_3_sub to “resting on internal bioassay only”, removing one wrapped line from each Protocol grid row.
2. 4.5 — Contraindication items shortened: Condensed the transplant and immunocompromised items (e.g. “Solid-organ transplant recipients” to “Transplant recipients”, “neutrophil count below 1,000/µL” to “neutrophils below 1,000/µL”) and the sprout item, keeping every qualifier required by 8.5.
3. 4.5 — Key Interaction drug lists trimmed: Shortened the example drug lists in the over-the-counter, glucose-lowering-supplement and monoamine-oxidase-inhibitor items as permitted by 9.5, taking each from three wrapped lines to two without dropping any list entirely.
4. 4.5 — Monitoring cells condensed: Shortened the Why text for markers 3, 5, 6, 8 and 9, and tightened marker_7_name and marker_7_target to “Specific IgE: mung bean, soy, birch” / “Presence or absence, not a number”, collapsing six two-line table rows to one line each.
5. 4.5 — Cadence and Benefits tightened: Compressed monitoring_cadence to “Baseline, 8 to 12 weeks after starting, then every 6 months. …” and shortened three phrases in benefits_low while retaining all seven ER benefit headings.

Issues 15/08/2026 01:54

1. 9.2 — Calcineurin interaction duplicated across gates: The calcineurin-inhibitor entry appears in both decision gates — as a contraindication at line 572 (“Solid-organ transplant recipients on calcineurin inhibitors”) and again as a key interaction at line 595 (“Calcineurin inhibitors (tacrolimus, ciclosporin): Caution, with monitoring”) — but item 9.2 requires interactions already listed as Contraindications to be excluded from [caution_items].

Fixes 15/08/2026 01:54

1. 9.2 — Calcineurin interaction de-duplicated: Removed the “Calcineurin inhibitors (tacrolimus, ciclosporin): Caution, with monitoring” bullet from [caution_items], since the same interaction is already carried as a contraindication; Key Interactions now holds nine items.
2. 9.2 / 8.5 — Named drugs preserved in the gate: Added the drug examples to the surviving contraindication, which now reads “Solid-organ transplant recipients on calcineurin inhibitors (tacrolimus, ciclosporin; any interval post-transplant), unless troughs are monitored under transplant-team supervision”, so no named example drug was lost in the de-duplication.