Architecture boundary
Reasoning and privileged execution remain separate. Agents request bounded capabilities through Autonomy rather than receiving broad system credentials.
Core concerns
- Identity and mappings
- Versioned catalog and lifecycle
- Governance and policy
- Processes, actions, adapters, and bindings
- Execution evidence
- REST, MCP, A2A, and supported interfaces
Stable platform, dynamic Packs
Business and application content evolve independently from the stable execution platform.
Public web edition
The private company-content repository remains the canonical source.