Record entry · Australia

Firmus

Added 30 Sept 2026Mentions 23Sources 8Days of coverage 15

Why this name is on the record

Firmus was added automatically on 30 Sept 2026 after 23 mentions across 8 sources over 15 days. 56% of that coverage came from a single subject area.

Who Firmus moves with

Names most often reported alongside it; bigger circles and heavier lines mean more shared documents. A dashed circle has no page of its own yet.

AustraliaAIOpenAIIndonesiaNvidiaMalaysiaSingaporeMeta
  • Australia · 51 shared documents
  • AI · 45 shared documents
  • OpenAI · 20 shared documents
  • Indonesia · 17 shared documents
  • Nvidia · 16 shared documents
  • Malaysia · 15 shared documents
  • Tasmania · 14 shared documents · no page of its own yet
  • Singapore · 12 shared documents
  • AI factory · 11 shared documents · no page of its own yet
  • Meta · 11 shared documents

For developers

GET https://sigb.ai/api/registry?slug=firmus

{
  "slug": "firmus",
  "state": "active",
  "detail": {
    "state": "active",
    "source": "ontology",
    "label": "firmus",
    "promotedAt": "2026-09-30",
    "category": "australia",
    "evidence": {
      "mentions": 23,
      "sources": 8,
      "days": 15,
      "concentration": 0.565,
      "standAloneShare": 0.719
    }
  }
}

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

Walk the record from Firmus

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.

Firmus

Entity.

Evidence
59 documents · 16 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 3 Sept 2026, last seen 7 Oct 2026
Measured
27% of mentions say something specific about it; the rest only name it
As of
8 Oct 2026
11 links from here

Who it moves with: the 10 names are in the map above.

What is claimed about it (1)

  • Reported by two: Reported by two sources that did not copy each other.

Situations it is named in (0)

none on file at this cutoff

For machines: this record as JSON

Watch this