Audit: QRS - Hypertonic Saline Nasal Spray for Health & Longevity

Audit conducted on 20/09/2026 22:59 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.	🟢	Spot-checked every populated span: protocol values (ER `Therapeutic Protocol`), time-to-effect values (ER `Practical Considerations`, `Expected Benefits`, `Monitoring Protocol & Defining Success`), gates (ER `Key Interactions & Contraindications`), monitoring table (ER biomarker table, verbatim), qualitative list (ER qualitative bullets, verbatim).
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.	🟢	“Certainty is low” mirrors ER `Conclusion` “reviewers rate the certainty as low”; time_2_sub “rest on low-quality evidence” is verbatim ER.
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 ER’s “⚠️ Conflicted” marker on the common-cold benefit is carried as “(conflicted)”; contraindication carve-out “unless the surgical team specifies rinses” is preserved.
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.	🟢	Gate items come only from `Key Interactions & Contraindications`; risks only from `Potential Risks & Side Effects`; protocol sub-text only from `Therapeutic Protocol`. No Benefit-/Risk-Modifying Factor content appears anywhere.
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, citations, author names, NCT IDs or brand names (NeilMed, Ayr, Ocean, Xlear) appear in the QRS at all.
1.6	The QRS does not introduce new attributions.	🟢	No attributions 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.	🟢	Measured, evidence-weighted register matching the ER.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Benefits and risks are both stated plainly with tier weighting.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Statements are descriptive of practice (“Split dosing is standard”, “Older adults often need 1.5–2% rather than 3%”).
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperatives or directives; cadence and timing are reported as observed practice.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No occurrences of recommend/advise/should-you constructions.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere in the file.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Clinical terms retained are the ER’s own and are required by 2.15; lede uses plain equivalents (“hay fever”, “long-standing sinus inflammation”, “brain infection”).
2.8	Information is presented in a concise and very compact manner	🟢	Gate and tier items are stripped to the key fact; sub-cells carry at most three short clauses.
2.9	It DOES NOT address the reader directly	🟢	Confirmed — no direct address.
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.	🟢	Protocol, monitoring targets and tolerability signals are pitched at self-directed implementers.
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.	🟢	Water-sourcing constraint, buffering, split dosing and a six-marker monitoring panel all assume 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.	🟢	Includes specialist markers (saccharin transit time, PNIF) that a general-population sheet would omit.
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.	🟢	Low certainty and the hypertonic-versus-isotonic ambiguity are surfaced in the lede rather than buried.
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.	🟢	Title uses “for Health & Longevity”; the string “anti-aging” does not occur.
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.	🟢	Route of administration is given as “administered intranasally” in the lede (ER `Conclusion` wording); body uses “Epistaxis”, “Sodium chloride”, “Intranasal corticosteroids”.

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 the template byte-for-byte (lines 446, 492, 542, 572, 597, 626, 652, 759; table headers lines 656-658).
3.2	All “<span data-qrs-var=”NAME”>…</span>” from the [qrs_template] are present in the the QRS.	🟢	All 31 fixed-name spans present, plus the repeatable `marker_#_*` expanded to 1–6 and `qualitative_item_#` expanded to 1–7.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The three non-variable spans (`website="evidence_review"`, `website="audit"`, `website="full_review"`) are unchanged from 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 ER section mapped onto the QRS is empty; every source section is populated.
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/2/3_label are “Standard regimen”, “Large-volume irrigation approach”, “Best time of day” — verbatim ER `Therapeutic Protocol` bold labels.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Protocol labels verbatim; marker names verbatim from the ER biomarker table; tier and column labels fixed.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No pictographic characters in the file; the ER’s “⚠️ Conflicted” marker is rendered as plain text “(conflicted)”.
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.	🟢	Print rules pin A4 with 12 mm padding; every section is condensed to the per-section budget (6 contraindications, 8 interactions, four one-line tiers per card, one sub-line per protocol cell) and nothing is carried over beyond what items 8.5/9.5/14.2/15.2 mandate.

5. Metadata

#	Description	Result	Comments
5.1	The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content.	🟢	Lines 2–14, immediately after the doctype and before the template banner comment at line 16.
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 `---` line 3, closing `---` line 13; preamble text “QRS — Metadata (invisible, parsed by audit tooling)” sits before the opener.
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.	🟢	Wholly inside an HTML comment; no metadata value is echoed into the body.
5.4	All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting.	🟢	Only `duration: "00:03"` is quoted, and it contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: `er_filename: hypertonic_saline_nasal_spray_2026-0920-1948_Opus_ER.md`.
5.6	Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]”	🟢	Line 5: `qrs_prompt_version: 26.9.11`, matching the 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)	🟢	Line 6: `qrs_creation_date: 2026-0920-2251`.
5.8	The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]”	🟢	Line 7: `qrs_creator_ai_nickname: Opus`.
5.9	The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT)	🟢	“Opus” — single word, no version.
5.10	The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]”	🟢	Line 8: `qrs_creator_ai_fullname: Opus 5`.
5.11	The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier (e.g., Opus 4.6, Sonnet 3.2, Grok 4.5, Gemini 3.1, ChatGPT 5.4)	🟢	“Opus 5” — nickname plus version, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the on-disk filename exactly.
5.13	All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting.	🟢	Re-verified across all nine keys; no stray whitespace or unnecessary quoting.

#	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: “Hypertonic Saline Nasal Spray for Health & Longevity - Quick Reference Sheet”.
6.2	[header_topic] is set to the [canonical_topic] of the ER `frontmatter`, with HTML entities encoded as needed (e.g., `&` for `&`)	🟢	Line 417: “Hypertonic Saline Nasal Spray for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	2026-0920-2251 → “09/20/2026” (line 421).
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “Opus 5”.
6.5	No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker.	🟢	Header holds only the title and the template subline; the ER’s “Also known as” line 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	🟢	Compresses all three `Conclusion` paragraphs: mechanism, benefit set, certainty, cost.
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` sentence (mechanism ¶1; hay fever / sinus inflammation / medicine sparing / post-surgical crusting ¶1; low certainty ¶2; burning, nosebleeds, tap-water infection ¶3).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “hay fever”, “long-standing sinus inflammation”, “allergy medicines”, “crusts”, “brain infection” replace the technical classifications.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	Only the generic “Pooled trials support…”.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numbers of any kind in the lede.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER `Key Interactions & Contraindications` section	🟢	Sourced from the “Populations who should avoid Hypertonic Saline Nasal Spray” list.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All six ER population bullets are present, in ER order.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Six `<li>` elements inside the span (lines 575–592).
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.	🟢	The ER’s “People with a…” / “Anyone unable to…” framing is stripped to the bare condition; 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).	🟢	“within 12 weeks”, “past 6 weeks”, “below 50 × 10⁹/L”, “past 3 months”, “under 2 years”, “1-micron-filtered” and the surgical-team carve-out are all retained.
8.6	When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol.	N/A	The ER uses no ranking notation 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 does identify such populations and the section is correctly populated, not 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. <!– empty: ER names no population that should avoid the intervention –>	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	🟢	Sourced from the eight interaction bullets of that ER section.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All eight interaction bullets present; none duplicates a contraindication.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Eight `<li>` elements inside the span (lines 600–616).
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 “— beneficial, monitor” / “— caution” tail and every “Mitigation:” sentence is stripped; only the agent class and its drug list remain.
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 six ER example-drug lists are preserved; only the lay glosses inside the parentheses (“anti-inflammatory nasal sprays:”, “sprays that shrink swollen lining:”, “drugs that stop platelets clumping:”) are trimmed.
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 does identify interactions and the section is correctly populated, not empty.
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. <!– empty: ER names no interaction that changes how the intervention is used –>	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 trace to ER `Therapeutic Protocol`.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER `Protocol` section	🟢	Standard regimen (dose and concentration), large-volume irrigation approach (delivery format), and best time of day (timing) are the three decision-bearing bullets.
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 eleven 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.	🟢	Sub-lines draw on the ER’s “Single versus split dosing”, “Age-related considerations” and “Pre-existing conditions” bullets; no placeholder text.

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	🟢	Symptom improvement (4 weeks – 2 months) and congestion relief (minutes) are the ER’s own “Time to effect” bullet; sinonasal quality of life (3–6 months) comes from the `Expected Benefits` magnitude data.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered by ER benefit tier: allergic-rhinitis symptom relief (High) → chronic rhinosinusitis symptoms and sinonasal quality of life (High) → congestion relief (symptomatic, untiered).
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 are available, 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.	🟢	Each sub-line is ER-sourced, including the 8-week reconsideration point and the 10–20 minute contact window.
11.5	If the ER does not provide any information on time to effect, the section is removed completely from the `Protocol Panel`	N/A	The ER does provide time-to-effect information, so the section is retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER `Expected Benefits` section	🟢	All eight ER benefit headings are represented across the four tiers.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present and populated (lines 544, 551, 554, 560).
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 the ER’s own headings; all Magnitude paragraphs, confidence intervals and study attributions are dropped.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No ER parenthetical is carried through; “(conflicted)” is the plain-text rendering of the ER’s own “⚠️ Conflicted” heading marker, required by 1.3 and 4.4.
12.5	If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing.	N/A	All four tiers carry at least one ER item.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER `Potential Risks & Side Effects` section	🟢	All eight ER risk headings are represented across the four tiers.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present and populated (lines 628, 631, 634, 640).
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 the ER’s own headings; the 32%/13% burning figures, the 23% epistaxis figure and the Louisiana case detail are all dropped.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	The ER’s “(nosebleed)” gloss on Epistaxis and all Magnitude parentheticals are stripped.
13.5	If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing.	N/A	All four tiers carry at least one ER item.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER `Monitoring` section	🟢	Sourced from ER `Monitoring Protocol & Defining Success`.
14.2	All measurable/quantifiable biomarkers from the `Monitoring` section are listed	🟢	All six ER table rows present with names, targets and rationales verbatim (SNOT-22, TNSS, PNIF, saccharin transit time, blood eosinophil count, total IgE).
14.3	[monitoring_cadence] is populated with the monitoring cadence/frequency derived from the ER `Monitoring` section. It is not left with placeholder text or empty.	🟢	Line 750: baseline on two separate days, then 4 weeks, 8 weeks, and every 3–6 months, with the post-surgical endoscopy exception — all ER-sourced.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER `Monitoring` section	🟢	Sourced from the ER’s qualitative-marker bullet list.
15.2	All subjective/qualitative biomarkers from the `Monitoring` section are listed	🟢	All seven ER qualitative bullets present, verbatim and in ER order.

Issues 20/09/2026 22:59

Pass rate 100.00%. No issues found.