Audit: QRS - sh-Polypeptide-71 for Hair Regrowth

Audit conducted on 08/07/2026 22:59 using AI4L / Opus 4.8

Summary

Items	Count
Total	91
Passed	85
Failed	0
N/A	6
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 QRS content traces to the ER (Conclusion, Protocol, Monitoring, Interactions & Contraindications, Benefits, Risks sections).
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.	🟢	QRS preserves “conflicting evidence”, “theoretical stimulation”, “unproven benefit”, “no controlled human study exists”.
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”).	🟢	Neither strengthening nor softening detected; the “(conflicting evidence)” flag on the growth-phase benefit preserves the ER’s conflicted framing.
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, Key Interactions, Benefits, Risks, and Monitoring all map to their corresponding ER 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.	🟢	QRS contains no citations, PMIDs, expert names, or NCT IDs; drug names (minoxidil, finasteride, etc.) all appear in the ER interactions section.
1.6	The QRS does not introduce new attributions.	🟢	No attributions introduced.

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.	🟢	Tone matches the ER’s cautious, objective framing.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Tone is expert yet accessible and objective.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Presents evidence rather than directives.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No advice-implying language in the QRS body.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Content is presented, not recommended.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No direct second-person address.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Plain language throughout; technical biomarker terms are confined to the Monitoring section and derive from the ER.
2.8	Information is presented in a concise and very compact manner	🟢	Highly condensed.
2.9	It DOES NOT address the reader directly	🟢	No direct reader 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 suits risk-aware, 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.	🟢	Consistent with the intended 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.	🟢	Not written for the general population.
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 the target 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.	🟢	No “anti-aging” usage in the document’s own voice.
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.	🟢	Formal terminology used; “add-on” mirrors the ER’s own wording.

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 labels and headings are present and unmodified.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	Full set of data-qrs-var spans present (header, at_a_glance, action/time sets, benefits/risks tiers, stop/caution items, markers, cadence, qualitative items).
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	No unaddressed spans appear modified.

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”	🟢	No section required empty-state text; empty benefit/risk tiers are handled per 12.5/13.5 (display:none).
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.	🟢	Qualitative labels (“Reduced shedding”, “Visible density and coverage”, “Hair quality”, “Scalp comfort”) match the ER verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Labels preserved verbatim.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji indicators present.
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 is condensed to a single page.

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 the first element after the doctype (lines 2-14).
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 — at lines 3 and 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; 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; only “duration” is quoted (contains a colon).
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	er_filename: sh_polypeptide_71_hair_2026-0708-2106_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.7.02
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-0708-2253
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” is a single word.
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” = nickname + version, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	qrs_filename: sh_polypeptide_71_hair_2026-0708-2106_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 are clean and consistent.

#	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 `&`)	🟢	Title: “sh-Polypeptide-71 for Hair Regrowth - Quick Reference Sheet”; no entities needed.
6.2	[header_topic] is set to the [canonical_topic] of the ER `frontmatter`, with HTML entities encoded as needed (e.g., `&` for `&`)	🟢	header_topic: “sh-Polypeptide-71 for Hair Regrowth”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	2026-0708 → 07/08/2026.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	header_subline_model: “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 contains only title, date, model, and template links.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER `Conclusion` section	🟢	Condenses the ER Conclusion (line 367).
7.2	[at_a_glance] is no longer than 60 words	🟢	56 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each fact traces to the Conclusion and body of the ER.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	Plain-language only (“natural body signal that widens blood vessels and calms inflammation”); no acronyms.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trials cited.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No statistics cited.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER `Key Interactions & Contraindications` section	🟢	Derived from the “Populations who should avoid it” bullet (ER line 233).
8.2	[stop_items] represent the Contraindications from the ER	🟢	All four avoid-populations represented (hypersensitivity, broken/inflamed/lesion skin, pregnancy/breastfeeding, scalp-cancer history).
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Each item is an `<li>`.
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 trailing explanatory clauses; only compound hyphenated words remain.
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).	🟢	ER contraindications carry no qualifier-type parentheticals (only rationale, stripped per 8.4).
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 contraindications contain no ranking notation.
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	🟢	Derived from the ER interactions bullets (lines 217-231).
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All interaction bullets represented; avoid-populations correctly excluded.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Each item is an `<li>`.
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.	🟢	No trailing explanatory 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 (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely).	🟢	Example drug lists preserved in parentheses for each item.
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 interactions contain no ranking notation.
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	🟢	Derived from the ER Therapeutic Protocol (line 255).
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER `Protocol` section	🟢	Dose, Frequency, and Application cover the key implementation aspects.
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	All three action 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 three sets carry meaningful ER-derived content.

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	🟢	The ER provides a single time-to-effect aspect (visible change at 3–6 months); it is captured and the remaining sets are handled per 11.3.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Only one set exists; ordering is trivially satisfied.
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.	🟢	time_2 and time_3 are empty and set to display:none.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	time_1 (Visible change / 3–6 months / consistent daily use, matches the hair cycle) is meaningful and ER-derived.
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 (3–6 months).

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER `Expected Benefits` section	🟢	Derived from the ER Expected Benefits (Speculative tier).
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four tier variables 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.	🟢	Three speculative benefits stated as key facts; the “(conflicting evidence)” flag preserves the ER’s conflicted framing required by 1.3.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No effect sizes, sample notes, or study details preserved; the only parenthetical retained is the conflict flag mandated by the ER’s “⚠️ Conflicted” designation.
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/medium/low set to display:none; speculative populated.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER `Potential Risks & Side Effects` section	🟢	Derived from the ER Potential Risks & Side Effects section.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four tier variables 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.	🟢	Low and speculative risks stated as concise key facts.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content in the risk items.
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/medium set to display:none; low and speculative populated.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER `Monitoring` section	🟢	Derived from the ER Monitoring Protocol & Defining Success section.
14.2	All measurable/quantifiable biomarkers from the `Monitoring` section are listed	🟢	Ferritin, Vitamin D, TSH, Serum zinc, DHEA-S and free testosterone — all five listed 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.	🟢	Cadence populated (photographs at 3 months, 6 months, then every 6 months; abnormal markers rechecked ~3 months).

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER `Monitoring` section	🟢	Derived from the ER “Qualitative markers of success” (lines 344-349).
15.2	All subjective/qualitative biomarkers from the `Monitoring` section are listed	🟢	Reduced shedding, Visible density and coverage, Hair quality, Scalp comfort — all four listed.

Issues 08/07/2026 22:59

Pass rate 100.00%. No issues found.