CRESASTREAM AUTOMATION
All updates →
ANNOUNCEMENT
Private Testing is planned VERY SOON

Selected candidates will soon be able to give the suite a real world test run and provide their feedback and opinions!

← Back to all updates

DEVELOPMENT UPDATE

CRESA Gives Its Alerts Rules of the Road

UPDATEPUBLISHED

CRESA introduces a shared alert routing policy, giving the Suite clearer rules for deciding how incoming alerts should be presented and how different presentation modes interact.

A Framework Needs Rules

Building the Global Alert Framework gave CRESA one place to receive and manage alerts, but centralising them introduced another question: what should actually happen when an alert arrives? Not every event needs to be presented in the same way, and the decision could no longer be scattered across individual alert implementations.

A shared Alert Routing Policy began defining those decisions, giving the framework a consistent set of rules for choosing how an incoming alert should enter the broadcast.

Choosing the Right Presentation

The routing policy allowed CRESA to reason about different presentation paths rather than assuming every event belonged in one universal alert layout. An alert could be directed toward an appropriate presentation mode while the framework retained responsibility for the wider lifecycle around it.

This was an important step toward supporting both distinctive single-alert experiences and situations where several alerts need to be handled together. The presentation could change without requiring the underlying alert system to become a collection of unrelated pipelines.

Handling Competing Events

Routing also needed to account for what was already happening on screen. An incoming alert might arrive while another presentation was active, while alerts were being grouped together or while another part of CRESA temporarily owned the presentation space.

By moving those decisions into policy, CRESA could begin defining predictable behaviour for handoffs, priority and presentation ownership instead of allowing whichever component reacted first to decide what happened.

Separating Decisions From Design

This created an important boundary inside the alert architecture. The routing layer could decide where an alert belongs, while the presentation layer remained responsible for what that alert looks like once it gets there.

That separation opened the door for CRESA to become much more adventurous with individual alert experiences without sacrificing the consistency of the system underneath them.

Back to all updates