Audit: QRS - Copper for Health & Longevity

Audit conducted on 20/09/2026 04:00 using AI4L / Opus 5

Iterations

Summary

Items	Count
Total	93
Passed	85
Failed	0
N/A	8
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 cell, gate item, tier item, biomarker row and qualitative item traces to a verbatim or near-verbatim ER passage.
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.	🟢	“trials show no gain”, “tracks with”, “the presence of Alzheimer’s disease” mirror the ER Conclusion’s hedged wording.
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”).	🟢	Association framing preserved; absolute contraindications remain absolute (copper-chelating drugs placed in Contraindications).
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.	🟢	Gates draw only on Key Interactions & Contraindications; Benefits/Risks draw only on their own ER sections.
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, NCT IDs, author names or brand names appear anywhere in the QRS.
1.6	The QRS does not introduce new attributions.	🟢	The only attribution-like phrase, “used by integrative practitioners”, is verbatim from the ER Monitoring table.

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.	🟢	Measured, non-promotional register matching the ER throughout.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Thresholds and targets given without alarmism; the sheet frames copper as a measurable, actionable status question.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Content is stated descriptively; no imperatives directed at a patient.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	Cadence and dose cells describe practice, not instructions.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No occurrence of “recommend”, “advise”, “should” or equivalents.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere in the file.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms retained are the ER’s own section headings and biomarker names, which the compactness rules (12.3/13.3) require unexpanded.
2.8	Information is presented in a concise and very compact manner	🟢	Gate items, tier items and biomarker cells are all single clauses.
2.9	It DOES NOT address the reader directly	🟢	Confirmed: no “you”/”your” anywhere.
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.	🟢	Optimal functional ranges, non-ceruloplasmin copper and the copper-to-zinc ratio are pitched at an optimizing 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.	🟢	A 12-marker baseline panel, a 24-hour urine collection and a three-point recheck schedule are presented without hedging on 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 simplified “ask your doctor” framing; the sheet assumes the reader will obtain and interpret the panel.
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 lede makes the key optimizer-specific point explicit: supplementation helps only where a shortfall exists, and adding it above adequacy tracks with harm.
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.	🟢	“anti-aging” does not occur; the title uses “Health & Longevity”.
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.	🟢	No “pill”, “shot”, “by mouth” or similar. Lede wording (“weight-loss surgery”, “death from any cause”) is the ER Conclusion’s own voice, not route-of-administration lay phrasing.

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 strings byte-identical to the template.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 template variables present; marker_#_* and qualitative_item_# correctly expanded to 12 and 6 numbered instances.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Normalised diff against the template shows no change outside metadata, variable content, and the two required display: none attributes.

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 is empty; the High benefits tier carries explanatory prose rather than an empty-state phrase.
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.	🟢	“Standard supplemental dose”, “Preferred forms”, “Best time of day” and all gate items reproduce the ER bold labels verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Monitoring row labels and tier labels match the ER table and ER headings exactly.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji code points anywhere in the file; the ER’s “⚠️ Conflicted” markers are correctly stripped.
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.	🟢	The template’s A4 print rules are intact, and every section is condensed against its ER source: the Monitoring table drops the ER’s entire Context/Notes column, Benefits and Risks reduce full ER subsections to bare headings, thirteen Protocol bullets become three cells, and the three-paragraph Conclusion becomes a 59-word lede.

---

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.	🟢	Lines 2–14, immediately after <!doctype html> on 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; preamble text on line 2 is 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.	🟢	Enclosed in an HTML comment; no metadata value is repeated in the header or body.
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:03" is quoted, and it contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: copper_2026-0920-0003_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.9.11, matching the prompt version.
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-0920-0331.
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” — single word, no 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]”	🟢	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” — nickname plus version, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the file’s actual name 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 across all nine keys; no stray whitespace or 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: “Copper for Health & Longevity - Quick Reference Sheet”.
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: “Copper for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: 09/20/2026, matching qrs_creation_date 2026-0920.
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 the title and the template subline.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Compresses all three Conclusion paragraphs into the decision-relevant core.
7.2	[at_a_glance] is no longer than 60 words	🟢	59 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Narrow range, shortfall causes, null trial evidence and the mortality/Alzheimer’s association all map to ER lines 491–493.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “weight-loss surgery” and “acid suppression” replace bariatric/PPI terminology.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial named or quantified.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numeric estimates of any kind.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All seven items trace to ER lines 323 and 331–338.
8.2	[stop_items] represent the Contraindications from the ER	🟢	The six “Populations who should avoid Copper” entries plus the copper-chelating drugs absolute contraindication.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Lines 540–546, seven <li> elements.
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.	🟢	Explanatory glosses stripped (e.g., “a severity grading of liver failure”, “rare early-life disorders in which copper builds up in the liver”); no trailing dash clauses.
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).	🟢	1.6 µmol/L, bilirubin 2 mg/dL, Child-Pugh Class C, 155 µg/dL and 100 µg / 24 h 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 uses no ranking notation 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 ER names such populations and the section is correctly populated.
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 section is not empty.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All eight items map to ER lines 313–329.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Eight of the nine ER interaction bullets carried over; copper-chelating drugs correctly excluded and placed in Contraindications.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Lines 554–561, eight <li> elements.
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.	🟢	Mechanism and mitigation text dropped throughout; the explanatory gloss “stomach-acid reducers” correctly trimmed from the PPI item.
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 drugs (ferrous sulfate, ferrous bisglycinate, omeprazole, pantoprazole, famotidine), the 1,500 mg vitamin C threshold and the 50 mg zinc contraindication threshold are all retained.
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 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 ER names nine interactions and the section is correctly populated.
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 section is not empty.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER Protocol section	🟢	All three cells map to ER Therapeutic Protocol lines 362, 366 and 372.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose, form and timing — the three decisions a reader must make to execute.
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 lists thirteen protocol bullets, 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 fields populated with 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	🟢	The ER’s Practical Considerations “Time to effect” bullet names exactly two distinct aspects, both covered.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Blood counts (93% of cytopenias resolve) precede neurological recovery (25% improve).
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.	🟢	The third pcell carries style="display: none" (line 503) with all three spans empty.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	Both used sets populated from ER line 417 and ER lines 161–167.
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.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	Every listed benefit is an ER Expected Benefits sub-heading.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present at lines 521–530.
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.	🟢	Headings only; all Magnitude figures and “⚠️ Conflicted” markers stripped.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any benefits item.
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 states no benefit reaches High; benefits_high carries style="display: none" and is empty (line 521).

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All nine listed risks are ER Potential Risks & Side Effects sub-headings.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present at lines 573–584.
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.	🟢	Headings only; relative risks, standardized mean differences and “⚠️ Conflicted” markers stripped.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any risks item.
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 risk tiers carry 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	🟢	Rows and cadence both drawn from ER Monitoring Protocol & Defining Success (lines 443–460).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All 12 ER biomarker table rows reproduced with matching targets and rationales.
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 736 reproduces the baseline / 8-week / 6-month / 12-month schedule and the 40 mg zinc trigger from ER line 445.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Items taken from the ER’s “Qualitative markers worth tracking alongside the labs” list.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All six ER qualitative markers (lines 464–469) reproduced in order.

Issues 20/09/2026 04:00

Pass rate 100.00%. No issues found.

Issues 20/09/2026 03:53

1. 2.15 — Consumer-grade drug term in lede: [at_a_glance] (line 433) says “long-term stomach-acid reducers”, the over-the-counter consumer label for the drug class; the ER Conclusion uses “long-term acid suppression” and the QRS Key Interactions gate (line 558) correctly uses “Proton pump inhibitors and H2 blockers”.

Fixes 20/09/2026 03:53

1. 2.15 — Consumer-grade drug term in lede: Replaced “long-term stomach-acid reducers” in [at_a_glance] with the ER Conclusion’s own formal wording “long-term acid suppression”; the lede remains at 59 words.

Issues 20/09/2026 03:47

1. 11.1 / 11.3 — Half-life used as time-to-effect: The third Time to effect cell (QRS lines 503-513) carries “Half-life and dose splitting” / “4–6 weeks”, taken from the ER Therapeutic Protocol bullet on whole-body turnover (ER line 374), which is a pharmacokinetic and dosing-frequency property rather than a time to effect; the ER names only two time-to-effect aspects (ER line 417), so the third set should have been left empty and made invisible.

Fixes 20/09/2026 03:47

1. 11.1 / 11.3 — Third time-to-effect cell emptied: Removed the “Half-life and dose splitting” / “4–6 weeks” content from time_3_label, time_3_value and time_3_sub, since it is a pharmacokinetic property rather than a time-to-effect aspect. The three spans are retained but emptied and the containing .pcell is set to style="display: none", leaving the two ER-supported sets (blood counts, neurological recovery) visible.

Issues 20/09/2026 03:39

1. 7.4 — Clinical shorthand in the lede: The At-A-Glance span (line 433) uses “long-term acid suppression”, a clinical-register phrase a non-specialist would not use unprompted; the ER itself glosses it as “acid-suppressing medication” (ER line 228) and “stomach-acid reducers” (ER line 321).

Fixes 20/09/2026 03:39

1. 7.4 — Plain language in At-A-Glance: Replaced “long-term acid suppression” with the ER’s own plain-language gloss “long-term stomach-acid reducers” (ER line 321) in the at_a_glance span; the lede remains 59 words.

Issues 20/09/2026 03:36

1. 1.3 — Alzheimer’s qualifier dropped: [at_a_glance] (line 433) says blood copper “tracks with … Alzheimer’s disease” where the ER Conclusion (line 493) says “the presence of Alzheimer’s disease”; dropping “the presence of” upgrades a prevalent-case association into an unqualified risk signal.
2. 2.15 — Consumer-grade drug-class term: [at_a_glance] (line 433) uses “long-term use of stomach-acid reducers” instead of the ER’s formal “long-term acid suppression”, and it contradicts the QRS’s own “Proton pump inhibitors and H2 blockers” at line 558.

Fixes 20/09/2026 03:36

1. 1.3 — Alzheimer’s qualifier restored: Changed the [at_a_glance] closing clause from “and Alzheimer’s disease” to “and the presence of Alzheimer’s disease”, matching the ER Conclusion and restoring the prevalent-case framing.
2. 2.15 — Formal term for acid suppression: Replaced the consumer-grade “long-term use of stomach-acid reducers” in [at_a_glance] with the ER’s formal “long-term acid suppression”.