Files
CASAN/packages/casan-platform/README.md
T
thanhnvandClaude Opus 4.8 63dd44a11b feat(plan-13): read-only Ops Console (NestJS API + React UI) — Track 1
Real web Control Panel over CASAN harness telemetry (Level-3 casan-platform component).
Read-only ("Đọc ≠ Ghi"): no settings writes, no gate bypass. Management/RBAC/approval are
Track 2/3 (future, Plan-14). Additive — harness gate untouched (64/0/3).

packages/casan-control-panel/
- backend/ (NestJS, ESM, /api/v1 + ok() envelope): TelemetryReader (jsonl/json, missing→[],
  never fabricates) + TelemetryService (aggregations mirroring generate-agentops-dashboard.py)
  + endpoints overview/runs(+:traceId)/governance/security/incidents/tools/traceability/
  drift/cost, and /healthz (stale-aware 200/503, fail-loud like dashboard-server.py). App
  root + telemetry paths resolve via casan-paths-style marker walk-up (.specify OR
  packages/casan-harness) + honor CASAN_DASHBOARD_* env. Binds 127.0.0.1; refuses
  non-loopback under CASAN_PROFILE=prod. @Inject token so DI works under tsc AND tsx.
  Tests (node native runner) 7/0: reader parse/missing, app-root, overview shape on real
  repo state, freshness/stale fail-loud.
- frontend/ (React+Vite+Tailwind+TanStack, port 5174, proxies to :3010): AppLayout +
  Sidebar + Header (LIVE/STALE badge from /healthz) + pages Overview/Runs/Governance/
  Security/Incidents/Traceability. axios client unwraps ok() envelope. build green.

Wiring: root workspaces + `console:*` scripts. packaging/levels.json + casan-platform
README: platform preview now lists the Ops Console as an implemented component.

Verified: backend build + test 7/0; frontend tsc + vite build; API serves REAL data
(runs=6, provider_tokens=5556, action_blocks=7); /healthz 503 stale → 200 after touch.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-08 16:59:56 +09:00

1.9 KiB

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)
Ops Console (Control Panel) ✅ read-only (Plan-13 Track 1) packages/casan-control-panel/ — NestJS API + React UI over harness telemetry (npm run console:api + console:ui). Includes Run History + verdicts + governance + security + incidents + traceability views.
Management / settings writes 📋 planned Plan-13 Track 2 (wrap control-plane-settings.py)
RBAC + approval inbox 📋 planned Plan-13 Track 3 / Plan-14
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 📋 planned Plan-18 MVP-0 (read-only)
Gitea webhook integration 📋 planned trigger gate / publish evidence on push

Build (preview)

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.