Entity

Jdam

A topic on our watch list — we track its coverage across 3 coverage verticals, including Defense Procurement, Defense Tech Startups and Intelligence Surveillance.

As of 10 Nov 2026Last evidence 9 Nov 2026

What is happening now

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

What changed

  • Attention Jdam has 3 mentions in tracked coverage: too few to measure a trend.
  • State No change in coverage state or wire tier recorded since 10 Nov 2026.
  • Claims No claim first reported since 9 Nov 2026.

How well we know this

36 documents · 15 publishers · 0% say something specific about it · last evidence 9 Nov 2026

  • Gap: 0% of mentions say something specific about it; the rest only name it

In this snapshot’s daily coverage:

Reported alongside Jdam

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.

IranNorthern Marian…United StatesChinaPentagonNavy
  • Iran · 24 shared documents
  • Joint Direct Attack · 20 shared documents · no page of its own yet
  • Northern Mariana Islands · 19 shared documents
  • F-35 · 17 shared documents · no page of its own yet
  • Jdams · 17 shared documents · no page of its own yet
  • United States · 17 shared documents
  • China · 15 shared documents
  • Nuclear · 14 shared documents · no page of its own yet
  • Pentagon · 13 shared documents
  • Navy · 12 shared documents

Jdam has 3 mentions in tracked coverage. That is too few to measure a trend. Watch Jdam to hear when coverage grows, or request deeper coverage of Jdam.

On the desk: Defense Desk

For developers

This page is also an object: GET https://sigb.ai/api/v1/node/e/4dcf214de8266778222d5d04 returns the same record as sb.node.v1. Or call the get_entity MCP tool at https://sigb.ai/api/mcp with name jdam.

{
  "name": "jdam",
  "label": "Jdam",
  "asOf": "2026-11-10",
  "mentions": 3,
  "domains": 3,
  "node": {
    "id": "sb:e/4dcf214de8266778222d5d04",
    "schema": "sb.node.v1",
    "rest": "https://sigb.ai/api/v1/node/e/4dcf214de8266778222d5d04",
    "knowledgeCutoff": "2026-11-10T18:52:35.044167+00:00",
    "snapshot": "this deploy's committed data files (commit not exposed in this runtime)"
  },
  "coverageTrend": "too few mentions to measure",
  "history": {
    "since": "2026-11-10T17:27:28.079035+00:00",
    "changes": 0
  },
  "whereFrom": {
    "level": "counts",
    "label": "3 mentions across 3 domains",
    "children": [
      {
        "level": "domains",
        "label": "3 coverage domains",
        "children": {
          "count": 3,
          "unfold": "expand=+1"
        }
      },
      {
        "level": "not shown",
        "label": "The other 3 mentions",
        "edge": "counted daily from tracked coverage; single mentions are not listed one by one"
      }
    ]
  }
}

The figures on this page, as data. The tool returns the full entity record.

Events involving Jdam

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

Walk the record from Jdam

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.

Jdam

Entity.

Evidence
36 documents · 15 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 4 Sept 2026, last seen 9 Nov 2026
Measured
0% of mentions say something specific about it; the rest only name it
As of
10 Nov 2026
10 links from here

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

What is claimed about it (0)

none on file at this cutoff

Situations it is named in (0)

none on file at this cutoff

For machines: this record as JSON

Watch this

Recorded history

No change in coverage state or wire tier recorded since 10 Nov 2026.

Ask about JdamWatch Jdam

Story momentum counts mentions in tracked coverage. Prices are the market’s own, cited with the venue. Informational only, not advice. As of 10 Nov 2026.