Editorial Policy
Publication mission
Weavidence Insights publishes evidence-aware, source-grounded writing about public-health practice, epidemiology and study design, analysis and reproducibility, scientific learning, and the design and engineering of the Weavidence ecosystem itself. It exists to be useful on its own — to a reader who never uses a Weavidence product — and to show, rather than merely claim, the reasoning behind how Weavidence is built.
Scope
In scope: methodological explainers, product-and-engineering notes grounded in Weavidence's documented architecture and implementation, and — where sourcing and review can be verified — evidence briefs and worked cases in public health and research methods.
Out of scope: individual clinical guidance, patient-specific recommendations, promotional content whose primary purpose is conversion rather than usefulness, and any claim of outcomes, effectiveness, certification, or external validation that has not actually been demonstrated.
Content types
Weavidence Insights uses six content types, labelled by what a piece actually is:
- Evidence Brief — a bounded synthesis of external evidence;
- Method Guide — a source-grounded approach to a methodological task;
- Worked Case — a concrete, usually synthetic or de-identified example worked through in detail;
- Concept Explainer — one concept and the distinctions needed to use it responsibly;
- Product Note — an inside account of Weavidence's own design, status, or implementation;
- Commentary — clearly interpretive analysis, not presented as settled fact.
A label is not a badge of authority. An Evidence Brief is not a systematic review unless its methods actually meet that standard. A Product Note is not an independent evaluation of Weavidence.
Authorship
Published articles currently use the organizational byline Weavidence (see the author profile). The accountable human operator is identified in the public legal pages. No individual name, title, qualification, affiliation, or reviewer is invented to make a page appear more authoritative.
Where a named person's professional judgment materially shapes a future piece and publication is authorized, the page should identify that role and any relevant conflict plainly.
Review levels
Every published article has a visible review level:
- Editorial — checked for clarity, internal consistency, accurate status language, citation linkage, limitations, and compliance with this policy.
- Methodological — the article additionally applies a methodological standard and its material claims are checked against appropriate external sources.
- Clinical — content could materially inform an individual clinical decision and therefore requires an identified, authorized reviewer before it can be published.
What a review label does — and does not — mean
A review level describes the standard applied to the article. It does not mean independent peer review unless the page names the reviewer and explicitly states that the review was independent. At present, an empty reviewer field means no named external reviewer is being represented.
Methodological review may be performed internally against cited sources. The article should therefore be read as an accountable editorial publication, not as journal peer review, institutional endorsement, or professional certification. Clinical-level content cannot be published without a named reviewer because the consequences of ambiguity are materially higher.
Draft and review-status content is never publicly routed, indexed, listed in the feed, or included in public navigation.
Conflicts of interest
Product Notes are written by the project whose products they describe. That relationship is inherent in the content type and must remain visible. Product claims should be connected to public product pages, documented status, or inspectable implementation where possible. Internal documentation can explain design intent but cannot substitute for independent evidence of effectiveness.
Where an article's framing could commercially benefit Weavidence, that does not invalidate the content, but it increases the need for precise status language, source separation, limitations, and a secondary product connection rather than a sales-led conclusion.
Source expectations
Methodological and public-health claims should use the strongest sources appropriate to the question, normally preferring:
- current official institutional guidance;
- current reporting or methodological standards;
- original research;
- high-quality systematic reviews or consensus reports;
- authoritative methodological references.
A historical source may remain essential, but current guidance or subsequent work should be added when it materially changes interpretation or application. One source is rarely enough for a broad Method Guide. Sources must support the claim where cited, not merely discuss the same topic.
Product Notes may use Weavidence's own documentation and verified code behavior for product-specific facts. They must distinguish current implementation, design intent, and future direction, and must not borrow the evidentiary weight of an external Evidence Brief.
A claim whose source, currency, or applicability cannot be checked remains in
draft or review status.
Examples and data
Worked examples are labelled as synthetic, illustrative, de-identified, or real. Synthetic examples must not be written to imply that a real authority, patient, institution, outbreak, or customer was studied. A real case requires lawful use, appropriate permission, and enough context to avoid misleading interpretation.
Examples should expose assumptions and failure modes rather than manufacture a perfect path to a predetermined conclusion.
Use of AI assistance
Some Insights content is drafted, researched, structured, or edited with AI assistance. AI may propose language, candidate sources, distinctions, and tests; it does not possess editorial authority and does not make publication safe by producing fluent text.
Before publication, material claims must be checked against the cited source, references must be real, source scope and currency must be considered, and the human operator remains accountable for the decision to publish. When the available environment cannot verify an evidence-sensitive claim, the article is held rather than filled with a plausible-looking citation.
Human accountability
A human remains accountable for every published article, correction, status label, and product representation. Publication is a decision supported by evidence and review, not an automatic consequence of a draft existing or a test passing.
Automated validators enforce structural minimums — valid citations, dates, status, topic membership, public-route exclusion, and similar contracts. They do not determine whether a scientific judgment is correct.
Updates and review dates
Articles are updated when:
- a material error is found;
- cited guidance changes;
- a product's documented status or implementation changes;
- a limitation becomes important enough to alter interpretation;
- a scheduled review identifies material new evidence.
A material change updates the modification date and visible revision history.
The last reviewed date means the article was reassessed against its scope and
sources on that date; it is not a guarantee that no newer publication exists.
Corrections
See Corrections for how to report a problem and how material changes are recorded. Corrections should preserve an honest history rather than silently rewriting a claim that materially changed.
Education, not clinical advice
Nothing published on Weavidence Insights is individual clinical advice. Content that discusses health topics does so at the level of method, system design, research, education, or public-health practice. It does not replace competent clinical, legal, ethical, institutional, or regulatory judgment.