Audit: QRS - Vitamin K2 (MK-4 & MK-7) for Health & Longevity

Audit conducted on 11/08/2026 06:18 using AI4L / Opus 5

Iterations

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 populated span traces to ER text: protocol cells to Therapeutic Protocol (ER 370–386), time cells to Practical Considerations “Time to effect” (ER 430), benefit/risk tiers to the ER sub-headings, gates to Key Interactions & Contraindications (ER 318–346), markers and cadence to the Monitoring Protocol & Defining Success table and paragraph (ER 460–478).
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. 🟢 Cautious verdict wording is carried through verbatim, e.g. “no interaction” for direct oral anticoagulants and “monitor”/”caution” tags (QRS 589–612) match ER 318–338; “not applicable otherwise” retained in marker_5_target (QRS 719).
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”). 🟢 Contraindication strength is preserved — pregnancy/breastfeeding at pharmacological MK-4 doses stays a stop item (QRS 577), and the vitamin K antagonist gate keeps its “unless a clinician sets a fixed dose” condition (QRS 570–571).
1.4 The QRS does not relabel an ER fact under a different decision category. A “Benefit-Modifying Factor” from ER section is not surfaced as a “Caution”; a “Risk-Modifying Factor” is not surfaced as a “Side Effect”; etc. 🟢 No content from ER Benefit-Modifying Factors (ER 234–246) or Risk-Modifying Factors (ER 302–312) appears in the gates, benefits, or risks cards; each QRS block draws from its own mapped ER section.
1.5 PubMed IDs, study citations, expert names, clinical trial identifiers (NCT*), and brand names appear in the QRS only if they appear in the source ER for the same fact. 🟢 The QRS carries no PMIDs, author names, NCT identifiers, or brand names; the ER’s “Eisai’s Glakay” (ER 372) was correctly dropped from action_2_sub.
1.6 The QRS does not introduce new attributions. 🟢 No attributions of any kind appear in the sheet.

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-graded register matching the ER, including the ER’s own plain-language Conclusion phrasing reused in at_a_glance.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Quantified targets and doses sit alongside plain-language framing; the sheet states what is known and what is unsettled without discouraging language.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Content is stated descriptively (“Absorption, not timing, drives the recommendation”, QRS 485) rather than as instructions to a patient.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Gates and markers are framed as conditions and readouts; the only advisory sentence is the fixed template disclaimer (QRS 816–818).
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No imperative or advisory constructions in the document’s own voice.
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 🟢 Marker names are spelled out in full rather than abbreviated (e.g., “Dephosphorylated-uncarboxylated matrix Gla protein”, QRS 660; “Estimated glomerular filtration rate”, QRS 759).
2.8 Information is presented in a concise and very compact manner 🟢 Benefits and risks are reduced to tier-tagged clause lists; the twelve-bullet ER protocol is reduced to three action cells.
2.9 It DOES NOT address the reader directly 🟢 Confirmed by full-file check for “you”/”your”; none present.
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. 🟢 Biomarker targets, dose ranges, and structural endpoints assume an actively self-managing reader.
2.11 The target audience is willing to employ lifestyle and behavioral changes as well as follow protocols that may be inconvenient, costly, or require effort. 🟢 Thrice-daily 15 mg MK-4 dosing (QRS 471) and specialist-assay monitoring are presented without hedging about inconvenience.
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. 🟢 Research-grade markers such as dephosphorylated-uncarboxylated matrix Gla protein and coronary artery calcium scoring are presented as routine, which is not a general-population framing.
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. 🟢 at_a_glance foregrounds the evidence gradient and the anticoagulant conflict, the two decision-relevant points for this audience (QRS 434–438).
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; the title uses “Health & Longevity” (QRS 417).
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 plain-language wording in at_a_glance (“blood-thinning drugs”) is taken from the ER Conclusion (ER 506) and is required there by item 7.4.

3. Template Integrity

# Description Result Comments
3.1 The following labels and headings on the QRS are fixed and not modified: Card and section headings: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”; Gate headings: “Contraindications”, “Key Interactions”; Tier labels: “High”, “Medium”, “Low”, “Speculative”; Table column headers in Monitoring: “Marker”, “Target”, “Why” 🟢 All fixed strings match the template byte for byte (QRS 446, 491, 533, 566, 586, 622, 647, 784, 651–653) including the template’s unescaped ampersand in “Risk & Side Effects”.
3.2 All <span data-qrs-var="NAME">...</span> from the [qrs_template] are present in the the QRS. 🟢 All 34 distinct template variables are present; the repeated marker_#_* and qualitative_item_# rows expand to 8 and 4 instances, giving 62 spans total.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 The three non-variable spans website="evidence_review", website="audit", and website="full_review" are unchanged (QRS 423, 426, 440).

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 mapped into the QRS is empty; every benefit tier, risk tier, gate list, protocol, monitoring, and qualitative block has ER content.
4.2 Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label. 🟢 All eleven caution labels reproduce the ER bold labels verbatim including their parenthetical drug lists (QRS 589–612 vs ER 318–338); action labels match ER 370, 372, 378.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Time-to-effect cell labels are drawn from the ER’s own wording in the single “Time to effect” bullet — “carboxylation markers”, “Bone density”, “arterial stiffness” (ER 430).
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 🟩/🟥/🟨/⚠️ markers were all 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 with latitude was condensed: benefits and risks reduced to bare tier headings, the twelve-bullet ER protocol to three cells, contraindications stripped of their definitional glosses, and the two-paragraph cadence text to one sentence. The remaining length is carried by content that other items require verbatim (4.2, 9.5, 14.2).

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. 🟢 Comment opens at QRS line 2, immediately after <!doctype html> on line 1, and closes at line 14 before the template comment on 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 --- at line 3 and closing --- at line 13; the “QRS — Metadata” caption on line 2 precedes the opening delimiter.
5.3 The metadata is not visible in any rendered view of the QRS and is not surfaced by any other element on the sheet. 🟢 Enclosed in an HTML comment; none of its values are echoed by a rendered element other than the independently required header date and model.
5.4 All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. 🟢 Only duration: "00:03" is quoted, correctly, because it contains a colon; all other values are bare and untrimmed of nothing.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: vitamin_k2_mk_4_mk_7_2026-0811-0321_Opus_ER.md (QRS 4) matches the ER’s own filename field (ER 17).
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 (QRS 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-0811-0609 (QRS 6) is in the required format.
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢 qrs_creator_ai_nickname: Opus (QRS 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) 🟢 “Opus” is a single word with no version or qualifier.
5.10 The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” 🟢 qrs_creator_ai_fullname: Opus 5 (QRS 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) 🟢 “Opus 5” is nickname plus version with no trailing qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename: vitamin_k2_mk_4_mk_7_2026-0811-0321_Opus_QRS.html (QRS 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. 🟢 Re-verified across all ten keys; formatting is consistent and no stray quoting or padding is present.

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., &amp; for &) 🟢 “Vitamin K2 (MK-4 & MK-7) for Health & Longevity - Quick Reference Sheet” (QRS 22) matches canonical_topic (ER 8) with both ampersands encoded.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 “Vitamin K2 (MK-4 & MK-7) for Health & Longevity” (QRS 417).
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 2026-0811-0609 renders as “08/11/2026” (QRS 421).
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 “Opus 5” (QRS 425) matches 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 (QRS 415–428) is the template subline only; the ER’s “Also known as” list (ER 30) was 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 (ER 502–506) into what the compound is, how the evidence grades out, and the one decision-blocking conflict.
7.2 [at_a_glance] is no longer than 60 words 🟢 58 words (QRS 434–438).
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 “beyond dispute”, “well supported”, “genuinely unsettled”, and “rests entirely on population studies” map one-to-one onto ER 504; the tolerability and anticoagulant clauses map onto ER 506.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms; “artery hardening” and “blood-thinning drugs” stand in for calcification and vitamin K antagonists.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial names, years, or sample sizes appear.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No numeric results; the ER’s magnitudes were all left out.

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 Vitamin K2 (MK-4 & MK-7)” list at ER 340–346.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All five ER populations are present and none was added (QRS 569–581).
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Five discrete <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 stripped: “where safety data are absent” (ER 345) and the “a measure of kidney filtering capacity” gloss (ER 346) are both gone; 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). 🟢 “(time in therapeutic range below 60%)”, “(above 1 mg daily)”, and “(estimated glomerular filtration rate under 30 mL/min/1.73 m²)” are all retained (QRS 574, 577, 579–580).
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 parentheticals contain no ranking notation; they carry only thresholds and dose values.
8.7 The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no population, condition, or scenario for which the intervention should be avoided, deferred, or used only under specialist supervision. 🟢 The ER names five such populations, and the section is correspondingly populated rather than empty.
8.8 If the section is left empty, an HTML comment inside the [stop_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. <!-- 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 eleven interaction bullets at ER 318–338.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All eleven interactions are carried; none duplicates a stop item, whose entries are population-scoped (mechanical heart valve, unstable INR) rather than the interaction itself.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Eleven discrete <li> elements inside the caution_items span (QRS 589–612).
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. 🟢 Each item is reduced to label plus verdict; every mechanistic sentence and mitigation instruction from ER 318–338 (e.g., “Dosing is separated by at least four hours”) was stripped.
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 parenthetical drug lists and effect qualifiers are retained intact, including “(apixaban, rivaroxaban, dabigatran, edoxaban)” and “(additive effect on clotting)”.
9.6 When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol. N/A The ER’s interaction parentheticals are already plain comma-separated lists with no ranking symbols.
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 interactions, and the section is correspondingly populated rather than 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 the ER Therapeutic Protocol section (ER 368–392).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 The two dosing regimens that define the intervention (ER 370, 372) plus administration timing (ER 378); the remaining nine bullets are refinements to those three.
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. 🟢 Nine of nine spans populated; e.g. action_1 “Low-dose MK-7 approach / 100–200 µg daily / All-trans MK-7, once daily. 180 µg carries the strongest three-year outcome data.” draws on ER 370 and ER 382.

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 🟢 Carboxylation markers, bone density, and arterial stiffness are exactly the three latencies the ER gives (ER 430).
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Order follows the ER benefit tiers: carboxylation restoration and bone density are both High (ER 168, 174), arterial elasticity is Medium (ER 188).
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 latencies, 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. 🟢 Nine of nine spans populated with the ER’s own values — 2–4 weeks with an 8–12 week plateau, and 2–3 years for both structural endpoints (QRS 497–526).
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 (ER 430), so the section is correctly retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All four tiers map to the ER Expected Benefits sub-headings (ER 166–228).
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present and populated (QRS 535–559).
12.3 Items are as concise as possible. No explanations, no elaborations, no effect sizes, no qualifiers, no attributions, no citations, no study details, no mechanistic explanations, etc. Just the key fact. 🟢 Each tier is a bare semicolon-separated list of ER sub-headings; every “Magnitude:” line, trial reference, and “⚠️ Conflicted” qualifier was dropped.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses remain in any benefits span.
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 ER benefit tiers contain items, so no span needed hiding.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All four tiers map to the ER sub-headings at ER 254–296.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present and populated (QRS 624–641).
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 ER sub-heading text; the INR mechanism, pooled risk ratios, and “⚠️ Conflicted” marker on breast cancer risk were all dropped.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses remain in any risks span.
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 ER risk tiers contain items, so no span needed hiding.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Marker names, targets, and “Why” text are taken from the ER Monitoring Protocol & Defining Success table (ER 462–471).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All eight ER table rows appear as marker_1 through marker_8, in ER order, with the “Optimal Functional Range” and “Why Measure It?” values preserved.
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 (QRS 774–778) with the 3-month/12-month marker recheck, 2-year bone scan, 3–5 year calcium score, and weekly INR schedule from ER 460.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Taken from the “Qualitative markers worth tracking alongside the laboratory set” list at ER 473–478.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All four ER qualitative markers appear as qualitative_item_1 through qualitative_item_4 (QRS 786–808).

Issues 11/08/2026 06:18

Pass rate 100.00%. No issues found.