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

Audit conducted on 27/09/2026 20:36 using AI4L + evidence-mcp / ChatGPT 6

Iterations

Summary

Items Count
Total 94
Passed 89
Failed 0
N/A 5
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. 🟢 Content maps to the ER Conclusion, Therapeutic Protocol, benefits, risks, precautions, and monitoring 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. 🟢 Unresolved standalone efficacy, unknown serum timing, indirect transplant evidence, and unvalidated dosing remain qualified.
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”). 🟢 Add-on benefit is distinguished from standalone efficacy; precautionary populations remain avoidance gates.
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. 🟢 Benefits, risks, contraindications, interactions, and monitoring retain their source categories.
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. 🟢 DermaHeal Stem C’Rum HL occurs in the ER for the same injected schedule and concentration.
1.6 The QRS does not introduce new attributions. 🟢 No new expert, study, or institutional attribution is 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. 🟢 Retains the ER’s evidence-focused, uncertainty-aware tone.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Balances supported add-on benefit with unresolved efficacy and safety.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Describes studied approaches and measurements without prescribing individual treatment.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Protocol is explicitly studied or unvalidated; cadence is illustrative.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Presents findings, exposure schedules, and monitoring information.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 Variable content does not address the reader; fixed disclaimer is preserved.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain descriptions are used and activity units are written out.
2.8 Information is presented in a concise and very compact manner 🟢 Compact protocol cells, tier lists, and monitoring rows.
2.9 It DOES NOT address the reader directly 🟢 No direct reader address in authored content.
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. 🟢 Distinguishes hair outcomes from health and longevity benefit.
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. 🟢 Includes repeated sessions, sustained topical use, monitoring, and treatment burden.
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. 🟢 Frames sustained intervention assessment for engaged adults.
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. 🟢 Presents added benefit alongside procedure burden and product uncertainty.
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. 🟢 Uses longevity terminology; no anti-aging framing.
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. 🟢 Uses injection, formulation, inflammation, and other appropriate scientific terms.

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 required section, gate, tier, and monitoring headings are preserved.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 Source comparison found every template data-qrs-var anchor present.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 No template variable outside the checklist was changed.

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” 🟢 Populated source sections are condensed; absent tiers use the expressly required hidden spans.
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 and qualitative labels preserve source bold labels; gate dash suffixes follow sections 8–9.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Labels are taken from source bullet labels, benefit headings, or monitoring rows.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji indicators occur 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. 🟢 A4 print rules, compact spacing, three-column protocol cells, and short content support the one-page design; assessed as HTML source.

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 immediately follows 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. 🟢 One opening and one closing YAML delimiter inside that comment.
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. 🟢 Metadata remains in the invisible comment.
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 are trimmed; duration has a colon and is quoted.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename matches the named source ER basename.
5.6 Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” 🟢 Version 26.9.27 matches 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) 🟢 Creation timestamp 2026-0927-1834 uses the specified format.
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 is present.
5.9 The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) 🟢 ChatGPT is a single word without 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 is present.
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) 🟢 ChatGPT 6 contains model name and version only.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename matches the target basename.
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. 🟢 No surrounding whitespace or unnecessary quotation marks.

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., &amp; for &) 🟢 Canonical topic and required title suffix match exactly.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 Header matches sh-Polypeptide-1 for Hair Regrowth.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 09/27/2026 matches the creation date.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Header model matches ChatGPT 6.
6.5 No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. 🟢 Only the template header content is present.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] opens by saying what the intervention is — its kind (e.g., dietary supplement, prescription medication, peptide, plant, procedure, practice) — and what it is used for, in plain language, before any verdict on the evidence 🟢 Opening identifies a growth-factor protein and scalp/hair-regrowth use.
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Condenses the Conclusion’s add-on signal, uncertain serum efficacy, delivery issues, safety, and durability.
7.3 [at_a_glance] is no longer than 70 words 🟢 63 whitespace-separated words.
7.4 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Every fact maps to Conclusion passages; scalp-product use is also established in Motivation.
7.5 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No specialist acronyms or technical classifications in the summary.
7.6 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial identifiers, dates, samples, or p-values.
7.7 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No effect sizes, relative risks, or statistical results.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All four gates come from Populations who should avoid in Key Interactions & Contraindications.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All four avoidance populations/scenarios are retained.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Each contraindication uses li tags.
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. 🟢 Contains only concise gate facts without explanations or dash suffixes.
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). 🟢 Under-18 threshold and intended-site qualifiers are 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. 🟢 No source ranking notation requires normalization.
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. 🟢 Section is populated because the ER identifies avoidance scenarios.
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 Section is populated; the empty-section condition does not apply.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All interaction entries come from Key Interactions & Contraindications.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Minoxidil, clot-prevention medicines, irritating topicals, and growth-factor procedures are retained; unestablished supplement interactions are not asserted.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Each interaction uses li tags.
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. 🟢 Entries contain names and decision-relevant examples without trailing explanations.
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). 🟢 Warfarin, apixaban, aspirin, clopidogrel, tretinoin, and salicylic acid are retained; skin-puncture context is explicit.
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 source ranking notation requires normalization.
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. 🟢 Section is populated because relevant exposures are described.
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 Section is populated; the empty-section condition does not apply.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 All three action cells derive from Therapeutic Protocol.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Covers absent standalone standard and the studied topical and injected approaches.
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 At least three distinct implementation aspects are available and used.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 Each label, value, and subtext preserves source dosing, scheduling, and limitations.

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 🟢 Covers regrowth assessment, transplant survival follow-up, and scalp symptom assessment.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Primary regrowth precedes the two low-tier benefits, in source order.
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 timed outcome assessments are available and used.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 Three/six months, twelve months, and eight sessions match the ER and retain context.
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/assessment information; removal condition does not apply.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Benefit descriptors and tiers match Expected Benefits.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four required benefit variable spans remain 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. 🟢 Only benefit descriptors appear, without study details or numerical results.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical study content is carried into benefit tiers.
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. 🟢 Empty Medium and Speculative tiers use display: none.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Risk descriptors and tiers match Potential Risks & Side Effects.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four required risk variable spans remain 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. 🟢 Only risk descriptors appear, without rates, study details, or mechanistic explanations.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical detail is carried into risk tiers.
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. 🟢 Empty High tier uses display: none.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Rows and cadence derive from Monitoring Protocol & Defining Success.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All five source table markers are included with conditional laboratory indications.
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, two-to-four-week tolerability, three/six-month counts, and symptom-triggered checks are retained as illustrative.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Qualitative items derive from the monitoring section.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 Coverage, shedding/comfort, and treatment burden all appear.

Issues 27/09/2026 20:36

Pass rate 100.00%. No issues found.