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

Audit conducted on 27/06/2026 03:13 using AI4L / Opus 4.8

Iterations

Summary

Items Count
Total 91
Passed 87
Failed 0
N/A 4
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, 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. 🟢 Cautious framing (“no controlled study”, “no chronobiological data”, “no timeline validated”) mirrors ER.
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 strengthening or softening detected.
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. 🟢 stop_items and caution_items derive from the ER Contraindications/Interactions section; no category swaps.
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 carries no PMIDs/NCTs/expert names; only ER ingredient names (copper tripeptide, sh-Oligopeptide-2, sh-Polypeptide-1) for the same interaction fact.
1.6 The QRS does not introduce new attributions. 🟢 No new attributions 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. 🟢 Skeptical, evidence-aware tone matches the ER.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Tone is balanced and accessible.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Presents information, not directives.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No prescriptive medical advice.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Informational framing throughout.
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 used; technical terms minimal.
2.8 Information is presented in a concise and very compact manner 🟢 Compact card/table layout.
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 the risk-aware optimizer.
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 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 general-population framing.
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. 🟢 Opportunity-cost and weak-evidence framing reflects this audience.
2.14 The document’s own voice frames usage in longevity terms, not “anti-aging” … Proper names that contain “anti-aging” … are quoted verbatim. 🟢 No “anti-aging” language used.
2.15 The document’s own voice uses formal clinical and scientific terminology, not colloquial or consumer-grade language … Direct quotes from sources are exempt. 🟢 Uses “serum”, “contact dermatitis”, “microneedling”; no “pill”/”shot”/”bad reaction”.

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; Monitoring column headers. 🟢 “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”, “Contraindications”, “Key Interactions”, tier labels, and “Marker/Target/Why” all intact.
3.2 All “” from the [qrs_template] are present in the the QRS. 🟢 All template spans present, including hidden time_3 and unused tier spans.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 No stray modifications to unaddressed spans.

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. 🟢 No empty source sections requiring empty-state phrasing; unused tiers hidden 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. 🟢 Interaction/protocol labels consistent with ER.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Labels preserved.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). 🟢 No emoji indicators in the rendered QRS.
4.5 The QRS is designed to render on one A4 page. Any section with more ER content than fits is condensed by the LLM, not extended onto a second page. 🟢 Content condensed to one-page budget.

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 (lines 2-13).
5.2 Inside that HTML comment the YAML block is delimited by a line “—” opening and a line “—” closing. 🟢 YAML delimited by — (lines 3 and 12).
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 HTML comment; not rendered.
5.4 All frontmatter values are trimmed: no leading/trailing whitespace, no surrounding quotes unless required. 🟢 All values clean and unquoted.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: sh_oligopeptide_9_hair_2026-0627-0244_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]” 🟢 qrs_creation_date: 2026-0627-0244
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. 🟢 “Opus” is 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. 🟢 “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_oligopeptide_9_hair_2026-0627-0244_Opus_QRS.html
5.13 All frontmatter values are trimmed: no leading/trailing whitespace, no surrounding quotes unless required. 🟢 Values trimmed and clean.

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. 🟢 “Sh-Oligopeptide-9 for Hair Regrowth - Quick Reference Sheet”; no & to encode.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed. 🟢 “Sh-Oligopeptide-9 for Hair Regrowth”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 2026-0627-0244 → 06/27/2026.
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 line, source-AI attribution, audit date, or QRS variant marker. 🟢 Header limited to title and standard subline.

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 Conclusion faithfully.
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. 🟢 “biologically plausible”, “no controlled study of the isolated peptide”, “penetrates scalp skin poorly”, “reassuring on safety”, “cost and lost time” all map to Conclusion.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 Plain-language only (“lab-made peptide”, “resting follicles”).
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 🟢 Derived from “Populations who should avoid it”.
8.2 [stop_items] represent the Contraindications from the ER 🟢 Active scalp infection, open wounds, known allergy.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Each is a separate <li>.
8.4 Items are as concise as possible. No trailing explanations … No content after an em-dash, en-dash, or hyphen-dash … Just the key fact. 🟢 Concise; no trailing clauses.
8.5 Parenthetical qualifiers from the ER bullet … ARE preserved as part of the item, kept as concise as possible … but never dropped entirely. 🟢 No parenthetical qualifiers in the ER contraindication; nothing to preserve.
8.6 When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) … normalize the items to a plain comma-separated list. 🟢 ER uses no ranking notation; condition not triggered.
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.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Minoxidil; retinoids/acids; microneedling; additive peptides. Non-interactions (oral drugs, supplements) correctly omitted.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Each is a separate <li>.
9.4 Items are as concise as possible. No trailing explanations … No content after an em-dash, en-dash, or hyphen-dash … Just the key fact. 🟢 Concise; no trailing clauses.
9.5 Parenthetical qualifiers from the ER bullet — example drug lists, time windows … ARE preserved … never dropped entirely. 🟢 Example drugs preserved: “(tretinoin, glycolic acid)” and “(copper tripeptide, sh-Oligopeptide-2, sh-Polypeptide-1)”.
9.6 When the ER uses ranking notation inside parens … normalize the items to a plain comma-separated list. 🟢 ER uses no ranking notation; condition not triggered.
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 Therapeutic Protocol.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Standard Use, Delivery Route, Best Time of Day.
10.3 If less that three distinct actionable implementation aspects are mentioned in the ER the unused sets are left empty and made invisible. N/A Three actionable aspects are present and 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 filled from ER protocol.

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 two distinct time aspects (visible change, reassessment); both used, third hidden per 11.3.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Visible change first, reassessment second — logical 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. 🟢 time_3 set hidden via display:none, empty, no placeholder.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 Both used sets derive from ER (4–6 month minimum; reassessment at 4–6 months).
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.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Derived from the ER Speculative benefits.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four variables present.
12.3 Items are as concise as possible. No explanations, no elaborations … Just the key fact. 🟢 Speculative line is a concise three-part list.
12.4 Parenthetical content … 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 is set to “display=none”. 🟢 high/medium/low spans 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 risks section.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four variables present.
13.3 Items are as concise as possible. No explanations, no elaborations … Just the key fact. 🟢 Low and Speculative lines concise.
13.4 Parenthetical content … 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 is set to “display=none”. 🟢 high/medium spans 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 Monitoring Protocol & Defining Success.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All 5 ER biomarkers present: Ferritin, TSH, Vitamin D, Zinc, Free testosterone/DHEA-S, with matching 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. 🟢 “Baseline labs once before starting; standardized photographs at baseline, 4 weeks, 3 months, and 6 months”.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Derived from the ER qualitative markers.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 Visible density/scalp coverage, Shedding rate, Hair texture/manageability, New short regrowth — all 4 listed.

Issues 27/06/2026 03:13

Pass rate 100.00%. No issues found.