# CASAN Platform (Level 3 — Productization UI) · **PREVIEW** > Status: **PREVIEW.** The AgentOps dashboard and Plan-13 Control Panel, including > Command Center baseline and Plan-18 MVP-0/1 Chat Console plus MVP-2 agent > selection and Operator loop/draft-hold foundation, exist today. > Evidence/attack viewers, Gitea integration, and managed production rollout remain > planned. `package-release.sh platform` builds a clearly-stamped > `casan-platform-preview-*` bundle containing only what exists. Optional layer for teams that want UI / dashboard / visibility. Packages: `casan-platform`, `casan-control-panel`. ## Components | Component | Status | Where | |---|---|---| | AgentOps Dashboard | ✅ exists | `packages/casan-harness/scripts/bash/dashboard-server.py` + `dashboard-serve.sh` (`casan dashboard`) | | **Ops Console (Control Panel)** | ✅ **monitoring + governed settings + HITL + kill-switch + FinOps/SLO + Command Center + Chat MVP-0/1 + agent selection foundation + local-prod TLS/OIDC smoke** | `packages/casan-control-panel/` — NestJS API + React UI over harness telemetry, settings management, approval inbox, kill-switch, FinOps/SLO, Command Center, Ask CASAN read-only, registered Operator actions, and governed agent/skill selection (`npm run console:api` + `console:ui`). Includes Run History + verdicts + governance + security + incidents + traceability + FinOps + Approvals + role-aware Settings page + `/command` evidence-backed executive view + `/chat` governed read-only/operator console. | | Management / settings writes | ✅ done+test | Plan-13 Track 2: wraps `control-plane-settings.py`, calls `rbac-check.py`, supports set/rollback/audit verify. | | RBAC + approval inbox | ✅ local-prod done | Settings + kill-switch API RBAC enforcement, approval inbox/delegation/oversight, SoD, governed setting proposal apply, and local OIDC claim→role mapping smoke are done. Enterprise IdP rollout remains production follow-up. | | Evidence Pack Viewer | 📋 planned | reads `docs/output/casan/evidence-packs/` | | Attack Battery Viewer | 📋 planned | reads red-team corpus + H4 recall results | | Read-only Ask CASAN + Operator/CODEGEN + agent selection + loop-hold + replay/widget/approvals + tenant hardening | ✅ MVP-0/1/2/3 done+test | Plan-18: `POST /api/v1/chat/ask`, `GET /api/v1/chat/actions`, `GET /api/v1/chat/agents`, `GET /api/v1/chat/replay`, Command Center `chat_loop` widget, chat escalation into `/approvals`, tenant-scoped replay, `/chat` + `/command`, backed by harness `chat-turn.py`, `chat-agent-resolver.py`, `chat-replay.py`, `approval-inbox.py`, `artifact-scan.sh`, `tenant-store.sh`, `tenant-crypt.sh`, and Plan-17 `loop-run.sh` | | Gitea webhook integration | 📋 planned | trigger gate / publish evidence on push | ## Build (preview) ```bash scripts/package-release.sh platform # → dist/casan-platform-preview-vX.Y.Z.tar.gz ``` The bundle includes a `PREVIEW-INCOMPLETE.txt` marker. Do not treat it as a finished product. ## To implement later Start from Plan-15 RAI view or the next backlog item. Keep new numbers evidence-backed with provenance; any write/governed action must continue to route through harness RBAC, approval, and audit primitives.