Studio · Full-screen workspace

Signals

Signals is the standalone, organization-wide feed for concise outcomes: on-track work, wins, FYIs, risks, blockers and requests for help. Write one directly or review a suggestion grounded in recent private notes, then share it end-to-end encrypted with your organization.

Share the outcome, keep the working context. Suggested Signals can cite private memories locally so you can audit the draft. The organization receives the short headline and its visible feed metadata — never the source notes, source IDs or source summaries.

Six visible states

On track, Win, FYI, Off track, Blocked and Need help make the feed scannable.

Suggested or manual

Review, edit or dismiss grounded suggestions, or write a 120-character headline yourself.

Private provenance

The underlying source identities and content stay in your local memory graph.

Reactions & retraction

Mark an update seen, react to it, and remove a Signal you authored.

Open it any time — type /signal with no text, say “open Signals,” or choose Signals from Studios. /signal your update stages an editable card in chat.

What it is#

Signals is its own Studio. It is optimized for scanning the organization's current outcomes, not for assigning work or collecting an answer. Use Broadcasts in Team when people must accept or decline a directive, and Team Asks when you need replies. Team includes a shortcut to Signals, but Signals is not one of its tabs.

Composing & sharing#

Choose one of six states, write a headline of up to 120 characters and optionally add a topic of up to 40 characters. Press Share Signal only after the wording is right. The Studio can also prepare up to three suggestions from recent local notes; each shows its local “based on N of your notes” provenance and offers Share, Edit and Dismiss.

A Signal suggested in chat follows the same human gate: the card lets you edit the headline, state and topic, and the publish request occurs only when you click. There is no destination picker — Signals is an organization feed.

Try saying
let the team know Project A is at-risk signal that the migration slipped to next sprint share where the ledger work stands

What leaves your device#

The transmitted Signal contains the headline, visible state, optional topic, author identity and creation time. If it came from a grounded suggestion, it also carries the number of private notes used, so recipients may see “Based on 4 private notes.” The notes themselves, their summaries, their IDs and the links between them remain local.

Publishing also creates a local output memory connected to those source memories. That gives you provenance without placing the evidence inside the shared envelope.

A signal, as sent
"Project A is at-risk."
Based on 4 private notes — the count is visible; the notes stay local

Audience & encryption#

A Signal goes to the authenticated organization feed, not to a selected peer or “team brain.” Pairing is not required; membership and verified identity come from your Zimac organization sign-in. The relay fans out an end-to-end-encrypted envelope and cannot read its contents.

Try saying
signal that the migration is back on track share this blocker with the organization

Reading & responding#

The feed is newest first and can be filtered to All, Needs attention (Off track, Blocked, Need help) or Progress (Win, On track). Each card shows the author's directory-verified identity when available. Use the eye reaction to mark an update seen or choose another reaction; counts update across the organization. You may retract only a Signal you authored, which removes it from everyone's feed.

Signals are a live pulse, not an archive. Each device keeps the newest 200 Signals and drops entries older than seven days whenever the feed changes.
Try saying
what's the team signaling right now? open Signals