Audit: QRS - Salicylic Acid for Hair Regrowth

Audit conducted on 13/09/2026 00:13 using AI4L / Opus 5

Iterations

Summary

Items	Count
Total	93
Passed	83
Failed	0
N/A	10
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 populated span traces to the ER: protocol cells to ER lines 324–328, time cells to ER 200/381, benefits to ER 150–206 headings, risks to ER 228–261 headings, gates to ER 279–302, markers to the ER table at 411–418, qualitative items to ER 422–427.
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 established target” carried verbatim into marker_2/3/4 targets; “never demonstrated for salicylic acid alone” retained in time_3_sub.
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”).	🟢	Contraindication qualifiers (“beyond scalp-only strengths”, “at strengths above 3% or beyond the scalp”) are preserved rather than broadened or narrowed.
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 ER Key Interactions & Contraindications; Benefit- and Risk-Modifying Factors (ER 211–219, 266–274) are not surfaced anywhere.
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 brand names appear; the Draelos attribution in ER line 326 is correctly dropped from action_3_sub.
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.	🟢	The sceptical, evidence-bounded register of the ER Conclusion is carried through at_a_glance and time_3_sub.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Distinguishes firm effects (scale, itch) from unsupported ones (hair count) without discouraging language.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Protocol cells describe regimens used in the literature rather than issuing instructions.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperatives; all protocol and monitoring content is in descriptive or passive form.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No instances of “recommend”, “advise”, “should” or equivalent.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere in the file; ER’s “the individual’s own baseline” condensed to “own baseline”, which remains impersonal.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Retained technical terms (keratolytic, trichoscopy, eGFR, Child-Pugh) are either mandated verbatim labels under 4.2 or threshold qualifiers mandated under 8.5.
2.8	Information is presented in a concise and very compact manner	🟢	Every gate, benefit and risk item is a single short phrase; monitoring targets and rationales are one clause each.
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.	🟢	Content assumes willingness to track trichoscopy, sebum excretion and TEWL.
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.	🟢	3–5 minute dwell times, twice-to-thrice weekly schedules and sequential morning/evening regimens are presented without hedging on inconvenience.
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.	🟢	Monitoring panel lists eight instrumented markers, well beyond general-population expectations.
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 flags the commercial funding base and the untested hair claim — precisely the weighting a proactive purchaser needs.
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.	🟢	The string “anti-aging” does not occur in the file.
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.	🟢	Route and formulation terms (“shampoo”, “topical”, “scalp-only strengths”, “hydrocortisone”) are the ER’s own clinical vocabulary; no consumer-grade substitutions.

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 fourteen fixed strings match the template byte-for-byte (QRS lines 445, 489, 535, 562, 576, 595, 617, 621–623, 757 and the four tier labels).
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 template variable names are present; the repeatable marker_#_* and qualitative_item_# patterns are correctly expanded to marker_1–8 and qualitative_item_1–6.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	A full diff against the template shows only placeholder substitutions inside data-qrs-var spans, plus the frontmatter fill; no structural, CSS or markup edits.

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 to the QRS is empty; every tier, gate, protocol and monitoring source has content.
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.	🟢	action_1/2/3_label reproduce the ER bold labels “Standard shampoo regimen”, “Combination-product approach” and “Sequential keratolytic-then-anti-inflammatory approach” (ER 324, 326, 328) exactly.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Benefit and risk items reuse the ER’s own H4 headings; monitoring marker names reuse the ER biomarker table’s first column verbatim.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji code points occur in the file; the ER’s ⚠️ and ⭕️ heading markers were 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.	🟢	Every section is condensed relative to the ER — multi-paragraph ER entries reduced to single clauses, magnitudes and citations stripped — and no section is expanded beyond the template’s single-sheet layout.

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: a single comment opening immediately after <!doctype html> on line 1.
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 --- on line 3, closing --- on line 13; the descriptive line 2 precedes the opener.
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; none of its values are echoed in the header, footer or any visible span.
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, because it contains a colon; all other values are bare and trimmed.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: salicylic_acid_hair_2026-0912-2046_Opus_ER.md, matching the ER’s own filename frontmatter value.
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.11, matching the version badge at the head of 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-0913-0007, correct YYYY-MMDD-HHMM form.
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 or qualifier.
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 only, no context-window or other qualifier appended.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the file’s actual name 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 including the added git_user and git_issue; 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 21: “Salicylic Acid for Hair Regrowth - Quick Reference Sheet”; the canonical_topic contains no characters requiring entity encoding.
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: “Salicylic Acid for Hair Regrowth”, identical to ER frontmatter line 7.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “09/13/2026”, the correct MM/DD/YYYY rendering of 2026-0913-0007.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “Opus 5”, matching the frontmatter value.
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 creation-date/model subline; the ER’s “Also known as” line (ER 29) was correctly 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	🟢	Compresses all three Conclusion paragraphs (ER 449–453) into five clauses: what it does, what is firm, what the hair claim rests on, harm profile, funding base.
7.2	[at_a_glance] is no longer than 60 words	🟢	57 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	“scale remover” ← ER 449; “itch, redness, oiliness and scratching” ← ER 449; “rests on an inference … rather than on any study that tested salicylic acid by itself and counted hairs” ← ER 451; “Harms are modest and mostly local” ← ER 453; “company-funded” ← ER 453.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “keratolytic” and “seborrheic dermatitis” are avoided in favour of “scale remover” and “scalp flakes”.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial names, years, n values or p values.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numbers of any kind appear in the span.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All seven items trace to ER lines 293 and 297–302.
8.2	[stop_items] represent the Contraindications from the ER	🟢	The six “Populations who should avoid” bullets plus the absolute 48-hour procedural contraindication (ER 293) are all present, and nothing else is.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Seven discrete <li> elements inside the span (QRS 565–571).
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 of any kind in the items; the ER’s mechanistic tail “Breached skin multiplies absorption … chemical burn” (ER 293) is stripped, as is the Child-Pugh gloss from ER 300.
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).	🟢	“(eGFR below 30 mL/min/1.73 m²)”, “(Reye’s syndrome risk)”, “Child-Pugh Class B or C”, “stage 4 or worse”, “above 3%” and “within 48 hours either side” 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 inside parentheses in its contraindication bullets; thresholds are written out in words (“below 30”, “stage 4 or worse”).
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 does identify such populations (ER 295–302), and the section is correspondingly 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 seven items trace to ER lines 279–291.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Seven of the ER’s eight interaction bullets are carried; the eighth (ER 293, an absolute contraindication) is correctly routed to [stop_items] and not duplicated here.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Seven discrete <li> elements inside the span (QRS 579–585).
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 a bare agent or class name; mechanism and mitigation clauses (e.g. “displaces warfarin from blood proteins”, “separating applications by at least 12 hours”) are stripped, and the “— blood thinners” gloss after the em-dash in ER 279 is removed as required.
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 four example drug lists are preserved: (warfarin, apixaban, rivaroxaban), (ibuprofen, naproxen), (glipizide, glyburide), (benzoyl peroxide, sulfur, resorcinol, glycolic acid).
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’s interaction parentheses contain only comma-separated drug names; no ranking symbols are used.
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 eight such interactions, and the section is correspondingly 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 action sets map to ER Therapeutic Protocol bullets at lines 324, 326 and 328.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	The standard regimen, the antifungal combination format (“the format most scalp trials tested”) and the sequential hydrocortisone schedule are the three implementable regimens; the remaining bullets are pharmacokinetic or modifying notes rather than distinct regimens.
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 four distinct regimens, so no set is unused.
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 substantive ER-derived content: strengths (1.8–3%), dwell time and frequency, the four named antifungal partners, and the 3% morning / 1% hydrocortisone evening split.

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	🟢	Flaking/itch onset (ER 381), post-transplant scab clearance (ER 200) and the hair-count horizon (ER 381) are the only quantified time-to-effect statements in the ER.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Set 1 maps to the ER’s only High-tier benefit (reduction of scalp scaling and flaking); sets 2 and 3 map to Low-tier benefits, so their relative order does not breach the magnitude ordering.
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 time-to-effect aspects exist in the ER, so no set is unused.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All nine spans populated: “1–2 weeks / Stabilise by four weeks”, “10 days / begun 48–72 hours after surgery”, “3–6 months minimum / never demonstrated for salicylic acid alone”.
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 (ER 381), so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All nine benefit phrases correspond one-to-one with the ER’s H4 benefit headings at lines 150, 158, 164, 172, 178, 184, 190, 196 and 204.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present and populated at their correct tiers, matching the ER’s own tier assignments.
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 ER heading alone; all Magnitude paragraphs, percentages, p values and funding notes are stripped.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses remain 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.	N/A	All four tiers have at least one ER benefit, so no span needs hiding.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All five risk phrases correspond to the ER’s H4 risk headings at lines 228, 236, 244, 251 and 259.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present and populated at their ER-assigned tiers.
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 heading; the odds ratio, confidence interval and p value from ER 232 and the case-report framing from ER 246 are stripped.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	The ER’s “(Salicylism)” parenthetical at line 244 is correctly removed; no parentheses remain.
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 tiers have at least one ER risk, so no span needs hiding.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	All marker names, targets and rationales come from the ER biomarker table at lines 411–418.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All eight ER biomarkers are present in ER order: Adherent Scalp Flaking Score, hair density, hair shaft diameter, sebum excretion rate, transepidermal water loss, scalp surface pH, serum salicylate, eGFR.
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.	🟢	Populated from ER line 407: 2 and 4 weeks, then 3-monthly; imaging no sooner than 6 months; serum salicylate only on symptoms.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	All six items come from the qualitative marker list at ER lines 422–427.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All six ER qualitative markers are present, in ER order and effectively verbatim.

Issues 13/09/2026 00:13

Pass rate 100.00%. No issues found.