Pulse and attention items

Attention item

An attention item is one concrete thing about a project that may need you to act. It has:

Field	Meaning
severity	attention or critical
category	Revenue · Analytics · Development · Infrastructure · Integration
title and detail	“Build failing on main” — “build-and-test failed twice since yesterday”
source	which provider and account it came from
detected	the sync day it first appeared
state	open, resolved or dismissed
deep link	straight to the workflow run, the PR list, the RevenueCat chart

Items come from plain rules, evaluated after every sync. The assistant may explain them; it never invents them.

The rules

Rule	Category	Severity	Resolves
GitHub Actions workflow failed on the default branch	Development	critical	automatically, when a later run of that workflow succeeds
No successful run after a failed one, for more than a day	Development	critical	automatically
Pull request waiting for review longer than 3 days	Development	attention	automatically, when merged or closed
Issue labelled critical / high / P0 open	Development	attention	automatically, when closed
Revenue materially below baseline	Revenue	attention at −25 %, critical at −50 %	only when you say so
Active users materially below baseline	Analytics	attention at −25 %, critical at −50 %	only when you say so
Integration sync failed	Integration	attention	automatically, when the next sync succeeds
Integration credentials expired	Integration	critical	automatically, when you reconnect

Thresholds are the same for every project. You do not configure them — see why.

Lifecycle

            ┌──────────► resolved  (automatic, or you)
   open ────┤
            └──────────► dismissed (you)

• Rules that can observe the fix resolve their items themselves: the build is green again, the PR is merged, the token works.
• Rules that cannot — “is revenue down for a good reason?” — wait for you. Resolve means “handled”; Dismiss means “not interested”.
• If the same condition happens again after an item was resolved, that is a new item. History stays truthful: “failed twice this week” is two items.

Pulse

A project’s Pulse is one of four states, derived purely from its open attention items:

Pulse	When
Healthy	no open items
Attention	at least one open item, none critical
Critical	at least one open critical item
Unknown	no usable data — never synced, no sources, or every integration broken

Pulse has no rules of its own. If it is red, there is always an item to click. Per-category sub-pulses (Revenue, Development, …) are the same derivation filtered by category.

The Pulse glyph shows its reason: a closed ring for Healthy, one amber segment per open item, and a ring that breaks at a critical segment. Unknown is dashed and uncoloured — it is the absence of information, not a fourth alarm level. More in the design notes.

No configuration

Ubrella deliberately has no alert builder. Every rule above is one an indie developer would write on day one anyway, and a fixed set means a red Pulse means the same thing on every project and for every user. If a rule fires too often for you, tell us — we would rather fix the rule than add a settings page.