Audit: QRS - Plasmalogens for Health & Longevity

Audit conducted on 23/08/2026 22:22 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 populated span traces to ER text: protocol cells to ER Therapeutic Protocol (lines 313–318), time-to-effect to Practical Considerations (line 349), gates to Key Interactions & Contraindications (lines 282–297), tiers to the ER benefit/risk headings, monitoring rows to the ER biomarker table (lines 373–381).
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 chronobiology data exist” (action_3_sub) and “No established target; track change from own baseline” (marker_1/2/8_target) are carried verbatim from ER lines 318 and 373–380.
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”).	🟢	The five avoid-populations stay in the Contraindications (stop) gate and the eight interaction bullets stay in the Key Interactions (caution) gate, at the ER’s own strength; “conflicted” is retained on the memory benefit.
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.	🟢	No content from ER Benefit-Modifying Factors (lines 209–215) or Risk-Modifying Factors (lines 271–277) appears in the gates or in Risk & Side Effects; each QRS card draws only from its mandated ER section.
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 identifiers, expert names or brand names appear anywhere in the QRS; the only study references are the ER’s own generic descriptors (“the athlete trial”, “the Alzheimer’s trial”).
1.6	The QRS does not introduce new attributions.	🟢	Takehiko Fujino and the Institute of Rheological Functions of Food (ER line 313) are dropped rather than replaced; no new attribution is 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.	🟢	The QRS mirrors the ER’s measured, sceptical register, including the ER’s own funding caveat and “payoff has not yet been demonstrated” framing.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Numeric targets, thresholds and doses throughout; the monitoring cadence and pre-set readout points give the reader an actionable frame without overselling.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Cells state what trials used and what markers show rather than instructing; e.g. “the regimen used in every Japanese trial”, “as used in the athlete mood trial”.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperative or prescriptive constructions; the footer disclaimer is the template’s unchanged text.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Protocol cells describe the studied regimens; monitoring rows describe what each marker shows. No recommending verbs appear.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	A scan of the full file returns no second-person pronoun outside CSS.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms are either the ER’s own defined terms or unavoidable marker names; the At-A-Glance is fully plain-language.
2.8	Information is presented in a concise and very compact manner	🟢	Gate items, tier lines and marker cells are single short clauses; ER trailing rationale is stripped throughout.
2.9	It DOES NOT address the reader directly	🟢	No direct address anywhere in the document.
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.	🟢	The nine-marker monitoring panel with functional (not conventional) targets and the self-tracked qualitative list presume a self-quantifying 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.	🟢	Specialist lipidomics markers, twice-run cognitive batteries and a 12-week/6–12-month cadence assume willingness to bear cost and 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.	🟢	Optimal functional ranges (hs-CRP <1.0 mg/L, triglycerides <80 mg/dL, ALT/AST <25 U/L) are optimizer-grade, not population-grade.
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 At-A-Glance leads with target engagement being real while clinical payoff is unproven, and flags the manufacturer-funding problem — the weighting a risk-aware optimizer 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.	🟢	“Anti-aging” does not occur in the file; the title uses the ER’s canonical “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)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt.	🟢	Marker names, thresholds and gate items use formal terminology throughout; the plainer At-A-Glance wording is required by item 7.4.

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 match [qrs_template] byte-for-byte, including “Time to effect” (line 484), “Risk & Side Effects” (line 589) and the Marker/Target/Why headers (lines 615–617).
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 template variable names are present; the additional spans are the expected numbered expansions of the repeatable marker_#* and qualitative_item# rows.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	A diff of the QRS body against the template shows only variable-content substitutions; every changed span is governed by a checklist item, and the header website= spans and footer 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 is empty; every ER section the QRS draws from carries content.
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 purified-plasmalogen dose”, “Higher-dose mood regimen” and “Timing of day” are the ER’s bold protocol labels verbatim (ER lines 313, 314, 318); the caution items reuse the ER’s bold interaction labels.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Protocol labels, marker names and gate labels are carried through unchanged; only the ER’s trailing “Other interventions — “ connector is dropped from the dietary-pattern label.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	A Unicode scan of the file returns no emoji; the ER’s ⚠️ marker on the memory benefit was resolved to plain text.
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 tier is a single line, gate items are single clauses, and marker targets/why cells are trimmed; the print rules and A4 @page block are intact.

---

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 comment opens at line 2, immediately after <!doctype html> on line 1, and closes at line 14 before any other content.
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; the descriptive text on line 2 precedes the opening delimiter.
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 block sits entirely inside an HTML comment and none of its values are echoed on the page apart from the independently required 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:03" is quoted, correctly, because it contains a colon; all other values are bare and trimmed.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: plasmalogens_2026-0823-1647_Opus_ER.md, matching the ER frontmatter filename field.
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 the version badge at the top of [qrs_prompt].
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-0823-2215, in the required format.
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 with 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]”	🟢	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” is nickname plus version number with no additional qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9: qrs_filename: plasmalogens_2026-0823-1647_Opus_QRS.html, 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.	🟢	Confirmed across all ten keys; no stray whitespace and no 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: “Plasmalogens 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: “Plasmalogens for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “08/23/2026”, the correct reformatting of 2026-0823-2215.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “Opus 5”, matching the frontmatter 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.	🟢	The header block (lines 415–428) contains only the title and the template’s subline; the ER’s “Also known as” list is 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	🟢	Lines 433–437 compress ER Conclusion paragraphs two and three: reliable target engagement, unproven outcome, single-study positives, sponsor funding, and the plausible-but-expensive verdict.
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.	🟢	Each clause maps to a distinct ER Conclusion passage (lines 408–412): raised blood levels, tolerability, conflicting memory results, single-study positives, sponsor funding, and the closing verdict.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; the ER’s clinical register is deliberately downshifted (“taken by mouth” for oral dosing, “blood fats” for triglycerides, “product makers” for sponsors).
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial name, year, sample size or p-value appears; “one small study” is used generically.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No point estimates, hazard ratios, confidence intervals or significance statements appear.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All five items come from the “Populations who should avoid Plasmalogens” list inside that ER section (lines 291–297).
8.2	[stop_items] represent the Contraindications from the ER	🟢	All five ER avoid-populations are represented, one-to-one, with none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Lines 555–561: five <li> elements inside the stop_items span.
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.	🟢	Every ER trailing rationale is stripped: “chicken-derived and synthetic forms are the alternatives”, “on the iron-dependent-oxidation concern”, “until the ether-lipid and tumour-metabolism question is resolved”, “since no trial has enrolled them”, “who need supervised disease-specific protocols”.
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).	🟢	The full iron thresholds (ferritin >300 ng/mL men, >200 ng/mL women, transferrin saturation >45%) and the marine-product scoping qualifier are preserved (lines 555–558).
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’s avoid-population list contains no ranking notation; the “>” characters in the ferritin item are numeric threshold operators, which are self-interpreting.
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 five such populations, and the section is correspondingly populated rather than empty.
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 come from the bulleted interaction list at ER lines 282–289.
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 stop-gate item — the ferroptosis-therapy drug interaction is distinct from the “active treatment for a solid tumour” population gate.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Lines 569–579: eight <li> elements inside the caution_items span.
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.	🟢	Every ER mechanism sentence and mitigation clause is stripped; the ER’s “Other interventions — “ connector is removed from the dietary-pattern item, leaving the bare label.
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).	🟢	All four ER drug-example lists are preserved intact: the anticoagulant, ferroptosis-inducer, antioxidant and NSAID parentheticals (lines 569–578).
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’s interaction parentheticals are plain comma-separated drug lists with no ranking notation.
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 identifies eight such interactions, and the section is correspondingly 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 derive from ER Therapeutic Protocol bullets at lines 313, 314 and 318.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose, higher-dose mood regimen and administration timing are the three executable choices in that ER section; the remaining bullets are modifiers (genetics, APOE4, sex, age, baseline biomarkers) or non-recommended alternative routes.
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 over three actionable aspects, so 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 cells are populated (lines 448–480): “1 mg daily”, “2 mg per day” and “With a fat-containing meal”, each with an ER-derived sub-line.

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	🟢	Mood/fatigue, memory and blood plasmalogen level are exactly the three timings given in the ER Practical Considerations “Time to effect” bullet (line 349).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Order runs Medium-tier mood and fatigue, then Low-tier memory, then Speculative-tier blood plasmalogen level — descending by ER benefit tier.
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 supplies three distinct time-to-effect aspects, so 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 cells are populated (lines 490–521) with “4 weeks”, “8–12 weeks” and “Within 4 weeks” plus ER-derived sub-lines.
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 explicit time-to-effect data at line 349, so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	Every listed item corresponds to a fourth-level heading in ER Expected Benefits (lines 138–204).
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans are present at lines 530, 531, 536 and 541.
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-separated list of bare ER headings; all Magnitude paragraphs, sponsor notes and trial descriptions are dropped.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any benefits span.
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 (line 140); line 530 is <span data-qrs-var="benefits_high" style="display: none"></span> with no empty-state text.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All eight listed items correspond to fourth-level headings in ER Potential Risks & Side Effects (lines 222–266).
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans are present at lines 591, 592, 596 and 600.
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 carries only the bare ER headings; the PPI-1011 trial description, the 18%-decline magnitudes and the ferroptosis mechanism text are all dropped.
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 span.
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.	🟢	The ER states no risk reaches High (line 224); line 591 is <span data-qrs-var="risks_high" style="display: none"></span> with no empty-state text.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	All rows derive from the biomarker table in ER Monitoring Protocol & Defining Success (lines 371–381).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All nine ER biomarkers are present in ER order, with the Optimal Functional Range and Why Measure It? values carried through faithfully.
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.	🟢	Lines 739–742 condense ER lines 367–369: baseline draw with the battery run twice, 12-week repeat, 6–12 month cadence thereafter, and the 3-month floor on red-cell measures.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	All six items come from the “Qualitative markers worth tracking alongside the labs” list at ER lines 385–390.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All six ER qualitative markers are present in ER order (lines 751–771).

Issues 23/08/2026 22:22

Pass rate 100.00%. No issues found.