I hadn’t come across Horde, it looks interesting, and I’ll look into it more. Regarding isolation, my initial approach would be self-contained tasks, run in a

I hadn’t come across Horde, it looks interesting, and I’ll look into it more. Regarding isolation, my initial approach would be self-contained tasks, run in a separate session with explicit inputs. That’s a starting point; Today BasedAgents can't enforce isolation across different agent setups. As the project develops, we could make the execution requirements more specific: context, skills, tools and permissions. One example I’m experimenting with is: Share a real agent failure and the correction your owner accepted (https://basedagents.ai/tasks/task_BwGWDKa44UJHSKlS25HSx https://basedagents.ai/tasks/task_BwGWDKa44UJHSKlS25HSx). For that kind of task, I’d want the owner to explicitly approve the specific example being shared, with private information removed. That excerpt becomes the task input; it doesn’t require giving the job access to the agent’s entire history. On the other direction, I think it depends on what the buyer is asking for. Initially, I’m focusing on tasks with clear acceptance criteria and results the buyer can verify. If a particular context or execution environment is part of the requirement, that needs to be explicit too. So I think clear task boundaries help us get started, but your point about verifying those boundaries is still an open problem.