March 2026 Release Archive

← Back to the latest release

March 2026: Y2SOURCE Event Provenance Engine

Y2 intelligence reports now feed the Situation Room. The Y2SOURCE extraction pipeline extracts structured geopolitical events from reports generated by the Y2 Orchestration Engine. Each event includes provenance metadata linking it to the source report.

What changed

Event extraction from reports

• Every Y2 intelligence report is now processed through a structured extraction pipeline that identifies discrete geopolitical events, including conflicts, political shifts, economic signals, and cyber incidents.
• Extracted events include geographic coordinates, severity, and temporal analysis such as ongoing, past, forecast, or analysis.
• Named-entity recognition captures people, organizations, countries, and locations referenced in each event.

Situation Room integration

• Y2-sourced events appear on the interactive globe alongside external OSINT feeds.
• Y2 markers distinguish report-derived intelligence from direct provider observations.
• Standard map filters such as category, severity, and region apply to Y2 events.

Provenance metadata

• Each Y2 event carries provenance metadata that connects the observation to report-derived extraction context.
• Confidence scores from 0 to 1 reflect the extraction model's certainty about each event.
• Temporal classification indicates whether an event is ongoing, historical, forecast, or analytical.

Query report-extracted events

GET /api/v1/osint/y2-events returns only observations with sourceType: "y2_report". It accepts category, severity, countryCode, limit, and cursor; Bearer-token requests require the osint:read scope.

curl -H "Authorization: Bearer y2_your_key" \
  "https://api.y2.dev/api/v1/osint/y2-events?category=conflict&severity=high&limit=10"

The current JSON response uses stable public IDs and cursor pagination:

{
  "data": [
    {
      "id": "obs_7Jf2kQ9mV4sP",
      "type": "observation",
      "sourceType": "y2_report",
      "title": "Escalation in Eastern Mediterranean Naval Activity",
      "description": "Multiple carrier groups repositioned...",
      "category": "conflict",
      "severity": "high",
      "coordinates": { "lat": 34.5, "lon": 33.0 },
      "geometry": { "type": "Point", "coordinates": [33.0, 34.5] },
      "locationName": "Eastern Mediterranean",
      "countryCode": "CY",
      "region": "middle_east",
      "eventTime": 1784023200000,
      "eventTimeISO": "2026-07-14T10:00:00.000Z",
      "occurredAt": "2026-07-14T10:00:00.000Z",
      "observedAt": null,
      "url": "https://example.com/source",
      "provenance": {
        "source": "y2_report",
        "confidence": 0.92
      }
    }
  ],
  "meta": {
    "pageCount": 1,
    "limit": 10,
    "hasMore": false,
    "nextCursor": null
  },
  "links": {
    "self": "/api/v1/osint/y2-events?category=conflict&severity=high&limit=10",
    "next": null
  }
}

See the generated GET /osint/y2-events reference for all parameters, representations, and error responses.

How the pipeline works

The pipeline identifies structured events, resolves locations and entities, and upserts each event as an observation with sourceType: "y2_report". Internal lineage retains the report, model, and confidence context used during extraction.

Profile sharing defaults

Community profile sharing is now enabled by default when creating new profiles. You can still turn sharing off in profile settings.

Situation Room map enhancements

• Y2 report-sourced events now render with distinct Y2-branded markers on the globe.
• Map-layer rendering for Y2 provenance events was improved.