Patena
Product · Monitors

Say what matters once. Be told when it changes.

A monitor is a rule your organization writes: these subjects, these places, these domains, this severity, this much evidence, this schedule, these people. Patena runs it against the stream around the clock. Atlas reads every hit before you do, explains it, holds what is not confirmed, and suggests when the rule should change.

Baltic suppliersRunning
Rule
Subjects
Nordfracht GmbHBaltic Rail Cargo+ 2 suppliers
Places
Gdańsk · 40 kmRiga · 40 kmTallinn · 40 km
Domains
UnrestSanctionsInfrastructure
Severity
≥ 1≥ 2≥ 34
Evidence
2 sources, at least oneT1orT2
Score drift
≥ 10in
24h7d30d
Schedule
15 minHourlyDailyOn change
Deliver to
In-appEmail · D. OrlićWebhook · #baltic-desk
Quiet hours
22:00–06:00 UTC, except severity 4
SaveTest against last 7 days
Hits
Open · 3AcknowledgedSnoozed · 1All
Dockworker strike spreads to Gdańsk and Riga terminals
Gdańsk · T1 + 11 T2 · 29 src · 1h · touches Nordfracht GmbH, Baltic Rail Cargo
AcknowledgeSnooze
EU adds Halvard Shipping AS to Annex I; carrier for 2 suppliers
Score drift · Halvard 68 → 74 · 7d · 61 src · 38m
AcknowledgeSnooze
Rail bridge inspection closes Gdańsk port spur for 48 h
Gdańsk · 2 T2 · 6 src · 3h
AcknowledgeSnooze
Reported stoppage at Tallinn terminal
Tallinn · 1 T3 · 20m · below evidence rule, not delivered
Held · unconfirmed
Dockworker strike begins at Gdańsk DCT
Gdańsk · Sunday 09:12 UTC · acknowledged by D. Orlić
Acknowledged
Last run 14:45 UTC · next 15:45 · 312 stories read · 3 matched · 1 held
Atlas on this monitor

The strike hit is the first for this monitor and it meets the rule by a wide margin: two T1 and eleven T2 sources 1. The sanctions hit is a score drift, not a story; the move came from one event on 14 October 2.

I held the Tallinn report: one T3 source, no corroboration 3. If a second source appears, you will get it.

Suggestion: in the last 7 days this rule would have fired 4 times at severity ≥ 2 and 1 time at ≥ 3. The current setting looks right.

1Reuters2Official Journal3ERR · T3
Proposed by Atlas
Add Klaipėda · 40 km
Nordfracht re-routed there twice this month
ApproveNot now
Machine-extracted. Events, entities, places and scores may be delayed or wrong. Verify against cited sources.
Last ingest 14:58 UTC · Lag 47 s

One monitor for a Baltic supply desk: the rule on the left, its open hits in the middle with acknowledge and snooze, Atlas on the right explaining the hits, holding a single-source report, and proposing a new place for the rule. Nothing is added until someone approves.

What a monitor can watch

Rules are explicit and visible. Atlas can draft one from a sentence; a person always saves it.

Baltic suppliersDraft · by Atlas, from one sentence
Subjects
Nordfracht GmbHBaltic Rail Cargo+ 2 suppliers
Places
Gdańsk · 40 kmRiga · 40 kmTallinn · 40 km
Domains
UnrestSanctionsInfrastructure
Severity
≥ 1≥ 2≥ 34
Evidence
2 sources, at least oneT1orT2
Score drift
≥ 10in
24h7d30d
Schedule
15 minHourlyDailyOn change
Deliver to
In-appEmail · D. OrlićWebhook · #baltic-desk
Quiet hours
22:00–06:00 UTC, except severity 4

Subjects, places, domains, severity, evidence

Any combination. A radius on the map, a list of companies, three of twelve domains, severity on the four-bar meter, and how many sources of which tier it takes to count.

74▲+6 · 7d
Hitrule: drift ≥ 10 in 30d · Halvard Shipping AS

Score drift

A monitor can watch the number, not just the news: fire when a subject’s risk score moves by more than a threshold in a window.

In-appalways
Email · D. Orlićseverity ≥ 3
Webhook · #baltic-deskall hits · JSON
Quiet hours22:00–06:00 UTC

Delivery per person

In-app for everyone. Email and webhook per analyst, per severity, with quiet hours. Webhooks carry the full hit as JSON with its citations.

Strike spreads to RigaAcknowledged
Port spur closed 48 hSnoozed · Fri
Tallinn stoppageHeld

Atlas does not repeat what you have seen. Snoozed hits return only if they change.

Acknowledge and snooze

Every hit is a state, not a message. Acknowledge it and Atlas stops mentioning it. Snooze it and it returns only if it changes.

Test · last 7 daysRun

Would have fired 9 times at severity ≥ 2, 1 time at ≥ 3. Atlas: “≥ 3 looks right for this desk.”

Test before you save

Run a rule against the last 7 or 30 days and see how often it would have fired. Atlas reads the result and says whether the threshold looks right.

What Atlas does with your monitors

Drafts from a sentence

“Watch our Baltic suppliers for strikes and sanctions” becomes a full rule with the subjects it found in your organization. You review and save.

Explains every hit

Each hit arrives with a two-sentence explanation, the sources behind it and which part of the rule it met.

Holds what is thin

A story that meets the subject and domain but not the evidence rule is held and shown as unconfirmed, not delivered and not hidden.

Proposes changes

When your subjects move, Atlas notices: a new port, a new carrier, a threshold that fires too often. It proposes; you approve.

Write the first rule with us.

Early access by request. Bring the subjects you track and we will set up the monitors together.