The trust loop: connected tools feed an evidence-backed record, a person decides, and the verified outcome improves future proposals without removing human control.
Five questions every signal must answer
What happened?
A concrete event or change, tied to the affected customer, invoice, deal or account.
What did Hive check?
The source and the field behind each reading — up to six readings per signal.
Why does it matter?
Plain-language reasoning, the stake, and any known limitation.
Who decides?
A person with the right role, in the review panel. Nothing runs until it is approved or within granted autonomy.
What happened next?
A receipt in the audit log and, where it can be checked, the outcome.
Evidence, not assertion
Every reading on a signal names its source connector and field, carries a typed value (money, a count, days, a date, a ratio), and says how it was compared: “past your threshold”, “against your usual”, “corroborated”, “correlated” or “cited”. Where Hive compares against a baseline, it shows the baseline. Confidence is labelled honestly. A figure marked “Hive’s own estimate” is the model’s self-assessment; a figure marked “measured” comes from observed results. Hive does not present one as the other. Links to source records are always secure HTTPS links without credentials. They open the record in the source tool, where that tool’s own access rules apply. Hive never gives demo or sample data evidence status in a real workspace. A row that only matches Hive’s built-in demo data belongs to no member there, so it is not shown, notified or acted on as evidence. Demo data is meant for the demo workspace.Say what could not be checked
If a source is unavailable, a permission is missing, or a piece of evidence expired, Hive says so. For example, if an invoice is overdue but support history cannot be read, the safe proposal is to review the account before contacting the customer — not to pretend there is no dispute. When Hive cannot see the conversation behind an email proposal, the review panel says Conversation context unavailable — review the source before sending. Hive never marks a signal resolved without fresh evidence. If a re-check fails or the provider asks Hive to slow down, nothing changes: the signal stays open, and if Hive cannot confirm it, the row reads Can’t confirm — coverage incomplete. See How Hive closes a signal on its own. The same honesty applies to what Hive did. A signal’s label names the furthest step Hive has evidence for (see Where the situation stands):- A saved draft never reads as sent, and a draft invoice is never counted as sent.
- A send reads Sent (Gmail accepted it) when the provider accepted it, never Delivered: no connector reports delivery today.
- A failed send on a signal you handled reads Action failed, not Resolved.
- A send stuck for more than 15 minutes with nothing holding it reads Can’t confirm it was sent. Check the mailbox or tool before you retry.
- An approval from an earlier occurrence of a signal that came back is not shown as waiting, and a declined action shows no label.
- The outcome line under a signal always matches its label.
One situation, one record
Repeated detections of the same situation update one signal rather than creating a stream of disposable alerts: the row shows how many times it has been seen and when it was first raised. That holds when you reconnect an account, and when a resolved mail wait comes back. Related signals that fire together are grouped, within one person’s connected accounts. See One situation, one signal. A situation that runs over weeks becomes a matter, which keeps its timeline, decisions and next step together.Learning without losing control
Hive improves from your team’s feedback in ways you can see:- Dismissal reasons change future detection — muting a record, counting towards alert fatigue for a type, or flagging a data source. See Triage signals.
- Approvals and denials feed earned autonomy: after repeated approvals of the same kind of action, Hive can offer to automate it. Once someone accepts, it runs automatically within limits, and the kill switch halts it.
- Execution memory records rules, workflows and exceptions your team has taught Hive; new ones start in shadow. See Learned behaviours.
Autonomy is earned one action type at a time, surrounded by role gates, approval limits, audit receipts, the kill switch and rollback where possible.
Proof, not a rented model
Models can be swapped. A model saying it is confident is not proof that a business decision was right. What makes Hive’s signals more useful over time is the record built around the model: connected business facts and their sources, evidence about what Hive could and could not observe, your team’s decisions and corrections, the rules it has learned about how you work, and outcomes that show whether an action worked. That record belongs to your workspace.What is available today
Related
Signals overview
How Hive finds and ranks signals.
Autonomy and blast radius
How Hive earns the right to act on its own.
Safety and control
The kill switch, spend caps and policy.
Audit log
Every action’s receipt, and undo.