Hummand presents

Alerts

Computed on read, from the acts and receipts that already exist.
No table of their own, no background monitoring.

Category
ProductAlertsFirst minimal version

Situations

A01prova_vencidarecurring presenceevents check.expired and ato.expiradoavailable

Expired proof

A recurring presence expired without renewal.

Recurring presence is the same proof repeated every period, like the annual proof of life; expired means the term passed with no new proof.

The act deadline passed and no new positive presence of the same subject replaced it. It is the only alert that also goes out as an event: check.expired and ato.expirado, on the webhook and in the dashboard notification, reusing the expiry sweep that already existed. No new worker.

What does not exist: an automatic exception proof from the alert. Opening an exception proof is still a request from the client.

Recurring presence
A02ato_fora_de_mandatodelegated actread-onlyavailable

Act outside the mandate

A delegated act was denied by the mandate.

A delegated act is an action taken on someone’s behalf; here, the action asked for more than the authorization that person gave.

The requested action did not fit the scope, the limits or the validity of the mandate, or the mandate had been revoked. The detail carries the reason code, never the content.

It appears when the endpoint is read; it has no event of its own yet.

Mandate
A03ato_esperado_ausentedual operatorread-onlyavailable

Expected act missing

The second position of a dual operator was never opened.

Dual operator requires two different people approving, each with their own proof; the second never started.

The first position finished positive, the group window expired, and the second was never opened. The detail carries the group.

It appears when the endpoint is read; it has no event of its own yet.

A04GET /v1/alertsreadfirst minimal versionavailable

How to read

One endpoint, filter by type, pagination by limit.

The three combined by default and ordered by recency. Computed on the fly from the acts and receipts that already exist, with no table of their own: nothing is monitored in the background, nothing is inferred.

There is no register of a monitored population in this version. The lookup at a vital-status source is synchronous and on the client's request, and the source only triggers the exception proof, never the proof.

See Docs
Notethealertnot to be confused

These are not TheAlert

Alerts are signals from the register of acts; TheAlert is supervision of the actions of AI systems.

TheAlert, Hummand's product and the first initiative of its AI division, reads these signals and does not replace them. It is a start document, in discovery, with no capability in the catalogue yet.

See TheAlert
1.0

Verify a receipt

Paste the JSON and the public key. No account, nothing sent: it runs in your browser.

Open the verifier
2.0

Talk to us

A technical conversation, straight with the people who build it, no sales script.

Contact