The Wire

Record entry · Auto

Postgresql

Entered the record 4 Oct 2026Mentions 20Sources 11Days of coverage 16

Why this name is on the record

Nothing here was hand-picked. Postgresql crossed the platform’s evidence bars on its own counts: 20 mentions across 11 sources over 16 days of tracked coverage · 45% of that coverage sits in a single domain. Those are the numbers that promoted it, kept on the row.

GET record row · published ontology entry "postgresql"

{
  "slug": "postgresql",
  "label": "Postgresql",
  "category": "auto",
  "promotedAt": "2026-10-04",
  "evidence": {
    "mentions": 20,
    "sources": 11,
    "days": 16,
    "concentration": 0.45,
    "standAloneShare": 0.857
  },
  "whereFrom": {
    "level": "evidence bars",
    "label": "20 mentions · 11 sources · 16 days",
    "children": [
      {
        "level": "reports",
        "label": "6 reports from the coverage window",
        "children": {
          "count": 6,
          "unfold": "expand=+1"
        }
      },
      {
        "level": "promotion",
        "label": "The counts themselves",
        "edge": "measured by the ontology promotion pass on 2026-10-04 and kept on the published record row; no human approved them"
      }
    ]
  }
}

Real: the published record row this page is built from, with its where-from tree folded below the first level.

The coverage behind it

Ask the engine about Postgresql＋ Track Postgresql

This name entered the record from tracked coverage, not from an editor: the counts above are the evidence it was promoted on. No momentum read and no market price are shown because neither has been measured for it yet. Informational only — not advice. As of 2026-10-04 · live snapshot.