Audit: QRS - sh-Oligopeptide-9 for Hair Regrowth

Audit conducted on 27/09/2026 22:48 using AI4L + evidence-mcp / GPT 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. 🟢 Claims trace to the ER Conclusion, Therapeutic Protocol, benefits, risks, interactions, 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. 🟢 Uncertainty remains explicit: untested benefits, uncertain safety, no validated regimen, and theoretical interaction 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”). 🟢 No unproven benefit becomes established and no avoidance gate is weakened.
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 remain in 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. 🟢 Named drugs and supplements appear in the same ER interaction discussion; no study or commercial names are added.
1.6 The QRS does not introduce new attributions. 🟢 No new attribution appears.

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 concise, cautious tone matches the ER.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Objective statements and practical documentation retain accessibility and agency.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 The sheet describes evidence and uncertainty without prescribing treatment.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No individualized clinical recommendation appears in the populated content.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Protocol limitations and documentation intervals are presented as information.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 Populated content does not address the reader directly; the fixed template footer is retained.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain explanations accompany the few necessary scientific marker names.
2.8 Information is presented in a concise and very compact manner 🟢 Compact cells, lists, and monitoring rows fit the summary purpose.
2.9 It DOES NOT address the reader directly 🟢 No second-person address occurs in variable 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. 🟢 Identity, exposure, uncertainty, and measurable outcomes serve 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. 🟢 The proposed monitoring intervals accommodate sustained documentation 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. 🟢 The content retains technical outcome measurement rather than general-population simplification.
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. 🟢 The unquantified benefit and monitoring burden remain visible.
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 framing occurs.
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. 🟢 Clinical terms such as topical, injection, and thyroid-stimulating hormone are used appropriately.

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”
🟢 Fixed headings, tier labels, and monitoring column names match the template.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 Every template data-qrs-var anchor remains present, including hidden time anchors.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 All populated variable regions are covered by checklist sections; website anchors remain unchanged.

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 unsupported empty-state text is inserted; absent tiers and time cells follow their explicit hiding rules.
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, contraindication, and qualitative labels preserve source wording; interaction dash suffixes are stripped under 9.4.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Visible labels derive from source labels or source monitoring column content.
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 CSS uses compact type, spacing, and three-column protocol cells; content is condensed in source. No rendered check performed.

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. 🟢 The 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. 🟢 The comment contains opening and closing YAML delimiter 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. 🟢 The metadata block is commented; required header values are rendered through their designated template spans.
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; the duration quotes are justified by the colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 The ER basename matches the supplied source review in content/staging.
5.6 Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” 🟢 The recorded prompt version matches 26.9.27.
5.7 Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) 🟢 The creation timestamp follows YYYY-MMDD-HHMM.
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢 The creator nickname is recorded as GPT.
5.9 The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) 🟢 GPT 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]” 🟢 The full creator name is recorded as GPT 6.
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) 🟢 The full name combines the nickname and version without qualifiers.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 The qrs_filename value matches the audited file 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 leading or trailing value whitespace or unnecessary quotes appear.

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 &) 🟢 The title is the canonical ER topic plus the required suffix.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 The header topic matches the canonical ER topic.
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] 🟢 The header model matches GPT 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. 🟢 No extra header badge, alias, or attribution is inserted.

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 🟢 The opening identifies a laboratory-produced cosmetic ingredient proposed for hair regrowth.
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 The summary covers clinical uncertainty, safety, absent regimen, identity, formulation, and outcome documentation.
7.3 [at_a_glance] is no longer than 70 words 🟢 The at-a-glance span contains 63 whitespace-delimited words.
7.4 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each fact maps to the ER Conclusion; scalp-condition uncertainty is also explicit in Expected Benefits.
7.5 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No specialist acronym or unexplained technical classification appears.
7.6 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No specific trial details occur.
7.7 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No quantitative effect or statistical result occurs.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All four avoidance populations come from Key Interactions & Contraindications.
8.2 [stop_items] represent the Contraindications from the ER 🟢 Known product allergy, pregnancy/lactation, children, and affected-site infection/wounds are retained.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Each gate item uses li markup.
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. 🟢 Only concise labels and applicable scope qualifiers 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). 🟢 Elective-use and affected-site/invasive-use scope qualifiers remain.
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 source contains no severity-ranking notation requiring 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. 🟢 The gate is populated because the ER names avoidance populations.
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 gate is not empty.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All five interaction categories derive from the ER interaction section.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Receptor blockers, topical medications, nonprescription products, supplements, and procedures are retained without contraindication duplication.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Each interaction uses li markup.
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. 🟢 Mechanisms, study details, and dash-suffix explanations are omitted.
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). 🟢 Named drug and supplement examples and immediate post-transplantation timing remain.
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 contains no ranking notation requiring 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. 🟢 The gate is populated because the ER identifies interaction and exposure concerns.
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 gate is not empty.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 The 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 🟢 Cells prioritize regimen validity, formulation-specific directions, and delivery-route non-equivalence.
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 provides at least three distinct implementation aspects.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 Every used action label, value, and subtext is meaningful and source-supported.

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 supplies no observed treatment-effect timing; no timing claim is presented.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 No unsupported benefit timing or magnitude ordering is introduced.
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. 🟢 All unused time variables are empty and enclosed in an invisible container.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 No time item is used or populated with an invented interval.
11.5 If the ER does not provide any information on time to effect, the section is removed completely from the Protocol Panel 🟢 The time section is outside the Protocol Panel and hidden, preserving required template anchors.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 The three benefit descriptors match Expected Benefits.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four benefit tier variables 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 concise benefit names appear in the visible tier.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 Study detail and noncentral-goal annotations are omitted.
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 high, medium, and low spans have display: none.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 The four risk descriptors match Potential Risks & Side Effects.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four risk tier variables 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. 🟢 Risk labels contain no added rationale, incidence, or study detail.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical risk detail appears.
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, medium, and low spans have display: none.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Markers and cadence derive from Monitoring Protocol & Defining Success.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 Hair density, shaft diameter, conditional ferritin, and conditional thyroid-stimulating hormone are all included.
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, weeks one/four, and months three/six match the proposed ER documentation intervals.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Qualitative items derive from the ER monitoring section.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 Appearance, tolerability symptoms, and shedding are all preserved.

Issues 27/09/2026 22:48

Pass rate 100.00%. No issues found.