gateway-orchestrator-contract

Define the Gateway-to-Orchestrator contract for AgentHub streamed orchestration.

Updated May 19, 2026
One-click install
npx skills add https://github.com/zxc1a1a1/Multi_Agent-AgentHub --skill gateway-orchestrator-contract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gateway-orchestrator-contract
Source: https://github.com/zxc1a1a1/Multi_Agent-AgentHub/tree/main/.agents/skills/gateway-orchestrator-contract
Command: npx skills add https://github.com/zxc1a1a1/Multi_Agent-AgentHub --skill gateway-orchestrator-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes the contract between AgentHub Gateway and the internal Orchestrator, preventing process-boundary leaks and ensuring reliable streamed orchestration with traceability and safe error handling.

Core Features & Use Cases

  • Service boundary enforcement: Guarantees Gateway only handles external HTTP/SSE, while Orchestrator owns planning, execution, fallback/retry, and internal streaming.
  • Stable inter-process streaming protocol: Defines the internal OrchestratorStreamEvent (snake_case) and the required mapping responsibility to AG-UI events (UPPER_SNAKE_CASE).
  • Operational correctness for runs: Specifies OrchestratorRequest, OrchestrationPlan, OrchestratorResult, run lifecycle/status, ordered_parallel and sequential behaviors.
  • Cross-process safety & reliability: Mandates internal auth, timeout, cancellation propagation, trace header propagation, and SafeError error contracts.
  • Contract test and mock-first guidance: Provides minimum checks to validate endpoints, serialization, streaming, cancel behavior, and error redaction.

Quick Start

Implement Gateway and Orchestrator as two independent processes and use this contract to validate request/stream/result shapes, internal auth, trace headers, and cancellation semantics end to end.

Frequently Asked Questions about gateway-orchestrator-contract

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce service boundaries in multi-agent orchestration between a gateway and an orchestrator?

Multi-agent orchestration service boundaries are enforced by restricting the Gateway to external HTTP/SSE handling while the Orchestrator owns planning, execution, fallback, and internal streaming. This separation prevents process-boundary leaks and ensures reliable orchestration.

What is the standard contract for streaming internal orchestration events to AG-UI?

The standard contract for streaming internal orchestration events uses snake_case OrchestratorStreamEvent objects that must be mapped to UPPER_SNAKE_CASE AG-UI events. This mapping responsibility ensures stable inter-process streaming protocol communication.

How do I handle cancellation and timeout propagation across multi-agent orchestration processes?

Cancellation and timeout propagation across multi-agent orchestration processes require strict cross-process safety rules including internal service authentication, trace header propagation, and SafeError error contracts to ensure reliable run lifecycle management.

Does the gateway orchestrator contract support ordered parallel and sequential execution strategies?

Yes, the gateway orchestrator contract supports ordered parallel and sequential execution strategies alongside single execution. These strategies define how multiple agents are coordinated during planning modes including direct, mention, auto, and manual.

How do I validate multi-agent orchestration endpoints for serialization and error redaction?

Validating multi-agent orchestration endpoints requires contract tests and mock-first guidance to check minimum serialization, streaming, cancellation behavior, and SafeError error redaction. This ensures request, stream, and result shapes are correct end to end.