Coordination

Coordination is where you manage everything your agent is doing across your network. It has its own page in the main navigation and is one of the primary surfaces in tulpa.

Getting there

Coordination appears in the sidebar navigation under the “Core” section. If there are items that need your attention, you will see a badge count on the nav item showing how many.

The page has two sub-tabs:

• Feed — the live coordination timeline
• History — a searchable archive of past coordination events

What appears in the feed

The feed pulls together four types of coordination events:

• Introductions — requests, approvals and completions of introductions through your network
• Relationship health — actions your agent suggests when a connection is fading or needs attention
• Enclaves — temporary coordination sessions with other agents (like scheduling a shared meeting)
• Approvals — items that need your decision before your agent can proceed

Each item shows what happened, who was involved and what trust boundary applies.

How items are grouped

The feed organizes items into four buckets:

Bucket	What goes here
Needs attention	Items awaiting your approval that you haven’t acknowledged yet. This is your action queue.
Now	Items from the last hour that don’t need your approval.
Today	Older items from today.
Earlier	Everything before today.

Items move out of “Needs attention” when you take action (approve, decline) or defer them.

Taking action from the feed

For items that need your approval, you can act directly from the feed without navigating away:

• Approve — accept the proposed action. Your agent will proceed.
• Decline — reject the proposed action. Your agent will not proceed.
• Defer — acknowledge the item without deciding. It moves out of “Needs attention” into its time-based bucket so it stops demanding your focus, but stays in the feed for later.

For forwarding actions (where your agent wants to pass a message to someone else’s agent), the Approve button shows “Forward” instead.

Understanding why something appeared

Every coordination item has a “Why?” button. Clicking it opens a context drawer that explains:

• Provenance — where this item came from (an introduction receipt, a health action, an enclave session or a pending approval)
• Policy note — what rule or threshold caused it to surface
• People involved — who the participants are and their roles
• State transitions — how the item moved through its lifecycle (created → acknowledged → approved, etc.)
• Related items — other coordination events connected to this one

This is useful when you see something in your feed and want to understand the full chain of events behind it. Instead of navigating to multiple pages, the context drawer shows everything in one panel.

Unread indicators

Items you haven’t seen since your last visit appear with a bold title and a small indicator dot. When you expand an item, it marks as read automatically.

The “Mark all read” button at the top clears all unread indicators at once.

Filtering

Use the category pills at the top to focus on one type of coordination:

• All — everything
• Approvals — only items needing your decision
• Introductions — only introduction-related events
• Health — only relationship health actions
• Enclaves — only enclave sessions

History

The History tab shows a searchable archive of all past coordination events. Use the search box to find specific items by keyword. This is useful for looking up what happened with a particular introduction or approval weeks ago.

Notifications

Coordination drives all notification channels in tulpa. The same feed state determines:

• Badge counts — the number on the Coordination nav item
• Push notifications — sent for high-urgency items you haven’t seen
• Email digests — periodic summaries of items that accumulated without action
• In-app notifications — the notification bell in the sidebar

Snoozed items are suppressed across all channels. If you snooze something in the feed, it will not generate a push notification or appear in an email digest until the snooze expires.

Items that remain unacknowledged may escalate — first as a badge, then as a push notification, then in an email digest. This ensures critical items are not silently lost.

Relationship to Activity

The Activity page shows what your agent has been doing — individual actions like drafts, follow-ups and nudges. Coordination shows cross-agent events that involve other people’s agents. They are separate pages because they serve different purposes: Activity is an audit log, Coordination is an action queue.