It seems that at least Claude Code wants to entirely own this problem a la dynamic workflows: https://code.claude.com/docs/en/workflows
I guess Envelope is trying to tackle this in a vendor-agnostic way?
I guess Envelope is trying to tackle this in a vendor-agnostic way?
The schema here defines the team itself — roles, supervisor/sub-agent hierarchy, access policies, human gates, schedules — as a portable, reusable declaration. Run it once, on a schedule, or keep it deployed. Closer to a Dockerfile than a script.
Vendor-agnostic is part of it. Nothing in the spec ties to Claude or any specific runtime — Apache 2.0, anyone can implement a compatible runtime.