Record entry · Auto

C Reactive

What is happening now

Nothing reported: the record holds no registered event and no claim that names this.

How well we know this

23 documents · 14 publishers · 0% contain a typed assertion · last evidence 14 Oct 2026

Gap: assertion coverage 0: about 100% of mentions carry no typed assertion

Added 14 Oct 2026Mentions 20Sources 14Days of coverage 13

Why this name is on the record

C Reactive was added automatically on 14 Oct 2026 after 20 mentions across 14 sources over 13 days. 50% of that coverage came from a single subject area.

Reported alongside C Reactive

Risk Factors · 8 shared documents

For developers

GET https://api.signalbureau.ai/api/registry?slug=c-reactive

{
  "slug": "c-reactive",
  "state": "active",
  "detail": {
    "state": "active",
    "source": "ontology",
    "label": "c-reactive",
    "promotedAt": "2026-10-14",
    "category": "auto",
    "evidence": {
      "mentions": 20,
      "sources": 14,
      "days": 13,
      "concentration": 0.5,
      "standAloneShare": 0.952
    }
  }
}

The record behind this page, as data. The live response also carries the registry date and version.

Walk the record from C Reactive

Open where it comes from, follow a claim or a related name, and use the trail to come back. Every step says what it is, how it stands and when. Machines read the same record.

C-Reactive

Entity.

Evidence: 23 documents · 14 separate publishers · a mention shows the name is in use, not that any claim about it is true
Standing: A name from our starting list; its record is kept up to date automatically from coverage
Time: first seen 8 Sept 2026, last seen 14 Oct 2026
Measured: 0% of mentions say something specific about it; the rest only name it
As of: 15 Oct 2026