# CASAN Platform (Level 3 — Productization UI) · **PREVIEW / structure-only**

> Status: **PREVIEW.** Only the AgentOps **dashboard** exists today (shipped inside the core
> harness). The rest of the platform UI is scaffolded here as structure + intent — NOT
> implemented in this task. `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`) |
| Control Panel | 📋 planned | Plan-13 (`docs/plans/CASAN_PLAN_13_CONTROL_PLANE.md`) |
| Evidence Pack Viewer | 📋 planned | reads `docs/output/casan/evidence-packs/` |
| Attack Battery Viewer | 📋 planned | reads red-team corpus + H4 recall results |
| Run History Viewer | 📋 planned | reads `.specify/logs/level5/pipeline-run.jsonl` |
| Read-only Ask CASAN | 📋 planned | Plan-18 MVP-0 (read-only) |
| 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-13 (Control Plane) + Plan-18 MVP-0 (Ask CASAN read-only). Keep the UI
**read-only over harness artifacts** first; write/governed actions belong to Level 4.