Audit: QRS - Selank for Health & Longevity
Audit conducted on 06/08/2026 18:18 using AI4L / Opus 5
Summary
| Items | Count |
|---|---|
| Total | 91 |
| Passed | 82 |
| Failed | 0 |
| N/A | 9 |
| 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 protocol value, gate item, tier item, marker row, and qualitative item traces to a specific ER passage (ER lines 340-348, 316-336, 374-384, 427, 455-476). |
| 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 preserved, e.g. time_2_sub “Placed in this window by practitioner reports rather than trial data” and time_3_sub “Where they occur; from practitioner reports”. |
| 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”). | 🟢 | Contraindications remain contraindications and interactions remain interactions; no upgrade or downgrade of any ER statement found. |
| 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 come only from the ER’s “Populations for whom Selank is contraindicated” list; interactions only from the ER interaction bullets; no modifying factor is repurposed. |
| 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, citations, expert names or NCT IDs in the QRS; all drug names in the gates are taken from the same ER bullets. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | The only attributions (“practitioner reports”) mirror the ER’s own wording in the Practical Considerations time-to-effect bullet. |
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. | 🟢 | Neutral, sceptical-but-constructive register of the ER is retained throughout. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Tiered benefits/risks plus concrete markers and targets give an objective, actionable read. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Content is presented as evidence and observed practice, not as instruction. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No prescriptive verbs in the QRS’s own voice; monitoring content is descriptive. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No “recommended”, “should”, or “advised” formulations in any variable region. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | All variable content is third person; no second-person address. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms retained are load-bearing decision qualifiers (e.g. Child-Pugh class, eGFR threshold); nothing gratuitous. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Gate items, tier items, and marker cells are reduced to key facts without elaboration. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed across at-a-glance, protocol, gates, tiers, monitoring, and qualitative sections. |
| 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. | 🟢 | Sourcing/quality risk, biomarker panel, and cycling framing address exactly this reader. |
| 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. | 🟢 | An 11-marker panel and weekly symptom scoring presume high willingness to invest 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. | 🟢 | No general-population simplification; content assumes an engaged, self-directed reader. |
| 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. | 🟢 | High risk tier leads with supply-chain and long-term-data gaps, which is the decisive weighting for this 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. | 🟢 | The string “anti-aging” does not occur anywhere in the QRS. |
| 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 register throughout (“subcutaneous use”, “injection-site reactions”, “nasal solution”). |
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 headings verified verbatim (lines 446, 492, 539, 637, 669, 866, 568, 599, 673-675) and tier labels intact. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | 73 data-qrs-var spans present and internally complete: header (4), at_a_glance, action_1-3 × 3, time_1-3 × 3, benefits × 4, stop/caution items, risks × 4, marker_1-11 × 3, monitoring_cadence, qualitative_item_1-6. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | The website-scoped spans (evidence_review, audit, full_review) and the footer disclaimer are untouched. |
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 that feeds the QRS is empty; the empty High benefit tier is governed by item 12.5 instead. |
| 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-3 labels reuse the ER Protocol bold labels verbatim (“Standard registered protocol”, “Single versus split dosing”, “Best time of day”); qualitative items reuse the ER bold labels. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Marker names and qualitative labels match the ER monitoring table and qualitative bullet labels exactly. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji anywhere in the QRS; tiering is carried by bold labels and CSS palettes. |
| 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 to bare facts (explanations, mechanisms, and mitigations stripped from gates; magnitudes stripped from tiers; context/notes column dropped from the marker table). |
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. | 🟢 | Comment opens at line 2, immediately after the doctype at 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 “—” at line 3, closing “—” at line 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; no metadata value is echoed into the body except the sanctioned header date and model. |
| 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:05" is quoted, correctly, because it contains a colon. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Line 4: er_filename: selank_2026-0806-1431_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]” | 🟢 | Line 5: qrs_prompt_version: 26.7.02, matching 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-0806-1759. |
| 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” is a single word without 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” carries no extra qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9 matches the actual file: selank_2026-0806-1431_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. | 🟢 | Re-verified across all eleven keys; 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 22: “Selank for Health & Longevity - Quick Reference Sheet”, matching ER canonical_topic with the ampersand encoded. |
| 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: “Selank for Health & Longevity”. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: “08/06/2026”, correct for creation date 2026-0806-1759. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Line 425: “Opus 5”. |
| 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 and the template subline; the ER’s “Also known as” line was 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 |
🟢 | Condenses ER Conclusion paragraphs 1 and 2 (lines 504-506) into what the compound is, what it reliably does, what is thin, and what is missing. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | Word count is exactly 60. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Each clause maps to ER lines 504 and 506; no unsupported assertion. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms; “immune-signalling peptide”, “drowsiness”, “memory dulling” are plain-language renderings. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial names, years, or sample sizes appear. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No numeric effect data of any kind. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All nine items come from the ER’s “Populations for whom Selank is contraindicated” list (ER lines 340-348). |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | Nine ER contraindications, nine QRS items, one-to-one and in ER order. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Each item is its own <li> inside the stop_items span (lines 571-594). |
| 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. | 🟢 | Rationale clauses stripped (“on grounds of complete absence of reproductive safety data”, “given the immune-activating tuftsin core”, “where clearance of peptide fragments has never been characterised”); no dash-trailing content remains. |
| 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). | 🟢 | “first five years”, “Child-Pugh Class B or C”, “below 30 mL/min/1.73 m²”, “100,000 per microlitre”, “within 12 months”, “within 90 days” 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 contraindication list uses no ranking notation inside parentheses. |
| 8.7 | If no [stop_items] are present the section is left empty | N/A | Nine stop_items are present. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All eleven items map to the ER interaction bullets (ER lines 316-336). |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | Anticoagulants are correctly dropped from the interaction list because therapeutic anticoagulation is already a contraindication; the antiplatelet component is retained. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Each item is its own <li> inside the caution_items span (lines 602-627). |
| 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. | 🟢 | Caution/Monitor/Avoid verdicts, clinical-consequence sentences, and mitigation sentences are all stripped; only the agent class remains. |
| 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 example drugs retained for benzodiazepines, antihistamines, decongestants and corticosteroids, opioids and antagonists, supplements, immunosuppressants, and stacked peptides. |
| 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 interaction bullets use no ranking notation inside parentheses. |
| 9.7 | If no [caution_items] are present the section is left empty | N/A | Eleven caution_items are present. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Protocol section |
🟢 | All three cells derive from the ER Therapeutic Protocol bullets (ER lines 374, 380, 384). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Dose/route/course, split dosing, and timing are the three decisions a reader must make first. |
| 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 well more than three actionable aspects; all three 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 nine action fields carry substantive ER-derived content; no placeholders remain. |
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 | 🟢 | Anxiety reduction, calm and mental clarity, and cognitive effects — the three windows named in ER line 427. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Anxiety reduction (Medium tier) first, then the two lower-tier/practitioner-reported effects. |
| 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 | The ER names three distinct time-to-effect aspects; all three sets are used. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | All nine time fields are populated from ER line 427, including the rapid-responder detail. |
| 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 an explicit time-to-effect bullet, so the section is correctly retained. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | All twelve benefit entries map to ER Expected Benefits headings (ER lines 150-218). |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans present (lines 541-561). |
| 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 sub-heading reduced to a phrase; no magnitude, trial, or mechanism text carried over. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses appear anywhere in the four benefit spans. |
| 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. | 🟢 | The ER High tier holds no benefit, and benefits_high is empty with style="display: none" (line 541). |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | All nine risk entries map to ER Potential Risks & Side Effects headings (ER lines 242-296). |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans present and populated (lines 639-663). |
| 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 ER sub-heading reduced to a phrase; the FDA framing, magnitudes, and mechanism paragraphs are dropped. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses appear anywhere in the four risk spans. |
| 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 ER risk tiers contain items, so no tier requires hiding. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Marker names, targets, and rationales are taken from the ER Monitoring Protocol table (ER lines 455-467). |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All eleven ER table rows are present in the same order, with targets reproduced exactly (GAD-7 through morning serum cortisol). |
| 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. |
🟢 | Line 856 reproduces the ER baseline plus day 14-30, 3-month, 6-12-month, and weekly symptom-score cadence (ER lines 449-451). |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | All six items come from the ER “Qualitative markers” bullets (ER lines 471-476). |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | Anxious arousal, sleep quality, cognitive clarity, energy and drive, emotional range, and local tolerance — six of six, with ER bold labels intact. |
Issues 06/08/2026 18:18
Pass rate 100.00%. No issues found.
Issues 06/08/2026 18:10
- 1.3 — Anxiety claim broadened beyond ER scope: [at_a_glance] (line 435) reads “Its most consistently reported effect is reduced anxiety”, dropping the ER Conclusion’s population restriction “in people with diagnosed anxiety conditions” (ER line 504), which presents a scoped trial finding as a general effect.
Fixes 06/08/2026 18:10
- 1.3 — At-a-glance anxiety scope restored: Reworded [at_a_glance] from “Its most consistently reported effect is reduced anxiety” to “Its most consistently reported effect is symptom reduction in people with diagnosed anxiety”, restoring the population restriction the ER Conclusion states; “and long-term human data are absent” was shortened to “; long-term human data are absent” to keep the section within the 60-word limit.