Skip to main content

HX113 - News, Alerts, and AI Context

HX113 teaches the Current shared economic-calendar path used by the News window, the built-in NewsEcon indicator, and Rion news context. The calendar is an external internet feed and can be delayed, stale, incomplete, or rate-limited; it is context, not an execution signal.

Lesson 1: Follow The Data Source​

The shared service downloads the FairEconomy.media weekly calendar, normalizes events, converts usable timestamps to Windows local time, and caches results in memory and on disk.

An event can include title, country/currency, impact, forecast, previous value, local event time, and a stable key. Tentative or unusable-time events can be omitted.

Before using an event:

  1. Confirm the News surface reports loaded data.
  2. Note whether the response is fresh or cached.
  3. Confirm the displayed local time against the source when timing is critical.
  4. Verify currency/country and impact filters.
  5. Treat a missing event as unknown, not proof that no event exists.

This feed is not broker market data and is not an authoritative exchange clock.

Lesson 2: Use The News Window​

Open the News window and practice:

  • refresh and read the loading/status message
  • switch among next 24 hours, today, this week, and all loaded events
  • filter by search text, currency, and impact
  • use all/none currency actions
  • close and reopen the window to verify saved filters

When opened from a chart, the title can include the chart instrument. That title provides context; it does not automatically reduce events to only those relevant to the instrument.

Lesson 3: Add NewsEcon To A Chart​

NewsEcon reads the same shared calendar service and draws a chart HUD. Its user-editable groups cover:

  • date scope and maximum displayed items
  • USD-only and impact filters
  • refresh interval
  • alert impact and lead time
  • post-event display time and optional sound
  • HUD background, spacing, colors, font, and offsets

Add the indicator, choose a narrow impact/currency scope, and compare its next event with the News window. Do not add a second network downloader to a custom indicator; reuse the built-in indicator or documented shared context.

Lesson 4: Verify One Alert Per Event​

NewsEcon tracks stable event keys that have already triggered during the running instance. Test with a safe lead time and verify:

  1. the selected impact threshold matches the event
  2. local event time is correct
  3. the optional sound path is valid
  4. the alert occurs once for that instance/event key
  5. chart updates do not repeatedly replay it

An alert is operational awareness. It does not open a trade and is not evidence that a strategy has tested a news rule.

Lesson 5: Ask Rion About Loaded News​

Rion can add structured context from the same calendar service when a prompt asks about news, the economic calendar, or high-impact events.

For a read-only exercise:

  1. Open the News window and note the next high-impact event.
  2. Select the intended chart.
  3. Ask Rion for the next high-impact events relevant to the instrument.
  4. Compare event title, country/currency, impact, and local time with the News window.
  5. Reject invented events or claims that the data came from the broker.

The AI provider receives the supplied news/chart context according to the selected provider path. Review AI Data And Privacy.

Lesson 6: Keep The Local API Boundary Clear​

The Preview Local Desktop API can return structured calendar context to a provisioned integration. Discover the installed route/schema and filtering options from Local Desktop API; do not copy a fixed query-field list from this course into a long-lived client.

The API still depends on the same external calendar service and cache. Token authentication does not make the underlying event feed more current or authoritative.

Lesson 7: Handle Rate Limits And Stale Data​

The shared service spaces requests, backs off after a rate-limit response, and can return stale cached events when a fresh request fails.

When status reports stale, cached, rate-limited, or failed data:

  • stop repeated manual refresh attempts
  • preserve the status and timestamp
  • verify critical events through an approved independent source
  • do not let an agent describe the calendar as current
  • export diagnostics if the state persists unexpectedly

Completion Check​

  • The News window and NewsEcon show the same event source and local-time interpretation.
  • Saved filters restore as expected.
  • One test alert fires once per event key in the running indicator instance.
  • Rion repeats only the supplied calendar context and identifies uncertainty.
  • Rate-limit or stale-cache state remains visible in the workflow.
  • No strategy or order is justified solely by the presence or absence of a calendar event.