SUPERSEDED by docs/boss_agent/BOSS_AGENT_CONSOLIDATION_PLAN.md

Boss Agent Service Consolidation Plan

Analysis of Deployed Services

Based on a deeper analysis of the codebase and build configurations, here is the status of the Cloud Run services:

Service Name Source/Version Status Notes
boss-agent miz-oki-adk-agents/boss (v5.2.2 Unified) ✅ CORRECT The latest Unified v5.2.2 implementation. Includes SRPVDAL, MoE, E-SHKG, and REWOO capabilities. Defined in deployment/cloudbuild-configs/cloudbuild-boss-agent.yaml.
boss-agent-adk miz-oki-adk-agents (v5.0.0) ❌ LEGACY Older v5.0.0 implementation. Superseded by boss-agent. Defined in miz-oki-adk-agents/cloudbuild.boss.yaml.
boss-rewoo-orchestrator services/boss-rewoo-orchestrator (v3.0.0) ❌ LEGACY Older v3.0 implementation of REWOO. The boss-agent now includes the REWOO Orchestrator natively.
boss-agent-dynamic services/boss_agent_enhanced ⚠️ SPECIALIZED Seemingly a "Dynamic" or "Enhanced" variant. Verify if its features are in the Unified agent.
boss-agent-backend (Various) ❌ LEGACY Old alias, referenced as "replaced" in app.py.
boss-agent-adk (Various) ❌ LEGACY Old version tag.
boss-agent-service (Various) ❌ LEGACY Generic/Old name.
agent-launcher Unknown ❌ UNUSED Not found in current build configs. Likely orphaned.
api-gateway services/api-gateway ✅ CORE The API Gateway is active. Needs config update to point ONLY to boss-agent.

Action Plan

1. Consolidate on boss-agent

The boss-agent service (deployed from miz-oki-adk-agents/boss/) is the single source of truth for the "Boss Agent". It unifies all capabilities.

2. Rename & Cleanup Strategy

We should stop updating the legacy services and eventually delete them.

Steps:

  1. Verify boss-agent Deployment: Ensure deployment/cloudbuild-configs/cloudbuild-boss-agent.yaml is the primary deployment pipeline.
  2. Update API Gateway:
    • Ensure services/api-gateway/main.py routes /api/boss-agent to the correct boss-agent service URL.
    • Currently, it points to http://boss-agent:8000. Verify port (likely should be 8080 or port 80 via Cloud Run internal DNS).
  3. Archive Legacy Build Configs:
    • Move miz-oki-adk-agents/cloudbuild.boss.yaml to archive/.
    • Move services/boss-rewoo-orchestrator/cloudbuild.yaml to archive/.
    • Update cloudbuild.yaml root triggers to remove legacy service deployments.
  4. Rename Service (Optional):
    • If you strictly want to rename boss-rewoo-orchestrator to boss-agent to preserve the URL, we can do that, but it is better to just cut over traffic to the existing boss-agent service.

Immediate Actions

  1. I will create a script/workflow to archive the legacy build files to prevent accidental updates.
  2. I will generate a "Universal" cloudbuild-boss-agent.yaml that explicitly builds the v5.2.2 Unified Agent.
← All docsView source on GitHub →