Entity

Vail

A topic on our watch list — we track its coverage across 3 coverage verticals, including Defense Tech Startups, Media Entertainment and Sacramento California Business.

As of 3 Nov 2026Last evidence 1 Nov 2026

What is happening now

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

What changed

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

How well we know this

32 documents · 18 publishers · 0% contain a typed assertion · last evidence 1 Nov 2026

  • Gap: assertion coverage 0: about 100% of mentions carry no typed assertion
  • Gap: 1 receipt withheld: no source link (the same rule the topic record applies)

In this snapshot’s daily coverage:

Reported alongside Vail

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.

ArizonaOracle
  • Arizona · 10 shared documents
  • Clifton · 9 shared documents · no page of its own yet
  • Tucson · 9 shared documents · no page of its own yet
  • Gila · 8 shared documents · no page of its own yet
  • Oracle · 8 shared documents
  • Pinal · 8 shared documents · no page of its own yet
  • Santa Cruz · 8 shared documents · no page of its own yet

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

For developers

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

{
  "name": "vail",
  "label": "Vail",
  "asOf": "2026-11-03",
  "mentions": 3,
  "domains": 3,
  "node": {
    "id": "sb:e/d2c5fd8e67ec765ce0921f4a",
    "schema": "sb.node.v1",
    "rest": "https://sigb.ai/api/v1/node/e/d2c5fd8e67ec765ce0921f4a",
    "knowledgeCutoff": "2026-11-03T15:51:23.084798+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-03T15:51:23.084798+00:00",
    "changes": 0
  },
  "whereFrom": {
    "level": "counts",
    "label": "3 mentions across 3 domains",
    "children": [
      {
        "level": "reports",
        "label": "5 reports drawn on this page, each with its link",
        "children": {
          "count": 5,
          "unfold": "expand=+1"
        }
      },
      {
        "level": "domains",
        "label": "3 coverage domains",
        "children": {
          "count": 3,
          "unfold": "expand=+1"
        }
      }
    ]
  }
}

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

Events involving Vail

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

Walk the record from Vail

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.

Vail

Entity.

Evidence
32 documents · 18 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 1 Nov 2026
Measured
0% of mentions say something specific about it; the rest only name it
As of
3 Nov 2026
7 links from here

Who it moves with: the 7 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 3 Nov 2026.

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