Audit: QRS - Butea monosperma for Health & Longevity

Audit conducted on 20/08/2026 17:49 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.	🟢	All 17 Low benefits, 1 Speculative benefit, 7 Low risks, 2 Speculative risks, 7 contraindications, 12 interactions, 15 biomarkers and 6 qualitative markers map one-to-one onto ER content.
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.	🟢	“No dose-finding study exists in humans for any preparation” and “No human time-course data exist” are carried verbatim.
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 and lactation remain in Contraindications, not Key Interactions; no hedge is removed in a way that alters meaning.
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 derive from the ER’s “Populations who should avoid” list; Key Interactions from the ER’s interaction bullets; no Modifying-Factor content is repurposed.
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 author names, no NCT IDs and no brand names (Banyan, Himalaya, Dabur) appear anywhere in the QRS.
1.6	The QRS does not introduce new attributions.	🟢	Institutional attributions in the ER (CSIR-CDRI, cosmetics manufacturer) are omitted rather than replaced.

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.	🟢	Measured, evidence-limited framing throughout, matching the ER.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Quantified targets and cadences alongside plain-language benefit descriptors.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	All content is declarative; no directives are issued.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No “should”, “must”, “recommend”, “consult” or equivalent appears in the document body.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Protocol cells state practice (“Split dosing is the consistent traditional practice”) rather than prescribing it.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns and no imperatives present.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms retained are biomarker names and ER-verbatim pharmacology terms; no gratuitous jargon added.
2.8	Information is presented in a concise and very compact manner	🟢	Benefits and Risks are collapsed into single tier-level run-on lines; gate items are label-only.
2.9	It DOES NOT address the reader directly	🟢	Confirmed — no direct address anywhere in the sheet.
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 biomarker ranges and a monitoring cadence assume a proactive, self-quantifying 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.	🟢	Semen analysis, bone turnover markers and a 15-marker panel presuppose willingness to undertake effortful monitoring.
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 depth and monitoring burden exclude a general-population framing.
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 foregrounds the preclinical evidence base and the reproductive harm as the decision-relevant asymmetry.
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.	🟢	“Other longevity interventions” is the only such phrasing; “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.	🟢	“gastrointestinal irritation”, “hypoglycaemic”, “progressive motility” — clinical register maintained throughout.

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 and tier labels are byte-identical to the template.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 38 template variable names present; marker_#* expanded to 15 rows and qualitative_item# to 6 items as intended.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	A structural diff against the template shows changes only inside data-qrs-var spans, the tier display:none attributes, and the metadata block.

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 drawn on by the QRS is empty; the empty High/Medium tiers are governed by items 12.5 and 13.5 instead.
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.	🟢	“Classical Ayurvedic preparations”, “Best time of day”, “Single versus split dosing” and all 12 interaction labels match the ER bold labels exactly.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Biomarker names match the ER table verbatim; protocol labels match ER bold labels verbatim.
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 correctly stripped.
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.	🟢	17 benefit subsections condensed to one line, 12 protocol bullets to 3 cells, interaction bullets to labels only; 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.	🟢	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; the descriptive text on line 2 precedes the opening delimiter.
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 entirely within an HTML comment; no duplicate rendering elsewhere.
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:03" 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]”	🟢	er_filename: butea_monosperma_2026-0825-0628_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 matches 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-0820-1740.
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” — 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]”	🟢	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” — nickname plus version, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	qrs_filename: butea_monosperma_2026-0825-0628_Opus_QRS.html 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: all nine keys clean; git_user and git_issue unquoted as required.

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 &)	🟢	“Butea monosperma for Health & Longevity - Quick Reference Sheet” (line 22).
6.2	[header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &)	🟢	“Butea monosperma for Health & Longevity” (line 417).
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	2026-0820-1740 → “08/20/2026” (line 421).
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	“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.	🟢	Header block is byte-identical to the template apart from the three variable spans.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Compresses the Conclusion’s two distinct mechanistic threads, the evidence-quality caveat, and the dominant harm.
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 of the five clauses maps to a specific sentence in the ER Conclusion (lines 548–552).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	“orange pigment”, “bark molecules”, “bone-building cells”, “laboratory dishes” — no acronyms, no specialist classifications.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial, author or year named.
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 “Populations who should avoid Butea monosperma” list (ER lines 378–392).
8.2	[stop_items] represent the Contraindications from the ER	🟢	7 ER avoid-populations → 7 stop items, complete and in ER order.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Seven discrete <li> elements inside the span (lines 573–587).
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.	🟢	Trailing rationales (“documented folk use as an abortifacient”, “given documented renal tubular injury in animals”, “in whom no dosing or safety data of any kind exist”) are all stripped.
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).	🟢	“below 15 million/mL”, “stage 3 or worse (below 60 mL/min/1.73 m²)”, “(Child-Pugh Class B or C)”, “within two weeks of scheduled surgery”, “under 18” 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 inside parentheses 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 avoid-populations and the section is correctly populated, not empty.
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 twelve items come from the ER’s interaction bullets (ER lines 354–376).
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All 12 ER interaction bullets are present; none duplicates a contraindication population.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Twelve discrete <li> elements inside the span (lines 593–618).
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 “Caution/Monitor, with… Mitigation:…” clause is stripped; the plain-language gloss “(agents that clear worn-out cells)” is correctly dropped as an explanation.
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 eleven named example-drug lists carried through verbatim.
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 inside parentheses 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 twelve interactions and the section is correctly populated, not empty.
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 (ER lines 414–426).
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose, timing and dose-splitting — the only three bullets that specify an executable action; the “No validated human dose” caveat is folded into action_1_sub.
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 three or more distinct actionable aspects, so 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 variables 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	🟢	Rodent bone 12 weeks, human urinary-stone trial 2 months, and the 8–12-week realistic window — the three concrete figures the ER gives (ER line 469).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Bone (the ER’s flagship benefit) first, then the sole human-trial endpoint, then the overall window.
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, so 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 variables carry ER-sourced content; no placeholders remain.
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 does provide time-to-effect information, so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All entries map to ER Expected Benefits subsection headings.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present (lines 543–564).
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.	🟢	Each entry is the bare benefit descriptor; no Magnitude figures or study context carried over.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in the Benefits card.
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_medium carry style="display: none" with no empty-state text; the ER records no High or Medium benefit.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All entries map to ER Potential Risks & Side Effects subsection headings.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present (lines 629–648).
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.	🟢	Each entry is the bare risk descriptor; Magnitude paragraphs and “⚠️ Conflicted” markers excluded.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in the Risks card.
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 carry style="display: none" with no empty-state text; the ER records no High or Medium risk.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Table content traces to the ER Monitoring Protocol & Defining Success biomarker table (ER lines 499–515).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All 15 ER biomarkers present, with name, target and rationale matching the ER table character-for-character.
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-week, 4/12-week, 12-week, 6-month and 12-month intervals all carried from ER line 497.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	All six items come from the ER’s “Qualitative markers worth tracking” list (ER lines 519–524).
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	6 of 6 present, with the trailing rationale clauses stripped.

Issues 20/08/2026 17:49

Pass rate 100.00%. No issues found.