Audit: QRS - Bhringaraj for Hair Growth

Audit conducted on 21/06/2026 04:33 using AI4L / Opus 4.8

Iterations

Summary

Items Count
Total 91
Passed 84
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. 🟢 All content traces to the ER (Conclusion, Protocol, Benefits, Risks, Interactions, Monitoring).
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 human trials confirm”, “remains unproven”, “potential liver toxicity” mirror ER caution.
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”). 🟢 Contraindications keep “Oral use in pregnancy or breastfeeding” without softening.
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. 🟢 Interactions/contraindications drawn from ER “Key Interactions & Contraindications”; no cross-category relabeling.
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/expert names introduced; only example drug/supplement names that appear in the ER.
1.6 The QRS does not introduce new attributions. 🟢 No new sources or attributions added.

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. 🟢 Objective, evidence-grounded tone matching the ER.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Balanced and accessible throughout.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Presents evidence, not prescriptions.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No advice-style imperatives; footer disclaimer present.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Information-presentation framing maintained.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person address.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain language with terms explained where used.
2.8 Information is presented in a concise and very compact manner 🟢 Cells and lists are terse.
2.9 It DOES NOT address the reader directly 🟢 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. 🟢 Framing fits proactive adults.
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. 🟢 Protocol assumes sustained multi-month effort.
2.12 The document is NOT written for the general population, who are unwilling to employ lifestyle and behavioral changes or follow protocols that may be inconvenient, costly, or require effort. 🟢 Not pitched to a passive general audience.
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. 🟢 Weighting reflects proactive-audience framing.
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. 🟢 No “anti-aging” usage.
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. 🟢 Uses “oral use”, “topical”, “contact dermatitis”, etc.

3. Template Integrity

# Description Result Comments
3.1 The following labels and headings on the QRS are fixed and not modified (card/section headings, gate headings, tier labels, table column headers). 🟢 All fixed headings/labels intact (“Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”, “Contraindications”, “Key Interactions”, tiers, “Marker/Target/Why”).
3.2 All “<span data-qrs-var=”NAME”>…</span>” from the [qrs_template] are present in the QRS. 🟢 All 51 template spans present.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 No unaddressed spans altered.

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 populated section relies on empty-state phrasing; empty benefit/risk tiers handled via display:none per 12.5/13.5.
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. 🟢 Tier labels and marker names match ER verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Labels faithful to ER.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emojis in the QRS.
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. 🟢 Content condensed to a single sheet.

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. 🟢 Metadata comment is first element after 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. 🟢 YAML delimited by — lines.
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. 🟢 Inside HTML comment; not rendered.
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. 🟢 Values trimmed and unquoted.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: bhringaraj_hair_2026-0621-0328_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]” 🟢 qrs_prompt_version: 26.5.18.
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-0621-0328.
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.
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” only.
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 4.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 4.8”, no qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename: bhringaraj_hair_2026-0621-0328_Opus_QRS.html.
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. 🟢 Values clean and trimmed.

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”. The [canonical_topic] is HTML-entity-encoded as needed. 🟢 “Bhringaraj for Hair Growth - Quick Reference Sheet”.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed. 🟢 “Bhringaraj for Hair Growth”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 “06/21/2026” from 2026-0621.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 “Opus 4.8”.
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 is clean; no extra content.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Distills the ER Conclusion (lines 407-409).
7.2 [at_a_glance] is no longer than 60 words 🟢 55 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Traditional tonic, preclinical anagen push, 5AR/DHT block, topical safety, unproven — all in Conclusion.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 “hormone behind common baldness” replaces DHT; no acronyms.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial citations.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No statistics.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Drawn from ER “Populations who should avoid it” (line 275).
8.2 [stop_items] represent the Contraindications from the ER 🟢 Pregnancy/breastfeeding, liver disease, young children/frail older adults (oral).
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Three <li> items.
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. 🟢 Terse; no trailing clauses.
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. 🟢 “Oral use” / “active liver disease” qualifiers preserved; nothing dropped.
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 ER uses no ranking-notation parentheticals.
8.7 If no [stop_items] are present the section is left empty N/A Stop items are present.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 From ER drug/supplement interaction bullets (lines 265-271).
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Hepatotoxic drugs, 5AR inhibitors, anti-DHT supplements; no overlap with stop_items.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Three <li> items.
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. 🟢 Concise; no trailing clauses.
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. 🟢 Example drugs/supplements preserved in parens.
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 ER uses no ranking-notation parentheticals.
9.7 If no [caution_items] are present the section is left empty N/A Caution items are present.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 From ER Therapeutic Protocol (lines 295-320).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Route, Frequency, Trial duration.
10.3 If less than 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 Three distinct actions are present.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 All three action sets populated from the ER.

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 🟢 ER provides one time-to-effect aspect (4-6 months visible change); used appropriately.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Single applicable aspect; ordering trivially satisfied.
11.3 If less than 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. 🟢 time_2/time_3 cells set to display:none and empty.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 time_1 populated from ER (line 348).
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 ER provides time-to-effect information.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 From ER Expected Benefits (lines 141-187).
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four present.
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 names only; no magnitudes/citations.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheticals carried over.
12.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> 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 set to display:none.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 From ER Potential Risks & Side Effects (lines 207-247).
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four present.
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. 🟢 Risk names only.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheticals carried over.
13.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> 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 set to display:none.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 From ER Monitoring Protocol table (lines 376-381).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 ALT, AST, Ferritin, TSH — all four ER markers present with targets.
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. 🟢 Photos every 3 months over 4-6 months; oral liver enzymes 4-8 weeks then every 3-6 months.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 From ER qualitative markers (lines 385-389).
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All five qualitative markers reproduced.

Issues 21/06/2026 04:33

Pass rate 100.00%. No issues found.

Issues 21/06/2026 04:30

  1. 12.4 — Parenthetical not stripped: benefits_low retained the parenthetical “(anagen)” in “Promotion of the hair growth phase (anagen)” (QRS line 527); per 12.4 parenthetical content must be stripped, not preserved.

Fixes 21/06/2026 04:30

  1. 12.4 — Strip parenthetical from benefit: Removed the parenthetical “(anagen)” from benefits_low, changing “Promotion of the hair growth phase (anagen)” to “Promotion of the hair growth phase”.