Audit: QRS - D-Mannose for Health & Longevity
Audit conducted on 08/09/2026 04:31 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. | 🟢 | Every cell traces to the ER: protocol cells to Therapeutic Protocol, gates to Key Interactions & Contraindications, tiers to Expected Benefits / Potential Risks & Side Effects, table rows to the Monitoring Protocol & Defining Success table. |
| 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. | 🟢 | Hedges preserved where carried over, e.g. action_2_sub keeps “an add-on, not a replacement for antibiotics in a confirmed infection”; at_a_glance keeps “rest on animal work”. |
| 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”). | 🟢 | No strengthening or softening; contraindication “Pregnancy, and actively trying to conceive” keeps the ER’s absolute framing rather than downgrading to caution. |
| 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. | 🟢 | Categories preserved: benefit-modifying and risk-modifying factors are not surfaced in the gates; gate items come only from the ER interaction and avoid-population lists. |
| 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, study names, years, NCT identifiers, expert names, or brand names appear anywhere in the QRS. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions introduced; the only named entities are drug/organism names already in the ER. |
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. | 🟢 | Matches the ER’s cautious, non-promotional register throughout. |
| 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; no hype and no discouragement beyond what the ER states. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Presents evidence status rather than instructing; no imperative clinical direction. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No prescriptive advice; protocol cells describe what was studied. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | Content is stated, not recommended. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person address anywhere in the file. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms retained are the ones the decision gates and monitoring table require; no unnecessary jargon. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Gate, benefit, and risk items are reduced to key facts; rationale is stripped from the ER bullets. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | No “you” or “your” anywhere in the file. |
| 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. | 🟢 | Framing assumes a reader tracking infection counts, cultures, and glycemic and renal markers. |
| 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. | 🟢 | Continuous six-month dosing, baseline documentation, and repeat labs are presented without softening the effort involved. |
| 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 written for a general audience; assumes willingness to run a documented baseline and monitoring schedule. |
| 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 mirrors the ER: unproven-not-disproven for prevention, animal-only for everything beyond the bladder. |
| 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 term “anti-aging” does not appear. |
| 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. | 🟢 | Clinical register used for the gates, monitoring, and risks; the plain wording in at_a_glance is required by 7.4 and mirrors the ER Conclusion. |
3. Template Integrity
| # | Description | Result | Comments |
|---|---|---|---|
| 3.1 | The following labels and headings on the QRS are fixed and not modified: Card and section headings: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”; Gate headings: “Contraindications”, “Key Interactions”; Tier labels: “High”, “Medium”, “Low”, “Speculative”; Table column headers in Monitoring: “Marker”, “Target”, “Why” | 🟢 | All fixed headings, gate headings, tier labels, and table column headers match the template exactly. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All 34 template variables present; marker_#* and qualitative_item# expanded to 6 and 5 instances respectively. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | Structural diff against the template shows no change outside variable regions; the website=”evidence_review”, website=”audit”, and website=”full_review” spans 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; the ER’s Benefits High and Medium tiers carry explanatory prose rather than an empty-state phrase, and their handling is governed by 12.5. |
| 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 are verbatim ER bold labels (“Standard prevention dose”, “Acute-episode dose”, “Best time of day”); gate labels are verbatim ER interaction labels; monitoring marker names are verbatim ER table entries. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | No invented labels; the Time-to-Effect cell labels are the only derived ones and are required by 11.1, which asks for aspects the ER does not label as bullets. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji present; a full character scan returned no tier emoji or other pictographs. |
| 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. | 🟢 | 611 words of visible text across the eight cards, within the one-page budget; ER rationale is stripped from the gate and tier items rather than carried through. |
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. | 🟢 | Metadata comment opens on line 2, immediately after <!doctype html>, before any other comment or head 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. | 🟢 | YAML opens with — on line 3 and closes with — on line 13; the preceding title text 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 and not echoed by any visible element. |
| 5.4 | All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. | 🟢 | All values trimmed; only duration: “00:03” is quoted, which is required because the value contains a colon. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | er_filename: d_mannose_2026-0908-0146_Opus_ER.md matches the source ER. |
| 5.6 | Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” | 🟢 | qrs_prompt_version: 26.7.02 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-0908-0426 is in YYYY-MMDD-HHMM form. |
| 5.8 | The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” | 🟢 | qrs_creator_ai_nickname: Opus. |
| 5.9 | The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) | 🟢 | Single word, no version or qualifier. |
| 5.10 | The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” | 🟢 | qrs_creator_ai_fullname: Opus 5. |
| 5.11 | The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier (e.g., Opus 4.6, Sonnet 3.2, Grok 4.5, Gemini 3.1, ChatGPT 5.4) | 🟢 | Nickname plus version number only; no additional qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | qrs_filename: d_mannose_2026-0908-0146_Opus_QRS.html 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. | 🟢 | No stray whitespace or unnecessary quoting in any value. |
6. Page Title & Header
| # | Description | Result | Comments |
|---|---|---|---|
| 6.1 | [page_title] is set to the [canonical_topic] of the ER frontmatter followed by “ - Quick Reference Sheet” (e.g., “Intervention - Quick Reference Sheet”). The [canonical_topic] is HTML-entity-encoded as needed (e.g., & for &) |
🟢 | |
| 6.2 | [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &) |
🟢 | header_topic is “D-Mannose for Health & Longevity”, the ER canonical_topic. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | 09/08/2026, the MM/DD/YYYY form of qrs_creation_date 2026-0908-0426. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | header_subline_model is “Opus 5”, matching qrs_creator_ai_fullname. |
| 6.5 | No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. | 🟢 | Header carries only the title and the template subline; no badge, alternate-names 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: mechanism, cost and tolerability, the blinding split, and the animal-only scope of non-urinary claims. |
| 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 Conclusion passage: the urinary route, “cheap, widely available, and among the better-tolerated things”, the blinded-versus-unblinded pattern, and “rests on mice and cell cultures”. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms or specialist classifications; “bladder infections” rather than UTI, “loose stools and bloating” rather than gastrointestinal adverse events. |
| 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 risk ratios, confidence intervals, or percentages. |
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 D-Mannose” list inside Key Interactions & Contraindications. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All four ER avoid-populations are represented, none added. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Four <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. | 🟢 | Rationale clauses stripped, e.g. “on the strength of rodent developmental toxicity at high exposure” and “who were excluded from every current trial” are removed; no dash-trailing clauses remain. |
| 8.5 | Parenthetical qualifiers from the ER bullet — time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely). | 🟢 | Thresholds preserved: “(HbA1c above 7%)” and “(estimated glomerular filtration rate below 30 mL/min/1.73 m²)”. |
| 8.6 | When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol. | N/A | The ER uses no ranking notation inside parentheses in this section. |
| 8.7 | The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no population, condition, or scenario for which the intervention should be avoided, deferred, or used only under specialist supervision. |
🟢 | The section is populated, which is correct because the ER names four populations that should avoid the intervention. |
| 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, so no explanatory HTML comment is required. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Drawn from the six bulleted interactions in the ER Key Interactions & Contraindications section. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | All six interactions carried; none duplicates a contraindication. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Six <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. | 🟢 | Severity, consequence, and mitigation clauses stripped from every ER bullet; only the interaction label remains. |
| 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). | 🟢 | Drug-class parentheticals preserved and trimmed, e.g. “(insulin, sulfonylureas, SGLT2 inhibitors)” and “(nitrofurantoin, trimethoprim-sulfamethoxazole, fosfomycin)”; none dropped entirely. |
| 9.6 | When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol. | N/A | The ER uses no ranking notation inside parentheses in this section. |
| 9.7 | The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no interaction, additive effect, or exposure that changes how the intervention is used. |
🟢 | The section is populated, which is correct because the ER names six 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 section is not empty, so no explanatory HTML comment is required. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Protocol section |
🟢 | Derived from the ER Therapeutic Protocol section. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Standard prevention dose, acute-episode dose, and best time of day are the three actionable levers in that section; the remaining bullets cover competing approaches, incentives, and unstudied modifiers. |
| 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 three or more distinct 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 action variables carry ER-derived content. |
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 | 🟢 | Prevention of recurrence, acute symptom relief, and correction of mannose phosphate isomerase deficiency are the only time-to-effect aspects the ER quantifies. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered as the ER orders the corresponding Low-tier benefits. |
| 11.3 | If less that three distinct time-to-effect aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing. | N/A | Three distinct time-to-effect aspects exist, 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 time variables carry ER-derived content, with values “6 months”, “2 to 4 days”, and “Within weeks”. |
| 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 in Practical Considerations and in the benefit magnitudes, so the row is retained. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | Derived from the ER Expected Benefits section and its tier structure. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four benefit variables present. |
| 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. | 🟢 | Reduced to bare benefit names; magnitudes, conflict markers, and mechanistic text stripped. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical content carried into either tier. |
| 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. | 🟢 | benefits_high and benefits_medium carry style=”display: none” with no empty-state phrasing, matching the ER’s statement that no benefit reaches those tiers. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | Derived from the ER Potential Risks & Side Effects section and its tier structure. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four risk 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. | 🟢 | Reduced to bare risk names; frequencies, pooled risk ratios, and mechanism stripped. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical content carried into any tier. |
| 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 ER risk tiers contain items, so no sub-section needed hiding. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Derived from the ER Monitoring Protocol & Defining Success section. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All six ER table biomarkers listed, with targets and rationale carried verbatim. |
| 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 the ER’s ongoing-monitoring paragraph; no placeholder text. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Derived 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 five qualitative markers listed. |
Issues 08/09/2026 04:31
Pass rate 100.00%. No issues found.