Audit: QRS - Spirulina for Health & Longevity
Audit conducted on 13/08/2026 06:47 using AI4L / Opus 5
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. | 🟢 | Every protocol cell, time-to-effect cell, benefit, risk, gate item, marker row, cadence sentence and qualitative bullet traces to a literal ER passage (ER Therapeutic Protocol, Practical Considerations, Expected Benefits, Potential Risks & Side Effects, Key Interactions & Contraindications, Monitoring Protocol & Defining Success). |
| 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. | 🟢 | The ER’s ⚠️ Conflicted markers on “Improved Glycemic Control” and “Antiviral Effect in Chronic Viral Infection” are carried as “(conflicted)”; the ER’s “No established target for this purpose” and “No established optimum” wording is preserved in marker_12_target and marker_13_target. |
| 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”). | 🟢 | Absolute exclusions stay absolute in [stop_items]; “Monitor”/”Caution”-graded ER interactions stay in the Key Interactions gate rather than being promoted to 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. | 🟢 | Nothing from ER Benefit-Modifying Factors, Risk-Modifying Factors, Risk Mitigation Strategies or Sourcing and Quality appears in the gates or risk tiers; each QRS section draws only from its mandated ER source 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. | 🟢 | The QRS carries no PMIDs, no study citations, no expert names, no NCT identifiers and no brand names; ER attributions such as “[The dose-response body composition analysis]” were dropped rather than transplanted. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions of any kind appear in the QRS. |
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. | 🟢 | Flat, declarative, evidence-first 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 | 🟢 | Quantified doses, ranges, thresholds and target values are given without hedging or exhortation. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Content is stated as what the evidence shows (e.g., “Higher doses produced larger effects”), not as instruction to a patient. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | Monitoring cadence and gates are stated as noun-phrase schedules and category lists, not as imperatives directed at anyone. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No instance of “recommend”, “advise”, “should”, or equivalent prescriptive verb in the QRS body. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronoun (“you”, “your”, “yourself”) occurs anywhere in the file. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms are confined to biomarker names where no plainer equivalent exists (hs-CRP, ALT, AST, HbA1c); the At-A-Glance uses lay equivalents throughout. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Gate items, benefit and risk tiers, and marker rows are single short phrases; no item carries a subordinate explanatory clause beyond what the checklist requires preserved. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed: 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 sheet assumes willingness to obtain a certificate of analysis-grade product and to run a 14-marker panel — the proactive-optimizer profile. |
| 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. | 🟢 | Split dosing with meals, a full baseline draw, and repeat panels at 12 weeks / 3 and 12 months are presented without cost or convenience caveats. |
| 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. | 🟢 | Functional optimal ranges (e.g., ALT <20 U/L, hs-CRP <0.8 mg/L) are used rather than conventional population cut-offs. |
| 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 foregrounds product sourcing as the binding constraint — the variable this audience can act on — rather than the average consumer’s dose question. |
| 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 in the file; 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)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt. | 🟢 | Formal terminology throughout the gates, tiers, monitoring table and cadence; the lay substitutions (“blood fats”, “hay-fever”) occur only inside [at_a_glance], where item 7.4 explicitly mandates plain-language terms. |
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” | 🟢 | Verified against the template: “Protocol” (line 446), “Time to effect” (492), “Benefits” (540), “Contraindications” (573), “Key Interactions” (593), “Risk & Side Effects” (620), “Monitoring” (647), “Marker”/”Target”/”Why” (651–653), “Qualitative Assessment” (837); all four tier labels appear unmodified in both the Benefits and Risks cards. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All 38 template variable names are present; the repeating marker_#name/target/why and qualitative_item# spans are instantiated as marker_1–14 and qualitative_item_1–6. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | A structural diff against [qrs_template] shows changes confined to variable regions and to the added monitoring table rows; the website="evidence_review", website="audit" and website="full_review" spans, the CSS block, the footer disclaimer and all markup are byte-identical to the template. |
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 relied on by the QRS is empty. |
| 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_label] “Standard dose range”, [action_2_label] “Dose for lipid and pressure endpoints” and [action_3_label] “Split versus single dosing” reproduce the ER Therapeutic Protocol bold labels verbatim; marker names reproduce the ER monitoring table’s Biomarker column verbatim. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | No ER bold label is altered; the Time-to-Effect labels derive directly from the endpoint names inside the ER’s own “Time to effect” bullet (“lipid and blood pressure changes”, “Hemoglobin”, “subjective fatigue”). |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji characters occur in the file; the ER’s ⚠️ marker is rendered as the word “(conflicted)” and tiers rely on the CSS palette plus bold “High:/Medium:/Low:/Speculative:” labels. |
| 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 compressed to the minimum consistent with the mandatory-completeness items (14.2, 15.2, 8.2, 9.2): gate items and tier entries are bare noun phrases with all rationale stripped, marker “Why” cells are 2–5 words, and no content was moved onto additional structure beyond the template’s own single-sheet layout. |
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. | 🟢 | Single comment spanning 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 --- on line 3, closing --- on line 13; the preamble text “QRS — Metadata (invisible, parsed by audit tooling)” precedes the opening delimiter, which is permitted. |
| 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; none of its values are duplicated into any rendering 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, correctly so because it contains a colon. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Line 4: er_filename: spirulina_2026-0813-0317_Opus_ER.md, matching the ER’s own filename frontmatter value. |
| 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 head of 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-0813-0622, conforming to 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 carrying 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 with no context-window or deployment qualifier appended. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9: qrs_filename: spirulina_2026-0813-0317_Opus_QRS.html, matching 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 including the tooling-added git_user and git_issue: 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: “Spirulina for Health & Longevity - Quick Reference Sheet”, matching the ER’s canonical_topic with the ampersand correctly 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 &) |
🟢 | Line 417: “Spirulina for Health & Longevity”. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: “08/13/2026”, the correct MM/DD/YYYY rendering of qrs_creation_date: 2026-0813-0622. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Line 425: “Opus 5”, matching the frontmatter value. |
| 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 is structurally identical to the template; the ER’s eight alternate names were not carried over and no badge, stamp or variant marker was added. |
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 and closes on the decision-relevant lever — product sourcing — rather than restating the mechanism. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 56 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Lipid/pressure/body-composition/inflammation shifts, the thinner hay-fever, glycemic, antioxidant and fatigue signals, and the open-pond toxin-and-lead constraint each map to a distinct sentence in the ER Conclusion. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | Lay substitutions used throughout: “blue-green algae”, “blood fats”, “hay-fever”, “blood sugar”, “a marker of inflammation”, “liver-damaging toxins”. No acronym appears. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | Only the generic “Pooled trials” and “fewer studies” appear; no author name, year, n, or p-value. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | Direction-only language (“shift favorably”, “edges down”, “fall slightly”, “declines”); no numeric estimate or confidence interval. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All nine [stop_items] map to the “Populations who should avoid Spirulina” list in that ER section; the transplant/immunosuppression item additionally reflects the “Absolute contraindication” grading of the ER’s immunosuppressants bullet. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All nine ER exclusion bullets are present, in ER order, with none added and none omitted. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Nine <li> elements at lines 576–588 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 clause is stripped: “— an absolute exclusion given the phenylalanine load”, “on absence of human safety data rather than evidence of harm”, “on the contamination profile documented in retail product testing”, “on the antiplatelet effect”, and the gloss “(a blistering autoimmune skin disease)”. |
| 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). | 🟢 | Preserved: “of any severity”, the named autoimmune conditions, “ferritin above 300 ng/mL (men) or 200 ng/mL (women)”, “Child-Pugh Class B or C”, and the “two weeks before elective surgery” window. |
| 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 ER names nine such populations, so the section is correctly populated rather than left 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 ten [caution_items] map one-to-one onto bullets of that ER section. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | Ten of the ER’s eleven interaction bullets are carried; the immunosuppressants bullet — graded “Absolute contraindication in transplant recipients” — is correctly excluded because it is already covered by [stop_items] “Solid-organ transplant recipients and anyone on maintenance immunosuppression”. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Ten <li> elements at lines 596–610 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 grading word (“Caution”, “Monitor”, “Additive”) and mechanistic sentence is stripped; each item is reduced to the drug or supplement class plus its example list. |
| 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 named example drugs and supplements are retained; the antihypertensives list is shortened from the ER’s class-plus-example phrasing to “(lisinopril, losartan, amlodipine)” without dropping any agent, and the sulfonylurea example is kept as “glipizide”. |
| 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 ER names eleven such interactions, so 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 action sets derive from ER Therapeutic Protocol bullets (“Standard dose range”, “Dose for lipid and pressure endpoints”, “Split versus single dosing” with “Best time of day”). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Dose range, endpoint-specific dose, and timing/splitting are the three decisions a user must make; the remaining nine ER protocol bullets are modifiers or background rather than implementation steps. |
| 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 twelve protocol bullets, 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 action variables carry substantive ER-derived content: “2–8 g daily”, “4–8 g daily”, “2–3 doses with meals”, each with an ER-sourced 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 | 🟢 | The ER’s “Time to effect” bullet names exactly three: hemoglobin within two weeks, subjective fatigue within hours, and lipid/blood-pressure change over four to twelve weeks. All three are carried. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Lipids and blood pressure first (both High-tier benefits), then hemoglobin and subjective fatigue (both Low-tier), in the ER’s own Low-tier order. |
| 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. | 🟢 | “4–12 weeks”, “2 weeks” and “Within hours” each carry an ER-sourced sub-line drawn from the ER Practical Considerations bullet and the corresponding Expected Benefits magnitude 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 a dedicated “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 fourteen entries correspond to the fourteen benefit sub-headings in the ER Expected Benefits section, tier for tier. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans are present and populated (lines 542, 548, 554, 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 alone; no magnitude figure, confidence interval, trial count or mechanism is carried across. The one retained marker, “(conflicted)”, is the ER’s own ⚠️ Conflicted flag, which item 1.3 requires be preserved rather than dropped. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | The ER benefit sub-headings contain no parenthetical content, and none of the parenthetical glosses from the ER body text (e.g., “(low-density lipoprotein, the particle that deposits cholesterol in artery walls)”) was carried over. |
| 12.5 | If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, 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. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | All ten entries correspond to the ten risk sub-headings in that ER section, tier for tier. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans are present and populated (lines 622, 625, 630, 636). |
| 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 alone; the “8 of 18 products”, “31 adverse event reports”, “five documented cases” and single-case-report details are all left behind. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | The ER’s inline glosses — “(β-methylamino-L-alanine)”, “(a rapid, whole-body allergic reaction…)”, “(rapid breakdown of muscle tissue…)” — are all stripped from the QRS entries. |
| 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 contain items in the ER. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | The table reproduces the ER Monitoring Protocol & Defining Success biomarker table, with marker names, targets and “Why Measure It?” text carried across verbatim. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All fourteen ER table rows are present in ER order: LDL cholesterol, triglycerides, HDL cholesterol, blood pressure, hs-CRP, fasting glucose, HbA1c, ferritin, ALT, AST, uric acid, creatine kinase, blood lead, and vitamin B12 with methylmalonic acid. |
| 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 826–831 reproduce the ER’s second monitoring paragraph: baseline draw, lipid/CRP/liver panel at 12 weeks then annually, ferritin at 3 and 12 months then annually, blood pressure weekly then monthly, creatine kinase and blood lead symptom- or contamination-driven. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | All six entries reproduce the “Qualitative markers worth tracking alongside the laboratory values” list at the end of the ER monitoring section. |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All six ER qualitative bullets are present in ER order: digestive comfort, nasal symptoms and smell, perceived exertion and recovery, sleep latency and continuity, new rash/joint/muscle symptoms, and standing lightheadedness. |
Issues 13/08/2026 06:47
Pass rate 100.00%. No issues found.
Issues 13/08/2026 06:44
- 1.3 — Creatine kinase hedge broadened: [marker_12_target] (line 788) drops the ER’s scoping phrase, rendering “No established target for this purpose” (ER line 509) as the absolute “No established target”.
Fixes 13/08/2026 06:44
- 1.3 — Creatine kinase hedge restored: [marker_12_target] changed from “No established target; track change from the individual’s own baseline” to “No established target for this purpose; track change from the individual’s own baseline”, matching the ER’s scoped wording.
Issues 13/08/2026 06:30
- 1.4 — Rhinitis dose under wrong protocol label: [action_2_sub] (lines 470–473) closes with “Allergic rhinitis trials used 2 g daily”, a fact from the ER’s separate “Dose for allergic rhinitis:” bullet (ER line 411), placed inside the cell labelled “Dose for lipid and pressure endpoints” whose value reads 4–8 g daily.
Fixes 13/08/2026 06:30
- 1.4 — Rhinitis dose under wrong protocol label: Removed “Allergic rhinitis trials used 2 g daily.” from [action_2_sub] and replaced it with the ER’s own supporting clause for that bullet, so the cell now reads “Higher doses produced larger effects, and lipid trials clustering at 4 g and above produced the clearest separations from placebo.”
Issues 13/08/2026 06:27
- 11.4 — Time-to-effect subs restate value: [time_2_sub] (line 517) and [time_3_sub] (line 530) repeat their own label and value (“Hemoglobin shifts within two weeks”, “Subjective fatigue shifts within hours”) instead of carrying the ER’s substantive detail at lines 207 and 213.
Fixes 13/08/2026 06:27
- 11.4 — Time-to-effect subs restate value: Replaced the redundant [time_2_sub] and [time_3_sub] text with ER-derived detail — “Rose 3.4% after 14 days at 6 g daily, with no accompanying performance gain.” and “Mental fatigue scores improved within four hours at 3 g daily.” — instead of repeating the cell label and value.