Audit: QRS - Fucoidan for Health & Longevity
Audit conducted on 10/09/2026 02:12 using AI4L / Opus 5
Summary
| Items | Count |
|---|---|
| Total | 93 |
| Passed | 84 |
| Failed | 0 |
| N/A | 9 |
| Pass Rate | 100.00% |
- Total = Passed + Failed + N/A
- Pass Rate = Passed / (Passed + Failed) × 100
- N/A items are excluded from the pass rate calculation
1. General Rules
| # | Description | Result | Comments |
|---|---|---|---|
| 1.1 | Every claim, magnitude, label, recommendation, and statement in the QRS is literally supported by content in the source ER. | 🟢 | All protocol figures, gate items, tier items, marker targets and cadence text trace to ER lines 273-427. |
| 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. | 🟢 | “Neither established as superior” (line 467) and “no interference has been demonstrated” (line 629) mirror ER lines 352 and 327. |
| 1.3 | The QRS never strengthens an ER claim (e.g., “not formally studied” → “not required”) or softens one (e.g., “do not use during pregnancy” → “use with caution during pregnancy”). | 🟢 | Contraindications keep absolute framing (“Pregnancy and breastfeeding”, line 582); Caution/Monitor verbs match ER lines 321-327. |
| 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. | 🟢 | Benefits map to ER Expected Benefits, risks to Potential Risks & Side Effects, gates to Key Interactions & Contraindications; no cross-category relabelling. |
| 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. | 🟢 | Only “Taiwan” (line 457) is carried over, and it is present in ER line 351. |
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. | 🟢 | Tone tracks the ER’s measured, caveat-forward register. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Expert and data-driven while remaining accessible. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Presents evidence and ranges rather than directives. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No prescriptive verbs; the footer disclaimer is the template’s fixed text. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | Values are stated as trial observations (“Trials generally split above 1,000 mg daily”, line 481). |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns anywhere in the document. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Plain language throughout; the only abbreviations are marker names in the Monitoring table, where they are the marker. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Tier items are compressed to semicolon-separated headings; gate items are stripped to label plus verdict. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed: no direct address to the reader. |
| 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 proactive optimiser (product-form choice, split dosing, 10-marker panel). |
| 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 a monitoring panel and washout discipline that require real 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. | 🟢 | Not pitched at the general population. |
| 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. | 🟢 | Weighting reflects the ER: firm oncology-adjunct signal, animal-only longevity claim, product-quality caveat. |
| 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. | 🟢 | “Longevity” is used in the page title and header topic; “anti-aging” appears nowhere. |
| 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. | 🟢 | Clinical register throughout; “purified extract”, “adverse” framing and marker names are used rather than consumer 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 headings, gate headings, tier labels and the Marker/Target/Why column headers match the template byte-for-byte. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All 34 template spans present; marker_#* and qualitative_item# are expanded to 10 and 6 instances per the template’s repeatable pattern. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | The three website= spans, the page_title wrapper and all CSS 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 is empty; the ER’s High-risk tier carries explanatory prose and is handled under 13.5, so no empty-state phrasing applies. |
| 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. | 🟢 | Protocol labels (lines 450, 464, 478) and all seven interaction labels (lines 592-628) reproduce the ER’s bold labels verbatim. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | No label is paraphrased or abbreviated; Time-to-effect labels are derived where the ER supplies no bold label. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji present; the ER’s tier emoji and the two “Conflicted” markers are 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. | 🟢 | Every section is condensed to heading-level items with explanations, magnitudes and citations removed; no content is spilled into added structure. |
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 is the first element after <!doctype html> (lines 2-14). |
| 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. | 🟢 | Opened at line 3 and closed at line 13; the preamble text sits before 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. | 🟢 | Enclosed in an HTML comment; no metadata value is repeated in any rendered 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. | 🟢 | Only duration: "00:03" is quoted, and it must be because the value contains a colon. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | er_filename: fucoidan_2026-0910-0002_Opus_ER.md (line 4). |
| 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) matches the QRS.md version badge. |
| 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-0910-0153 (line 6), correct 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. |
| 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, no qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | qrs_filename: fucoidan_2026-0910-0002_Opus_QRS.html (line 9) matches 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 trimmed and unquoted except where YAML requires it. |
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>Fucoidan for Health & Longevity - Quick Reference Sheet</title> (line 22), 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 &) |
🟢 | Fucoidan for Health & Longevity (line 417). |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | qrs_creation_date 2026-0910-0153 renders as 09/10/2026 (line 421). |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Opus 5 (line 425). |
| 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, AKA line or audit stamp. |
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 (lines 444-448) into what fucoidan is, the firmest finding, the longevity basis, the two harms and the product caveat. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 54 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Each clause maps to a distinct Conclusion passage (lines 444, 446, 448). |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms; “sulfur-rich”, “clotting times” and “thyroid function” are plain-language. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial names, years or sample sizes. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No effect sizes or statistics. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Drawn from the ER’s “Populations who should avoid Fucoidan” list (lines 331-335). |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All five ER avoid-populations are represented (lines 576-583). |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | 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. | 🟢 | Trailing rationale clauses from ER lines 334-335 are stripped. |
| 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 50 × 10⁹/L threshold, the 7-day window and Child-Pugh Class C are all preserved. |
| 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 contraindication bullets use no ranking notation inside parentheses. |
| 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. |
🟢 | Correctly non-empty: the ER names five avoid-populations. |
| 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 Contraindications section is not empty (5 items). |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Drawn from ER lines 321-327. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | All seven ER interaction bullets are present and none duplicates a contraindication. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Seven <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. | 🟢 | Mitigation sentences from ER lines 321-327 are stripped; each item ends at the Caution/Monitor verdict. |
| 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). | 🟢 | Every example-drug parenthetical is carried through verbatim. |
| 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 bullets use no ranking notation inside parentheses. |
| 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. |
🟢 | Correctly non-empty: the ER names seven interactions. |
| 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 Key Interactions section is not empty (7 items). |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Protocol section |
🟢 | Drawn from the ER Therapeutic Protocol section (lines 351-362). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Dose range, molecular-weight form and split dosing are the three decision-bearing aspects of that section. |
| 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 Therapeutic Protocol section supplies more than three actionable aspects; all three sets are used. |
| 10.4 | All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. |
🟢 | All nine used fields carry ER-derived content (ER lines 351, 352, 355, 357). |
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 | 🟢 | Vaccine antibody response, grip strength and walking distance, and gut/inflammatory markers, per ER lines 167, 173 and 386. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered Medium, Medium, Low, matching the ER’s own tier ordering. |
| 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 at least three time-to-effect aspects; all three sets are used. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | All nine used fields carry ER-derived content. |
| 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 time-to-effect information (Practical Considerations line 386 and the vaccination/strength trials). |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | Drawn from the ER Expected Benefits section (lines 155-247). |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four variables present and populated. |
| 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 item is the ER sub-heading alone; magnitudes, trial detail and mechanism are removed. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical content survives. |
| 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 (High, Medium, Low, Speculative) carry items in the ER. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | Drawn from the ER Potential Risks & Side Effects section (lines 265-305). |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four variables present. |
| 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 item is the ER sub-heading alone. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical content survives. |
| 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’s High tier carries no risk item, and [risks_high] is emptied and set to style="display: none" (line 642) rather than filled with empty-state text. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Drawn from the ER Monitoring Protocol & Defining Success table (lines 407-418). |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All ten ER biomarkers are present 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. |
🟢 | Populated from ER lines 341-342 and 405. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Drawn from the ER’s qualitative-marker list (lines 422-427). |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All six ER qualitative markers are present. |
Issues 10/09/2026 02:12
Pass rate 100.00%. No issues found.
Issues 10/09/2026 02:04
- 4.2 — Interaction label not verbatim: Line 628 renders the label as “Other interventions, chemotherapy and radiotherapy:” whereas ER line 327 reads “Other interventions - chemotherapy and radiotherapy:”; the hyphen separator was replaced with a comma.
Fixes 10/09/2026 02:04
- 4.2 — Interaction label restored verbatim: Changed the Key Interactions label at line 628 from “Other interventions, chemotherapy and radiotherapy:” back to the ER’s exact wording “Other interventions - chemotherapy and radiotherapy:”.
Issues 10/09/2026 01:59
- 1.3 / 2.5 — Split-dosing stated as a directive:
[action_3_value](QRS line 481) reads “Split above 1,000 mg daily”, an imperative instruction, while the ER’s “Single versus split dosing” bullet only reports that “Trials above 1,000 mg daily generally split into two doses”.
Fixes 10/09/2026 01:59
- 1.3 / 2.5 — Split-dosing stated as a directive:
[action_3_value]changed from “Split above 1,000 mg daily” to “Trials generally split above 1,000 mg daily”, restoring the ER’s hedged description of trial practice instead of an imperative dosing instruction.