Everything Oliver has to tell you that isn't a conversation

A name, a glyph, and one sentence.

Its charter fit in a sentence, everything Oliver has to tell you that isn't a chat, and that sentence turned out to be a surprisingly deep engineering project.

The hard part wasn't rendering rows. It was making a surface that spends the member's attention honestly, and enforcing that mechanically with tests so it stays honest as the codebase moves.

Not a row, on purpose.

One line, Oliver is working on <task> · 2:41, rendered only while a delegation is actually running, elapsed counter ticking off the earliest start in the set.

It's deliberately not a row: no id, no timestamp, no dismiss, which structurally keeps it out of the keyboard walk. And there is no "all quiet" fallback, because a surface fed by a 15/60-second poll can't honestly claim quiet.

Blocked on the member, and nothing else.

Rows where something is blocked on the member: a review assigned to you, an open tool-approval gate, a shadow waiting at an approval step. Mono lane label on the left, one-word act on the right, expiry always written as a duration ("times out in 20m"), never a bare timestamp.

Needs-you rows have no dismiss: hiding something you genuinely owe is grooming, not deciding, and the row leaves when the state resolves.

An offer is not an obligation.

Oliver's own offers: title, one-line gist, at most two controls, Start and Decline.

Proposals never light the orange badge: an offer is not an obligation.

A briefing surface, not an archive.

What finished, arrived, or broke: shipped previews, shadow runs, shares, resolved approvals and reviews, goals Oliver completed or set aside. Bucketed Today · Yesterday · This week · Earlier, hairline-separated, no cards, keyset-paged, ending in an honest terminal line: "That's everything from the last 30 days."

The part we most wanted to build.

"Oliver suggests" is the first surface where the memory Oliver collects comes back as a concrete, executable offer.

Oliver's brain runs on the org's own box, digesting what's happening (conversations, activity, things you've told it). Out of that it mints proposals.

Three things, decided brain-side.

Composition happens brain-side, at digest time, and the composer decides three things: the prompt, the target agent (main thread or a specific project agent), and the delivery.

Memory proposes; the member is the gate.

By the time a proposal reaches the Inbox it isn't a nudge; it's a loaded action waiting on one click. And the click is load-bearing: nothing auto-executes. Memory proposes; the member is the gate.

The first fully wired producer is the idle-project sweeper: nothing has moved on a project in 14 days → "Want me to take a pass and report back?"

Every no, remembered.

Producers write with an idempotency key and ON CONFLICT DO NOTHING. A dismissed row keeps its key, so a declined proposal can't sneak back in a later sweep.

Proactivity that re-asks on a timer is spam with better branding.

Orange means one thing.

The color grammar is enforced mechanically: orange means "alive or blocked on you," and a test asserts no ledger kind maps to it. A crashed preview from three hours ago is neither.