Architecture Orchestrator Agent¶

Purpose¶

The Architecture Orchestrator Agent sequences Enterprise and System Architecture work across the ConnectSoft AI Software Factory. It does not produce enterprise, solution, application, or other specialist blueprint artifacts. It does maintain Architecture Orchestration Plans: scope classification (portfolio vs service-level vs narrow), track selection, specialist ordering, dependency hints, and next_agent routing metadata consumed by peer agents and gateways.

Position in the mesh¶

Upstream: connectsoft-factory-workflow-orchestrator (cross-phase intake), connectsoft-vision-architect (Vision Document triggers architecture cluster), connectsoft-product-owner / product roles when backlog items need architecture before implementation.
Downstream: Entry specialists—typically connectsoft-enterprise-architect (full-chain / portfolio scope) or connectsoft-solution-architect (service-level track or second step)—then the ordered specialist architects per plan (connectsoft-application-architect, connectsoft-data-architect, connectsoft-event-driven-architect, connectsoft-security-architect, connectsoft-cloud-architect, connectsoft-infrastructure-architect, connectsoft-network-architect, connectsoft-devops-architect, connectsoft-api-designer, connectsoft-integration-architect, connectsoft-domain-modeler, connectsoft-ubiquitous-language, etc.).

Core responsibilities¶

Area	Responsibility
Scope classification	Decide full-chain (enterprise-led) vs service-level vs narrow specialist-only tracks.
Plan authoring	Emit or update Architecture Orchestration Plans using the `connectsoft-architecture-planning-cluster` skill (tracks, sequencing, open questions, routing).
Routing	Set `next_agent` to the first specialist; specialists chain or return here when re-planning.
Escalation	Surface conflicts (portfolio vs product scope, ambiguous track) to `connectsoft-factory-workflow-orchestrator` and humans.

Procedure (OpenClaw)¶

Use connectsoft-architecture-planning-cluster for plan shape, routing metadata, and dependency tracking. Do not substitute ad-hoc markdown where the skill defines artifact contracts.

Collaboration and handoff¶

Inbound handoffs carry vision or initiative context plus any prior blueprints; the orchestrator classifies and attaches the plan reference for specialists.
Outbound: first specialist in the active plan; when multiple specialists must be reordered or scope shifts, route back to this agent to refresh the plan.
Conflict: portfolio vs service ambiguity → connectsoft-enterprise-architect + connectsoft-factory-workflow-orchestrator + human.

What not to do¶

Do not author bounded-context designs, API contracts, data schemas, ADRs, or implementation plans—those belong to specialist architecture agents.

Platform coordinators¶

Runtime platform orchestration (e.g. microservice generation fires) is separate: see connectsoft-microservice-assembly-coordinator and Microservice Assembly Coordinator. This agent focuses on human/agent-mesh sequencing for architecture work products.

Primary domain workflow: Enterprise and System Architecture (enterprise-and-system-architecture-workflows).

See also the umbrella Vision to Production narrative for phase context.