Enclaves

An enclave is a temporary coordination room where multiple agents work together on a specific task. Enclaves exist because some coordination — like finding a meeting time for three people — requires sharing information across more than two agents at once.

How enclaves work

When your agent needs to coordinate with multiple other agents, it creates an enclave with a stated purpose. Each participant’s agent must authorize joining before any information is shared.

The key principle is minimum disclosure: an enclave only shares what is necessary for its purpose. A meeting scheduling enclave shares availability windows, not full calendars. It shares time slots, not event titles.

Enclave types

Currently, tulpa supports one enclave type:

Meeting sync — finds a mutually acceptable meeting time among three or more people. Each agent submits availability windows (start time, end time, optional confidence level). The enclave computes overlap and proposes slots. Participants accept or counter until a time is agreed.

Lifecycle

Every enclave moves through a defined set of states:

pending → open → resolved
  ↓        ↓
expired   expired
  ↓        ↓
aborted   aborted

State	What it means
Pending	The enclave has been created and is waiting for all participants to authorize
Open	All participants have authorized and the enclave is actively coordinating
Resolved	The purpose has been fulfilled (e.g., a meeting time was agreed)
Expired	The enclave’s time limit passed before it could be completed
Aborted	A participant withdrew or a policy check failed

Enclaves always have a time limit. They close automatically if their purpose is not fulfilled within that window.

What happens inside an enclave

Once open, participants can take these actions:

• Submit windows — share available time slots
• Acknowledge windows — confirm receipt and acceptability of a proposal
• Propose slot — suggest a specific time from the overlap
• Accept slot — agree to a proposed time
• Counter slot — reject a proposal and suggest an alternative
• Withdraw — leave the enclave (this aborts it for all participants in the current version)

Authorization

Your agent cannot join an enclave without authorization. Depending on your permission settings:

• Your agent may ask for your approval before joining (the enclave will appear in your Coordination feed as “awaiting approval”)
• Your agent may join automatically if your rules allow it (it will appear as “auto-executed”)

Either way, the enclave and its outcome are logged in your Activity and Coordination feeds.

Receipts

When an enclave resolves, each participant receives a signed receipt recording:

• The enclave’s purpose
• Who participated
• The outcome (e.g., the agreed meeting time)
• How many operations occurred

Receipts are cryptographically signed so any participant can verify the outcome independently.

Privacy

• No data from an enclave persists on other participants’ systems beyond the receipt
• Only the specific information needed for the enclave’s purpose is shared
• Full calendars, notes, relationship data and other private information are never exposed
• When an enclave expires or aborts, the shared state is discarded

Where enclaves appear

• Coordination feed — enclave events show up with their current status, and you can expand them to see participants and progress
• Context drawer — click “Why?” on an enclave item to see the full chain of events