Execution Provider Framework and Four Binding Protocols
Preserve COR, decisions, governance and outcome evidence across Native, A2A, vendor API and MCP execution bindings.
Audience: Runtime builders, partners, architects and tenant administrators.
Status: Opt-in execution-provider.v1alpha1 draft extension to core v0.3.1; bounded installed adapters, live tenant acceptance pending.
Four binding protocols
Native execution using Aegora Runtime is the default. A2A is preferred when an eligible autonomous external agent supports it, never mandatory. Proprietary interfaces use native vendor adapters; tools use MCP. No artificial A2A wrapper is required.
- aegora_native: Aegora agent or capability runtime
- a2a: eligible autonomous external agent
- vendor_api: approved proprietary invocation API
- mcp: tool capability with optional long-running Tasks
Portable specification and private tenant configuration
The portable x-execution-provider extension references versioned capability contracts and execution policy. Tenant deployment bindings specify the actual protocol, provider and adapter release, implementation, environment, contracts and authentication profile. Endpoints and secret references stay outside portable specs. Execution modes native/delegated/compiled are separate from protocol; compiled Runtime execution remains future work.
{
"x-execution-provider": {
"schema_version": "execution-provider.v1alpha1",
"capability_contract_refs": [
"capability.example@1.0.0"
],
"execution_policy_ref": "policy.example.execution@1.0.0"
}
}Implemented product scopes
Installed transports cover A2A, Microsoft Foundry, ServiceNow Virtual Agent, Salesforce Agentforce, AWS AgentCore JWT, Google Agent Engine custom query and MCP Streamable HTTP. Exact product interfaces and advertised operations determine compatibility. ServiceNow needs authenticated callback routing; AWS and Google require the reviewed application result envelope. MCP 2026-07-28 and 2025-11-25 are separately pinned generations. Tasks do not confer autonomous agent semantics. These transports do not establish use-case delivery or certification.
Configuration and acceptance
The dedicated Execution Provider Studio manages tenant drafts. The Aegora problem-to-path plugin prepares and validates configuration alongside Operating Path drafts without activating or executing them. Every protocol retains COR, explicit decision, governance, approval and audit linkage. Duplicate requests reuse execution records; ambiguous results require reconciliation and human fallback. Authoritative resulting-state evidence must establish the business outcome. Local tests are implemented; production deployment and live tenant acceptance are separate pending gates.
Partner ecosystem
Execution adapters, spec compilers and deployment providers form open contribution interfaces. Certified provider publication through Marketplace is the intended ecosystem direction. Partner certification verification, Marketplace provider publishing, compilers and deployment providers remain future work. Certification never grants tenant permissions.
Use the public standard to shape governed runtime behavior.
The point of the standard is not documentation for its own sake. It is to make packages authorable, reviewable, validatable, and portable enough to drive governed execution.