Audit: QRS - Selenium for Health & Longevity

Audit conducted on 13/08/2026 08:30 using AI4L / Opus 5

Iterations

Summary

Items	Count
Total	93
Passed	83
Failed	0
N/A	10
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.	🟢	Spot-checked every populated span against the ER: protocol values (ER lines 340, 350, 354, 362), tier headings (ER 146-212, 234-278), contraindications (ER 316-320), interactions (ER 298-312), biomarker rows (ER 428-435), qualitative markers (ER 439-443). All literally supported.
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.	🟢	No cautious ER phrasing is dropped or hardened; e.g. marker_7_target keeps “As low as achievable; no established target” (ER line 434).
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”).	🟢	Thresholds and directionality preserved, e.g. action_2_sub keeps both “above 122 µg/L predicts harm without benefit” and “below 90 µg/L” (ER line 362).
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 map to the ER “Populations who should avoid Selenium” list; caution_items map to the ER interaction bullets; no modifying factor is promoted to a gate.
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, author names, NCT identifiers, or brand names appear anywhere in the QRS.
1.6	The QRS does not introduce new attributions.	🟢	No attributions are introduced; the sheet carries no named source beyond the template header line.

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.	🟢	Register matches the ER: measured, status-first, U-shaped-curve framing.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Expert but accessible; the at-a-glance and protocol cells give actionable numbers without hedging into vagueness.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Presents thresholds and evidence tiers rather than issuing instructions.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperative clinical directives; the footer disclaimer is the unmodified template text.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Content is stated as evidence (“Starting above 122 µg/L predicts harm without benefit”), not as advice.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person address anywhere in the file (zero occurrences of “you”/”your”).
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms are used only where the ER uses them, and expanded forms are kept (e.g. “Glycated haemoglobin (HbA1c)”).
2.8	Information is presented in a concise and very compact manner	🟢	Every cell is a single condensed clause; benefit and risk tiers are semicolon-joined one-liners.
2.9	It DOES NOT address the reader directly	🟢	Confirmed: no direct reader address in any span.
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.	🟢	Content assumes a reader who will test plasma selenium before supplementing and titrate to a biomarker.
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.	🟢	Presents repeat biomarker testing, speciation-verified products, and defined-course dosing without softening for convenience.
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 pitched at the general population; the monitoring table alone assumes willingness to order specialist assays.
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 status-dependent inversion (benefit when low, harm when replete) is the organising frame, which is exactly the distinction this audience needs.
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 occurrence of “anti-aging” in the document.
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 throughout (“selenosis”, “high-grade prostate cancer”, “supra-nutritional intakes”); at-a-glance plain wording is taken verbatim from the ER Conclusion.

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 headings verified in source: “Protocol” (line 446), “Time to effect” (490), “Benefits” (538), “Risk & Side Effects” (615), “Monitoring” (646), “Qualitative Assessment” (781), “Contraindications” (571), “Key Interactions” (589), tier labels High/Medium/Low/Speculative, and Marker/Target/Why (650-652).
3.2	All “<span data-qrs-var=”NAME”>…</span>” from the [qrs_template] are present in the the QRS.	🟢	63 data-qrs-var spans present with no duplicates: header set, at_a_glance, action_1-3, time_1-3, four benefit and four risk tiers, stop_items, caution_items, marker_1-8, monitoring_cadence, qualitative_item_1-5.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	No span outside the checklist scope was altered; template comments, CSS, and the website=”…” spans are intact.

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 used by the QRS is empty, so no empty-state phrasing is required.
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.	🟢	ER bold labels reused verbatim: “Standard dose”, “Baseline biomarker targets”, “Best time of day” (ER 340, 362, 350) and all eight interaction labels (ER 298-312).
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	No label is paraphrased or abbreviated; the time-to-effect cells take their wording from the ER text they summarise, since the ER supplies no per-item bold label there.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	Scan of the file returns no 🟩/🟥/🟨 or any other emoji indicator; tiers are conveyed by bold labels and CSS only.
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.	🟢	Each section is condensed to its per-section budget: single-line tier summaries, gates trimmed to the key fact, monitoring “Why” column held to one clause.

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 opens on line 2, immediately after <!doctype html>, ahead of any other comment or markup.
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 “—” on line 3 and line 13; the preceding title text sits outside the block.
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.	🟢	Wrapped in an HTML comment and not echoed by any visible element.
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.	🟢	All values trimmed; only duration: “00:03” is quoted, which YAML requires because the value contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	er_filename: selenium_2026-0813-0725_Opus_ER.md (line 4), matching the source ER.
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 (line 5), matching this guideline version.
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-0813-0817 (line 6), in YYYY-MMDD-HHMM form.
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 (line 7).
5.9	The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT)	🟢	Single word, no 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]”	🟢	qrs_creator_ai_fullname: Opus 5 (line 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)	🟢	Nickname plus version number only, no additional qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	qrs_filename: selenium_2026-0813-0725_Opus_QRS.html (line 9), matching the file on disk.
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: no stray whitespace and no unnecessary quoting in any frontmatter value.

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 &)	🟢	Title reads “Selenium for Health & Longevity - Quick Reference Sheet” (line 22), with the ampersand entity-encoded.
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 is “Selenium for Health & Longevity” (line 417), the ER canonical_topic entity-encoded.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	header_subline_date is 08/13/2026 (line 421), the MM/DD/YYYY form of qrs_creation_date 2026-0813.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	header_subline_model is “Opus 5” (line 425), matching qrs_creator_ai_fullname.
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 carries only the title and the template subline; no badge, version stamp, AKA line, or audit date.

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 (ER lines 467-473) into the decision that drives use: status determines whether selenium helps or harms.
7.2	[at_a_glance] is no longer than 60 words	🟢	59 words, within the 60-word ceiling.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause traces to a distinct Conclusion passage: ER 467 (trace mineral), 469 (low intake case), 471 (inversion, diabetes, prostate, hair/nail/skin), 473 (body levels carry the signal).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms and no specialist classifications; “heart muscle disease” is used instead of cardiomyopathy, in the ER Conclusion’s own plain wording.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial names, years, sample sizes, or p-values.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No effect sizes, risk ratios, or confidence intervals; the only numbers in the sheet sit in the protocol and monitoring cells.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	Drawn from the ER “Key Interactions & Contraindications” section, specifically its “Populations who should avoid Selenium” list (ER lines 314-320).
8.2	[stop_items] represent the Contraindications from the ER	🟢	All five ER avoid-populations are represented, one per item, in ER order.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Five discrete <li> elements inside the stop_items span (lines 574-584).
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.	🟢	Trailing rationale stripped, e.g. ER “in whom trial evidence shows harm and no benefit” and “a measure of kidney filtering capacity” are both removed; no dash-trailing clauses 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).	🟢	Qualifiers retained: “(Gleason score ≥7)”, “(glycated haemoglobin 5.7–6.4%)”, “<30 mL/min/1.73 m²”, “top two quintiles”, “400 µg”, and “absent a documented deficiency”.
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 uses no ranking notation inside parentheses in this section.
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 section is populated, and the ER does identify populations that should avoid the intervention, so the emptiness condition never applies.
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. <!– empty: ER names no population that should avoid the intervention –>	N/A	The section is not empty, so no explanatory HTML comment is required.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	Drawn from the ER “Key Interactions & Contraindications” bullets (ER lines 298-312).
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All eight ER interaction bullets are present and none duplicates a contraindication.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Eight discrete <li> elements inside the caution_items span (lines 592-605).
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.	🟢	Each item is the ER bold label only; the ER Caution/Monitor grading, mechanism sentence, and “Mitigation:” clause are all stripped.
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 preserved verbatim, e.g. “(simvastatin, atorvastatin with extended-release niacin)”, “(amiodarone, contrast media)”, “(cisplatin, carboplatin)”, “(≥1 g taken together)”.
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 uses no ranking notation inside parentheses in this section.
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 section is populated, and the ER does identify interactions that change how selenium is used, so the emptiness condition never applies.
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. <!– empty: ER names no interaction that changes how the intervention is used –>	N/A	The section is not empty, so no explanatory HTML comment is required.

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” section (ER lines 338-364).
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose, baseline biomarker target, and administration timing are the three load-bearing implementation decisions for an intervention whose harm is status-dependent.
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 describes well over three actionable implementation aspects, so no set is unused.
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 populated from ER lines 340, 354 (once daily is sufficient), 362, and 350.

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	🟢	Enzyme repletion, thyroid antibodies, and mild thyroid eye disease are the only three time-to-effect windows the ER quantifies (ER lines 398, 160).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	All three map to High-tier benefits and appear in the ER’s own High-tier order: deficiency correction, thyroid antibodies, thyroid eye disease (ER 146-162).
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 time-to-effect aspects exist in the ER, so no set is unused.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All nine time fields populated; values 3–6 weeks, 3–6 months, and 6 months all trace to ER lines 398 and 160.
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 does provide time-to-effect information, so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	Derived from the ER “Expected Benefits” section (ER lines 140-212).
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four tier spans present and populated (lines 540-564).
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 tier is a semicolon-joined list of ER benefit headings with no magnitudes, mechanisms, or citations carried over.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content survives; the ER “⚠️ Conflicted” marker on the cancer-incidence heading is also dropped.
12.5	If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing.	N/A	All four benefit tiers contain items in the ER, so no span needs hiding.

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 (ER lines 228-278).
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four tier spans present and populated (lines 617-640).
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 tier is a semicolon-joined list of ER risk headings; hazard ratios, trial names, and mechanisms are all omitted.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content survives; the ER “⚠️ Conflicted” marker on the melanoma heading is dropped.
13.5	If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing.	N/A	All four risk tiers contain items in the ER, so no span needs hiding.

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 (ER lines 422-435).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All eight ER biomarker rows are present in ER order, with targets and rationale reproduced verbatim (ER lines 428-435).
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.	🟢	monitoring_cadence carries the full ER cadence: selenium at baseline, 3 and 12 months then annually, thyroid markers at 3 and 6 months, glycaemic markers annually (ER line 424).

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Derived from the qualitative marker list in the ER “Monitoring Protocol & Defining Success” section (ER lines 437-443).
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All five ER qualitative markers are listed: nail appearance, hair, breath and taste, energy and cold tolerance, gastrointestinal comfort.

Issues 13/08/2026 08:30

Pass rate 100.00%. No issues found.

Issues 13/08/2026 08:23

1. 11.2 — Time-to-effect order wrong: The Time to Effect cells run thyroid antibodies → thyroid eye disease → enzyme repletion (lines 494–532), but “Enzyme repletion” maps to the ER’s leading High-tier benefit “Correction of Deficiency and Full Selenoprotein Expression”, which the ER calls the one mechanistically certain benefit, so it must be ordered first.
2. 1.3 — “biochemical” qualifier dropped: action_2_sub (lines 470–471) reads “below 90 µg/L predicts the largest response”, strengthening the ER’s “predicts the largest biochemical response” (ER line 362) from a biomarker claim into an unqualified one.

Fixes 13/08/2026 08:23

1. 11.2 — Time-to-effect reordered by benefit: Reordered the Time to Effect cells so “Enzyme repletion” (3–6 weeks) leads, followed by “Thyroid antibodies” (3–6 months) and “Mild thyroid eye disease” (6 months), matching the ER’s High-tier benefit ordering.
2. 1.3 — Restored “biochemical” qualifier: Changed action_2_sub from “predicts the largest response” to “predicts the largest biochemical response”, matching the ER wording.