aaf-orchestration-occ

Enforce the Orchestrator Capability Contract for non-bypassable agent governance.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/AgenticAF-Community/FrameworkCore --skill aaf-orchestration-occ
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aaf-orchestration-occ
Source: https://github.com/AgenticAF-Community/FrameworkCore/tree/main/tools/skills/aaf-orchestration-occ
Command: npx skills add https://github.com/AgenticAF-Community/FrameworkCore --skill aaf-orchestration-occ

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that agent orchestration is implemented in a secure, reliable, and auditable manner by enforcing the Orchestrator Capability Contract (OCC) and the governance-above-orchestration pattern.

Core Features & Use Cases

  • Pluggable Orchestration: Design and implement orchestration engines (graphs, multi-agent coordination, workflows) that can be easily replaced without compromising governance.
  • Non-Bypassable Governance: Ensure that critical decisions like tool usage, budget adherence, and safety checks are always handled by a central governance layer, never directly by the orchestrator.
  • OCC Compliance: Use the OCC checklist to select or build orchestration tools that meet essential requirements for auditability, recovery, and safety.
  • Use Case: When setting up a multi-agent system for customer support, use this skill to ensure the workflow engine (orchestrator) cannot bypass the approval process for issuing refunds (governance).

Quick Start

Use the aaf-orchestration-occ skill to ensure the chosen workflow engine meets the OCC requirements for interruptible and auditable state management.

Frequently Asked Questions about aaf-orchestration-occ

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

FAQPage Schema
How do I ensure non-bypassable governance in multi-agent orchestration?

To ensure non-bypassable governance in multi-agent orchestration, enforce an Orchestrator Capability Contract mandating gateway-only tool invocation and structured event emission for safety and auditability.

What is the Orchestrator Capability Contract for agent workflows?

The Orchestrator Capability Contract is a compliance checklist for selecting or building orchestration engines, ensuring critical decisions like tool usage and safety checks are handled by a central governance layer rather than the orchestrator.

How do I implement pluggable orchestration engines without compromising governance?

Implement pluggable orchestration engines by separating the workflow logic from a central governance layer, ensuring the orchestrator can be replaced without bypassing critical safety checks or interruptible state management.

When do I need structured event emission in multi-agent coordination?

Structured event emission is required in multi-agent coordination when you need auditable state management and recovery, ensuring all orchestrator actions and tool invocations are traceable for safety compliance.

Can I use a workflow engine that bypasses the governance layer for agent coordination?

No, workflow engines must not bypass the governance layer. The orchestrator should only coordinate agents while a central governance layer handles critical decisions like budget adherence and approval processes.

What is the best way to audit tool invocation in multi-agent systems?

The best way to audit tool invocation in multi-agent systems is to mandate gateway-only tool access through an Orchestrator Capability Contract, ensuring all actions emit structured events for compliance tracking.