Files
CASAN/packaging/levels.json
T
thanhnvandClaude Opus 4.8 8c20cfde9f feat(packaging): level-based source hub — Core + DevKit packaging, Platform/Enterprise scaffold
Organize CASAN as a reusable source hub with SPLIT releases so downstream adopts only the
level it needs (packaging/levels.json is the single source of truth).

Implemented now:
- Level 1 Core: bin/casan CLI (run/gate/test/verify/reuse/dashboard) + VERSION.
- Level 2 DevKit: packages/casan-devkit (install.sh, Dockerfile.harness, templates:
  project scaffold, domain-pack, gitea-workflow).
- scripts/package-release.sh core|devkit|platform|all-in-one-demo — builds split bundles
  into dist/ (BUNDLE-MANIFEST + SHA256SUMS); platform is stamped PREVIEW/INCOMPLETE;
  enterprise (future) is REFUSED (exit 3, no fake-complete package). Bundles verified:
  extract → bin/casan works, deterministic + domain suites pass, casan reuse VALID.
- docs/packaging: CASAN_PACKAGING_PLAN + ADOPTION + CI + DOMAIN_PACK + GITEA_PACKAGE + DOCKER.

Structure + docs only:
- Level 3 packages/casan-platform (dashboard exists; control-panel/viewers pending).
- Level 4 packages/casan-enterprise (RBAC/tenant/KMS/WORM/approval exist in core; governed
  console pending). No Chat Console/RBAC-console/tenant-console/model-mgmt built in this task.

Harness change (enables extracted bundles to self-resolve): casan-paths.sh + the Python
project_root() walk-ups now accept a second root marker `packages/casan-harness` in addition
to `.specify`, so a freshly-unpacked core/devkit/demo bundle (no `.specify` yet) roots
correctly and creates state on first run. In an adopted repo `.specify` still matches first.
policy-bundle.yaml paths corrected to packages/casan-harness (re-signed). Full gate 64/0/3.

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

95 lines
5.3 KiB
JSON

{
"casan_packaging": "level-based source hub",
"version": "1.0.0",
"note": "Single source of truth for what each release bundle contains and its maturity. The repo is a source hub holding all levels; releases are SPLIT so downstream adopts only the level it needs. See docs/packaging/CASAN_PACKAGING_PLAN.md.",
"levels": {
"core": {
"level": 1,
"package_names": ["casan-core", "casan-harness"],
"status": "implemented",
"summary": "H1-H7 harness core, security/action gates, evidence pack, audit, cost/telemetry, hardening tests, policy/config defaults, lightweight CLI.",
"target_users": ["governance-harness-only projects", "BJT initial adoption", "CI gate usage"],
"includes": [
"packages/casan-harness/scripts",
"packages/casan-harness/security",
"packages/casan-harness/governance",
"packages/casan-harness/agentops",
"packages/casan-harness/config",
"packages/casan-harness/level5",
"packages/casan-harness/memory",
"packages/casan-harness/templates",
"packages/casan-harness/tests",
"packages/casan-harness/init-options.json",
"packages/casan-harness/README.md",
"bin/casan",
"VERSION"
],
"excludes_globs": ["**/__pycache__/**", "**/*.pyc", "**/.DS_Store"],
"artifact": "casan-core-v{VERSION}.tar.gz",
"docker_image": "casan-harness:{VERSION}"
},
"devkit": {
"level": 2,
"package_names": ["casan-devkit", "casan-project-kit"],
"status": "implemented",
"summary": "Level 1 + project templates, domain-pack scaffold, Gitea workflow templates, harness Dockerfile, install script, adoption/CI/domain-pack guides.",
"target_users": ["new projects adopting CASAN", "internal teams needing a repeatable setup"],
"extends": "core",
"includes": [
"packages/casan-devkit",
"docs/packaging/ADOPTION_GUIDE.md",
"docs/packaging/CI_GUIDE.md",
"docs/packaging/DOMAIN_PACK_GUIDE.md",
"docs/packaging/DOCKER_GUIDE.md",
"docs/packaging/CASAN_PACKAGING_PLAN.md",
"scripts/package-release.sh"
],
"artifact": "casan-devkit-v{VERSION}.tar.gz"
},
"platform": {
"level": 3,
"package_names": ["casan-platform", "casan-control-panel"],
"status": "preview",
"summary": "Optional productization UI: Control Panel, Dashboard, Evidence/Attack/Run-History viewers, read-only Ask CASAN, Gitea webhook. Only the AgentOps dashboard exists today; the rest is structure-only.",
"target_users": ["teams wanting UI/dashboard/visibility", "demo/training/productization"],
"extends": "devkit",
"implemented_components": ["agentops-dashboard (packages/casan-harness/scripts/bash/dashboard-server.py + dashboard-serve.sh)"],
"pending_components": ["control-panel", "evidence-pack-viewer", "attack-battery-viewer", "run-history-viewer", "read-only Ask CASAN", "gitea-webhook-integration"],
"includes": [
"packages/casan-platform",
"packages/casan-harness/scripts/bash/dashboard-server.py",
"packages/casan-harness/scripts/bash/dashboard-serve.sh"
],
"artifact": "casan-platform-preview-v{VERSION}.tar.gz",
"docker_image": "casan-platform:{VERSION} (preview)"
},
"enterprise": {
"level": 4,
"package_names": ["casan-enterprise", "casan-governed-console"],
"status": "future",
"summary": "Governed Chat Console, Prompt Mode Router, Model Provider Management, Operator/Codegen modes, Agent/Skill Registry, RBAC, approval workflow, tenant isolation, KMS/WORM, policy versioning.",
"target_users": ["enterprise/internal platform", "multi-project governance", "official governed AI-SDLC console"],
"extends": "platform",
"implemented_components": [
"RBAC (rbac-check.py)",
"tenant isolation (tenant-store.sh/tenant-paths.sh/tenant-registry-verify.sh/tenant-crypt.sh)",
"approval workflow (approval-verify.sh/approval-sign.sh/approval-jwt-mint.py)",
"KMS (vault-kms.sh)",
"WORM (worm-ledger.py)",
"kill-switch (kill-switch.sh)"
],
"pending_components": ["governed-chat-console", "prompt-mode-router", "model-provider-management", "operator-mode", "codegen-mode", "agent-skill-registry", "policy-versioning-ui"],
"includes": ["packages/casan-enterprise"],
"artifact": "casan-enterprise-preview-v{VERSION}.tar.gz",
"docker_image": "casan-enterprise:{VERSION} (future)"
}
},
"bundles": {
"core": {"builds": ["core"], "status": "implemented"},
"devkit": {"builds": ["core", "devkit"], "status": "implemented"},
"platform": {"builds": ["core", "devkit", "platform"], "status": "preview"},
"all-in-one-demo": {"builds": ["core", "devkit", "platform", "apps/okr/domain", "backend", "frontend", "docs/output/casan", "package.json", "package-lock.json", "Dockerfile.backend", "Dockerfile.frontend", "docker-compose.prod.yml"], "status": "implemented", "note": "Full runnable snapshot: harness + OKR app (backend/frontend) + OKR demo domain + latest evidence, for demo/training. The traceability gate needs the app source, so it is bundled here."},
"enterprise": {"builds": ["enterprise"], "status": "future", "note": "Refused by package-release.sh — Level 4 is structure-only; no fake-complete artifact."}
}
}