Editorial policy
Numbers before opinion. Every major claim must reference a count, percentage, date, filing or named primary source. Every signal and tracker record carries a source URL and as-of date.
Regional isolation. Global figures are never presented as regional figures without an explicit regional source split. USA and India evidence remains separate.
Vendor claims. Vendor accuracy and outcome figures are always labelled “vendor-reported, not independently evaluated”.
No rumors. Anonymous claims cannot be published as facts. Verified means primary evidence has been reviewed; Reported attributes a named source; Watchlist means a question remains unresolved.
Patient privacy. We never publish or link patient-level or leaked datasets. Public aggregate reporting is reviewed for privacy before publication.
How an edition is built
The OpenClaw collection role retrieves allowlisted public RSS and API sources into an isolated raw queue. The Hermes validation role checks editorial review, dates, regional metadata and schemas, then stages Markdown and JSON for a static Astro build. Isolated native OpenClaw and Hermes runtimes review a sanitized evidence pack. Auditable Node workers harvest feeds and enforce the publication contract. Both roles use the same local model. Exact field comparison against an independently fetched primary-source snapshot, rather than model agreement alone, is required before automated publication.
AI assists collection, drafting and structured validation. Source-constrained primary facts may publish automatically after both native agents and exact-field validation agree. Human editorial approval is required for interpretations, conflicting evidence, privacy questions and regional extrapolation. AI-generated illustration metadata must contain a visible credit stating that the illustration is AI-generated and non-photographic. The current illustration is an AI-generated, non-photo vector diagram with a visible credit.
Staleness & forecasts
Signals older than the configured threshold display STALE. Forecasts specify a testable condition and review date; contradicted and expired entries stay publicly accessible. Uncertainty is part of the record.
Corrections
Corrections appear in place with a date and an explanation of the change. Edition metadata retains the correction history and updates the structured modification date. To report an error, include the edition URL, disputed claim and a primary source in a repository issue for the site operator.
Scope of this demonstration
Every seed record is marked SAMPLE. Reference URLs are genuine source destinations, but the sample scenarios do not assert real incidents, CVEs, counts or organizational outcomes. The sample banner can be disabled in site.config.json; individual sample labels remain until records are replaced.
Disclaimers
This publication provides information, not medical advice, legal advice or investment advice. Consult qualified professionals and primary sources before making decisions.