Coordination Layer

Orchestration Patterns

Two-tier orchestration architecture enabling both within-capability and cross-capability agent coordination.

Two-Tier Architecture

Tier 1: Capability Orchestrator

Within-capability orchestration: picks the agent best placed for each task from its track record, and runs the task through RIGOR.

Scope: BUILD, OPERATE, SECURE, GOVERN, OPTIMIZE, EVOLVE

Agent selection that improves with outcomes
RIGOR phase execution
ACMF mode enforcement
Learned pattern application

Tier 2: Cross-Capability Orchestration

Coordination for workflows that span more than one capability, such as building, securing and deploying a change in one flow.

Scope: PLATFORM-level workflows

Cross-capability workflows
Full SDLC orchestration
Incident response flows
Multi-agent coordination

Orchestration Patterns

Sequential

One phase after another (default RIGOR execution)

Use case: Standard task execution

Parallel

Multiple agents work simultaneously

Use case: Independent subtasks

Group Chat

Agents collaborate with shared context

Use case: Collaborative problem solving

Hierarchical

Manager agent coordinates worker agents

Use case: Complex delegated tasks

Debate

Multiple agents debate solutions

Use case: Critical decisions

Example Workflows

BUILD → SECURE → OPERATE

Feature delivery

A ticket is turned into requirements, a plan and a design; code and tests are generated and reviewed; the change is security-checked and policy-checked; then it is deployed and watched after release. Each hand-off carries the earlier context, so the deployment step knows what the requirements were.

OPERATE → BUILD → GOVERN

Incident response

Monitoring detects an anomaly; it is triaged and diagnosed; a fix is generated and validated against tests; the change is audited for compliance and rolled out. The incident record, the diagnosis and the fix stay linked for the post-incident review.

RIGOR Framework Architecture Overview