<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Weavidence Insights</title>
    <link>https://www.weavidence.com/insights</link>
    <atom:link xmlns:atom="http://www.w3.org/2005/Atom" href="https://www.weavidence.com/feed.xml" rel="self" type="application/rss+xml" />
    <description>Public health, research methods, and the systems behind reliable evidence.</description>
    <language>en</language>
    <lastBuildDate>Tue, 28 Jul 2026 00:00:00 GMT</lastBuildDate>
  <item>
    <title>How to evaluate whether a surveillance system is useful</title>
    <link>https://www.weavidence.com/insights/how-to-evaluate-whether-a-surveillance-system-is-useful</link>
    <guid isPermaLink="true">https://www.weavidence.com/insights/how-to-evaluate-whether-a-surveillance-system-is-useful</guid>
    <description>A surveillance system is useful only when it supports its stated decisions with data that are timely, sufficiently complete, interpretable, and sustainable. Evaluation is a purpose-led assessment of trade-offs, not a single score.</description>
    <pubDate>Tue, 28 Jul 2026 00:00:00 GMT</pubDate>
    <category>Method Guide</category>
  </item>
  <item>
    <title>How Weavidence Journey turns decisions into a protocol</title>
    <link>https://www.weavidence.com/insights/how-weavidence-journey-turns-decisions-into-a-protocol</link>
    <guid isPermaLink="true">https://www.weavidence.com/insights/how-weavidence-journey-turns-decisions-into-a-protocol</guid>
    <description>A finished-looking protocol and a protocol whose design reasoning survives review are different documents. Journey is built to produce the second one.</description>
    <pubDate>Tue, 28 Jul 2026 00:00:00 GMT</pubDate>
    <category>Product Note</category>
  </item>
  <item>
    <title>Human review as a governance layer for AI-supported evidence work</title>
    <link>https://www.weavidence.com/insights/human-review-as-a-governance-layer-for-ai-supported-evidence-work</link>
    <guid isPermaLink="true">https://www.weavidence.com/insights/human-review-as-a-governance-layer-for-ai-supported-evidence-work</guid>
    <description>&quot;AI-powered&quot; describes what a system uses. It does not describe who is accountable for what it produces. Weavidence treats that as a design boundary, not a caveat.</description>
    <pubDate>Tue, 28 Jul 2026 00:00:00 GMT</pubDate>
    <category>Product Note</category>
  </item>
  <item>
    <title>Scientific learning should teach reasoning, not only facts</title>
    <link>https://www.weavidence.com/insights/scientific-learning-should-teach-reasoning-not-only-facts</link>
    <guid isPermaLink="true">https://www.weavidence.com/insights/scientific-learning-should-teach-reasoning-not-only-facts</guid>
    <description>A completion record and evidence of demonstrated competence are different claims about a learner. Weavidence Academy is built around keeping that difference visible.</description>
    <pubDate>Tue, 28 Jul 2026 00:00:00 GMT</pubDate>
    <category>Product Note</category>
  </item>
  <item>
    <title>Turning a public-health problem into an answerable research question</title>
    <link>https://www.weavidence.com/insights/turning-a-public-health-problem-into-an-answerable-question</link>
    <guid isPermaLink="true">https://www.weavidence.com/insights/turning-a-public-health-problem-into-an-answerable-question</guid>
    <description>A public-health concern becomes researchable only after its population, exposure or intervention, comparator, outcome, and time frame are explicit — and after the question is tested for feasibility, relevance, ethics, and decision value.</description>
    <pubDate>Tue, 28 Jul 2026 00:00:00 GMT</pubDate>
    <category>Method Guide</category>
  </item>
  <item>
    <title>What counts as evidence of demonstrated competence?</title>
    <link>https://www.weavidence.com/insights/what-counts-as-evidence-of-demonstrated-competence</link>
    <guid isPermaLink="true">https://www.weavidence.com/insights/what-counts-as-evidence-of-demonstrated-competence</guid>
    <description>Competence cannot be inferred from attendance, completion, or one successful test. It requires evidence that knowledge can be selected and applied in unfamiliar situations, demonstrated across suitable tasks, and interpreted through a defensible assessment programme.</description>
    <pubDate>Tue, 28 Jul 2026 00:00:00 GMT</pubDate>
    <category>Concept Explainer</category>
  </item>
  <item>
    <title>What makes an analytical workflow reproducible?</title>
    <link>https://www.weavidence.com/insights/what-makes-an-analytical-workflow-reproducible</link>
    <guid isPermaLink="true">https://www.weavidence.com/insights/what-makes-an-analytical-workflow-reproducible</guid>
    <description>Reproducibility requires more than saved code. The exact data state, transformations, software environment, parameters, randomness, manual decisions, and expected outputs must be identifiable — and the workflow must be independently rerunnable within legitimate access constraints.</description>
    <pubDate>Tue, 28 Jul 2026 00:00:00 GMT</pubDate>
    <category>Method Guide</category>
  </item>
  <item>
    <title>Why traceability matters in AI-supported evidence systems</title>
    <link>https://www.weavidence.com/insights/why-traceability-matters-in-ai-supported-evidence-systems</link>
    <guid isPermaLink="true">https://www.weavidence.com/insights/why-traceability-matters-in-ai-supported-evidence-systems</guid>
    <description>A software artifact that looks correct and a software artifact that is inspectable and independently checkable are different claims. Traceability is what turns the first into the second.</description>
    <pubDate>Tue, 28 Jul 2026 00:00:00 GMT</pubDate>
    <category>Product Note</category>
  </item>
  <item>
    <title>Why Weavidence Lab separates computation, interpretation, and review</title>
    <link>https://www.weavidence.com/insights/why-weavidence-lab-separates-computation-interpretation-and-review</link>
    <guid isPermaLink="true">https://www.weavidence.com/insights/why-weavidence-lab-separates-computation-interpretation-and-review</guid>
    <description>A single &quot;run analysis&quot; button that returns a chart hides more than it reveals. Lab keeps quality, computation, and review as distinct, inspectable stages instead.</description>
    <pubDate>Tue, 28 Jul 2026 00:00:00 GMT</pubDate>
    <category>Product Note</category>
  </item>
  <item>
    <title>Why Weavidence separates learning, study design, and analysis</title>
    <link>https://www.weavidence.com/insights/why-weavidence-separates-learning-design-and-analysis</link>
    <guid isPermaLink="true">https://www.weavidence.com/insights/why-weavidence-separates-learning-design-and-analysis</guid>
    <description>Academy, Journey, and Lab could have been one bundled application. They are three connected products instead, and the separation is a deliberate design choice, not an accident of scope.</description>
    <pubDate>Tue, 28 Jul 2026 00:00:00 GMT</pubDate>
    <category>Product Note</category>
  </item>
  </channel>
</rss>
