AI Transformation Command Center Deployment Guide

Runtime Boundary

The AI Transformation Command Center remains a dedicated Cloud Run sub-application. Kakehashi provides the localized catalogue and app entry pages, while the full dashboard runtime is served from the stable runtime path.

Services

• Command Center web: Next.js Pages Router frontend deployed as command-center-web.
• Command Center API: FastAPI backend deployed as command-center-api.
• Demo database: pre-seeded SQLite for the cost-to-zero showcase runtime.
• Main shell: Project Kakehashi Next.js App Router application deployed as kakehashi-app.

Route Model

• Localized app entry: /en/apps/ai-transformation-command-center and /ja/apps/ai-transformation-command-center.
• Runtime launch path: /apps/ai-transformation-command-center.
• Legacy route during recovery: /ai-transformation-command-center.html redirects temporarily to the English app entry.

API Boundary

The runtime frontend calls the Command Center API backend directly from the browser. Production CORS must explicitly allow the public site origin; route rewrites alone do not satisfy this boundary.

Public Review Status

The legacy deployment guide includes internal configuration examples and production hardening notes. Keep the full runbook out of public canonical content until the owner approves the exact disclosure level.

Acceptance Checks

• Runtime path opens the Cloud Run frontend.
• API health endpoint responds from the deployed backend.
• Browser preflight from the public site origin succeeds and returns the matching access-control-allow-origin.
• Dashboard, maturity, ROI, discovery, roadmap, and export flows do not fail from browser CORS.
• Localized app entry pages remain readable without the runtime or agent layer.
• Legacy redirects are promoted from temporary to permanent only after owner acceptance.