Your Control Tower

When you open Monad, you land in your Control Tower. It is designed to answer two different questions without mixing them together:

• Do: What needs an action or decision from me?
• Know: What changed that is worth understanding?

Control Tower is not a timeline of every unread message. Spaces and DMs keep their own exact unread positions, while Control Tower helps you choose where your attention should go.

Do: outcomes, not inbox zero#

Do contains things such as a decision only you can make, an approval, a review, a reply request, or an agent waiting for your input. Opening the source does not complete the item. It stays open until the requested outcome happens, you mark it complete, dismiss it, or it becomes irrelevant because the underlying work changed.

Use Snooze 4h to hide an item until a specific deadline without lowering its importance or claiming it is complete. It reappears automatically. Actions sync across your devices; if an old tab acts on a request that has since been replaced, Monad leaves the newer request untouched.

Know: a grounded edition#

Know is an edition assembled from the work you are allowed to see. It can include a lead story, thread-movement digests, updates from people, a quiet fold, summaries from high-volume spaces, and notification digests. These are compact compiled blocks rather than one card per message. Every edition is frozen when it is created, so its wording and cited sources do not silently change later.

Editions have a deliberate size limit: Control Tower prioritizes the strongest updates and tells you when lower-ranked material remains for a later edition. If access to any source used by a block is removed, Monad removes that whole block instead of leaving behind a summary of content you can no longer open. It also tells you how many updates were left out, and those hidden updates are not marked read. Expand Sources and citations on any visible block to inspect every frozen source and grounding citation used for it.

Monad prepares a morning edition around 7:30 AM in your timezone. If you open Control Tower after the edition has become stale, it refreshes. Select Mark edition read when you have caught up; that acknowledges only the updates in that edition, not anything that arrived afterward.

While no edition is available, Control Tower distinguishes normal assembly, a delayed assembly, and a failed attempt. Delayed or failed attempts offer a retry; your updates are not lost or acknowledged while you wait.

If richer summarization is temporarily unavailable, Control Tower shows a deterministic source-backed edition and tells you it is degraded instead of inventing a summary.

Messages and threads#

Unread dots in spaces, DMs, and threads come from the exact messages positioned after your monotonic read frontier. Monad separately records each message occurrence that was actually rendered; compact ranges are only synchronization telemetry and never prove that skipped history was seen. A message arriving while a thread is open stays new until you reach it. Crossposting an older message creates a new arrival in the destination space.

Threads currently show their raw messages immediately. Their exact read and observation state keeps new replies below the frontier you opened, including when another reply arrives while the panel is already open.

The old Feed and Activity pages now take you to Control Tower.

When an agent run ends after using your delegated authority, Control Tower shows one Know item with the truthful outcome—even when the run failed, was cancelled, timed out, or crashed after completing some writes. Its summary includes every successful write action, not only the first, and Open takes you to the exact thread reply that caused the run when one exists. The individual actions remain available as the run's audit trail.