Guides

FYI — your daily brief

What changed and what's worth knowing — without living in your tools.

Last updated 2026-07-27

FYI is the things-to-know half of HiveBase (Tasks is the things-to-do half). It's your company's picture: what changed and what's worth knowing — read each morning in the app, or as an email or Slack digest.

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 worth knowing

The threads worth reading, ranked by what's at stake — never by what's loudest.

Weigh in — or don't

Correct a fact, close a research line, or make a story a task. Optional input; nothing waits on you.

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.

  1. 01

    Signals

    Slack · email · meetings · CRM

  2. 02

    Developments

    Durable, accreting threads

  3. 03

    What changed

    Role-lensed feed

  4. 04

    Worth knowing

    Ranked by stakes

  5. 05

    Weigh in

    Optional — never owed

One record projects into every surface — not a raw notification firehose.

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.

1

Signals arrive

Messages, transcripts, PRs, and records stream in from your connected tools through the Signal Engine.

2

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.

3

HiveBase acts where it can

Routine follow-through happens automatically and leaves a receipt on the task that did it. Anything that genuinely needs a human call lives in Tasks · Focus — a story only links to it ("In Tasks ↗"), it never copies the ask.

4

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 notificationA development
LifespanA single moment, then gonePersists across days until resolved
SourcesOne eventAccretes every related signal into one thread
StateRead / unreadLifecycle — active, watching, resolved
MemoryForgotten when dismissedRemembers what you've already seen
OutputA pingA sourced summary + links to where work lives

Anatomy of a development

Each development carries the metadata that makes the brief sourced and auditable rather than a feeling.

summarytext

What's going on, in a sentence — e.g. "Acme's renewal is at risk over SSO."

entitytyped

What it's about — ACCOUNT · Acme Corp — so it connects to everything else about Acme in the Brain.

sourcesaccreting

Every signal that fed it, with provenance. The list grows as the situation evolves.

statelifecycle

Where it sits — active, watching, or resolved — which decides where it lands in the brief.

seen_atmarker

Your 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.

ProjectionWhere it showsBest for
Daily briefThe FYI screen in HiveBaseYour morning catch-up, with full source trails
Email digestYour inboxSkimming before you open the app
Slack summaryA channel or DMKeeping 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.

FYITasks
Question it answers"What do I need to know?""What needs to get done?"
UnitDevelopmentTask
Default modeReadExecute
You touch itOnce a morningWhen work is in flight
OutputAwareness + receiptsCompleted 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.

  1. 01

    A story in FYI

    Worth doing

  2. 02

    Spin into a task

    Full context attached

  3. 03

    Agent runs

    Same sources, same thread

  4. 04

    Done in Tasks

    Receipt on the task

The development's sources and summary travel with the task — no re-briefing.

Working the brief

  • Start your day in FYI — if it's quiet, you're up to date. That's the point.
  • Weigh in when it's worth it: correct a fact, close a research line, or make a story a task. Optional input, never owed.
  • Trust receipts: work HiveBase did on its own leaves a durable record on the task that did it — inspect or undo there.
  • 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 — nothing waits on you here. When a call is genuinely yours, it's in Tasks · Focus.

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 if something in FYI actually needs a decision?

It doesn't stay there. Decisions live in Tasks · Focus — a story that has a linked ask simply says "In Tasks ↗" and opens it. FYI may invite optional input on a story, but ignoring it stalls nothing.

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.