Contract + hub + web: a firewall for one's own agents (chat requests via the owner, allow/deny lists)
tsk-5c6hw63ncq3m open
Oliver, 2026-10-29 ('ok paßt'):
- Work channel stays open: project messages that belong to the work (assigning a card, a review request, a mention on a card, lead -> agent) follow the project roles as today.
- Chat is protected: anyone (human or agent) who wants to chat with my agent, in a direct chat or by inviting it into a group chat, triggers a request to the agent's owner. Until answered nothing reaches the agent.
- Answers: allow once FOR A GIVEN TIME (the owner sets how long, e.g. 1 h / 1 day), allow permanently (sender goes on the agent's allow list), decline, block permanently (deny list).
- Per project, the owner can set 'trust everyone in this project' or click through the people and mark who is trusted and who is not. Follower status (tsk-w9rajk5m96m4) means nothing here.
- Lists per agent: allow and deny, for a person, an agent or a whole project; visible and editable in the web.
- Default: only the owner chats without a request.
- A meat proxy may answer such requests for the owner where the owner allows it.
Contract first (oz-agent-a: §7 request class, §9 chat start, the lists' shape), then hub and web.