Guides
FYI — your daily brief
What changed, what's handled, and what needs you — without living in your tools.
FYI is the things-to-know half of HiveBase (Tasks is the things-to-do half). It's your daily brief: what changed across the company, what HiveBase already handled, and the few things that actually need you.
It isn't another inbox to triage. FYI is a projection of the Brain — the same sourced record that powers everything else, rendered as the one screen you check each morning.
What you get
What changed
The developments that matter, summarized and sourced — lensed to your role.
What's handled
A receipt of what HiveBase took care of, so you can trust it ran without you.
What needs you
The short list of decisions only you can make — held, never auto-resolved.
How a brief gets built
FYI doesn't watch a firehose of raw notifications. Signals are first reconciled into the Brain as developments — durable, accreting threads about a single situation — and the brief is rendered from those.
- 01SignalsSlack · email · meetings · CRM
- 02DevelopmentsDurable, accreting threads
- 03What changedRole-lensed feed
- 04What's handledReceipt of work done
- 05What needs youHeld decisions only
- 01
Signals
Slack · email · meetings · CRM
- 02
Developments
Durable, accreting threads
- 03
What changed
Role-lensed feed
- 04
What's handled
Receipt of work done
- 05
What needs you
Held decisions only
A development is the unit FYI is built on. Where a notification is a single moment, a development persists across days and pulls new sources into the same thread — so you read the situation, not twelve disconnected pings about it.
Signals arrive
Messages, transcripts, PRs, and records stream in from your connected tools through the Signal Engine.
They reconcile into developments
Related signals attach to an existing development instead of starting a new one. The thread accretes sources, so you can see how a situation evolved over time.
HiveBase acts where it can
Routine follow-through happens automatically and lands in What's handled as a receipt. Anything that needs a human call is held and surfaced under What needs you.
The brief is rendered to you
Developments project into your FYI, lensed to your role. A "you last caught up here" marker means you only read what's new since last time.
Developments vs. notifications
This is the difference that makes FYI quiet instead of noisy.
| A notification | A development | |
|---|---|---|
| Lifespan | A single moment, then gone | Persists across days until resolved |
| Sources | One event | Accretes every related signal into one thread |
| State | Read / unread | Lifecycle — open, handled, needs-you, resolved |
| Memory | Forgotten when dismissed | Remembers what you've already seen |
| Output | A ping | A sourced summary + a receipt or a held decision |
Anatomy of a development
Each development carries the metadata that makes the brief sourced and auditable rather than a feeling.
summarytextWhat's going on, in a sentence — e.g. "Acme's renewal is at risk over SSO."
entitytypedWhat it's about — ACCOUNT · Acme Corp — so it connects to everything else
about Acme in the Brain.
sourcesaccretingEvery signal that fed it, with provenance. The list grows as the situation evolves.
statelifecycleWhere it sits — handled, needs-you, or resolved — which decides where it lands in the brief.
seen_atmarkerYour last catch-up point, so FYI shows only what's new since you read it.
Projections: brief, email, Slack
A development is stored once and projected to wherever you want to receive it. The content is the same record; only the surface changes.
| Projection | Where it shows | Best for |
|---|---|---|
| Daily brief | The FYI screen in HiveBase | Your morning catch-up, with full source trails |
| Email digest | Your inbox | Skimming before you open the app |
| Slack summary | A channel or DM | Keeping a team loop aware in real time |
One record, many surfaces
Because every projection reads the same developments, marking something caught-up in one place keeps the others in sync. You never re-read the same news twice.
FYI vs. Tasks
FYI and Tasks are two halves of the same system. FYI keeps you aware; Tasks gets things done. They share the Brain, so handoff between them is lossless.
| FYI | Tasks | |
|---|---|---|
| Question it answers | "What do I need to know?" | "What needs to get done?" |
| Unit | Development | Task |
| Default mode | Read | Execute |
| You touch it | Once a morning | When work is in flight |
| Output | Awareness + receipts | Completed work + drafts |
From awareness to action
When something in FYI needs doing, turn it into a task in one click. The development's full context — summary, entity, and every source — travels with it, so the agent picks up exactly where the development left off.
- 01Needs you in FYIHeld decision or work
- 02Spin into a taskFull context attached
- 03Agent runsSame sources, same thread
- 04Back as handledReceipt in FYI
- 01
Needs you in FYI
Held decision or work
- 02
Spin into a task
Full context attached
- 03
Agent runs
Same sources, same thread
- 04
Back as handled
Receipt in FYI
Working the brief
- Start your day in FYI — if it's quiet, you're caught up. That's the point.
- Trust What's handled: it's a receipt of work already done, not a queue.
- Treat What needs you as the real to-do list — these are the calls only you can make.
- Spin anything actionable into a task; the context comes with it.
- Use the catch-up marker — you only ever read what changed since last time.
Start your day here
FYI is designed to be the one place you check each morning. A quiet brief is a feature, not an empty page — it means HiveBase handled the routine and nothing needs your call.
FAQ
Is FYI a separate feed I have to maintain?
No. FYI is a projection of the Brain. You never curate it — developments form automatically as signals reconcile, and the brief renders from them.
Why don't I just get a notification for everything?
Because notifications don't remember. FYI reconciles related signals into a single durable development, so you read the situation once instead of chasing a dozen pings about it.
What does 'handled' actually mean?
HiveBase did the routine follow-through itself and left you a receipt. Anything that needs a human decision is held under What needs you instead — it's never auto-resolved.
How is FYI different from Tasks?
FYI is what you need to know; Tasks is what needs to get done. They share the Brain, so turning a development into a task carries its full context with no copy-paste.
Can I get the brief outside the app?
Yes. The same developments project to an email digest or a Slack summary. Catching up in one surface keeps the others in sync.
Related
Context & the Brain
The sourced record FYI is built on.
Tasks
The things-to-do half — where developments go to get done.
Action receipts
What's handled leaves a durable record — with undo when reverse is one step.
Trust & safety
Holds, Stop, and what never auto-resolves without you.
Connect your tools
Add the sources that feed your developments.
First governed run
When a development becomes an outbound action.