thanhnvandClaude Opus 4.8
664bd1f00c
Physically move the pure-code subtrees out of .specify into the package, leaving compat symlinks at the old .specify/<dir> paths so every existing reference (internal CASAN_HARNESS_ROOT + external CI/docker/mjs) keeps resolving. Runtime state stays put. Moved (git mv): scripts/ tests/ security/ templates/ config/ governance/ memory/ .specify/<dir> -> packages/casan-harness/<dir> (+ .specify/<dir> symlink) Stays in .specify (state/governance/domain, handled later): logs/ agentops/ level5/ init-options.json traceability-map.json Python `.resolve()` self-location followed the compat symlink into packages and lost the app root; generate-casan-demo-context.py, generate-agentops-dashboard.py and dashboard-server.py now walk UP for the `.specify` state marker instead of a fixed parent depth (fixes "missing trace files" in run-casan4). Full gate: PASS=64 FAIL=0 SKIP=3 (CASAN_CI_STEP_TIMEOUT_SEC=1200 — track-a ~450s runs close to the 600s default and can tip over under load; this is timing variance, not a regression — it passed cleanly with headroom). Runtime log/audit artifacts kept unstaged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
18 lines
606 B
Plaintext
18 lines
606 B
Plaintext
# CASAN — Incident severity map (C7 / V23). Line format: <event-type> <severity>
|
|
# severity ∈ LOW | MED | HIGH | CRIT. HIGH/CRIT auto-engage the kill-switch.
|
|
# Mirrors the Plan-07 C0 severity table.
|
|
secret-to-cloud CRIT
|
|
tool-write-sensitive CRIT
|
|
private-key-exposure CRIT
|
|
dependency-postinstall HIGH
|
|
dependency-malicious HIGH
|
|
audit-chain-broken HIGH
|
|
telemetry-tamper HIGH
|
|
sandbox-escape HIGH
|
|
evidence-pack-tampered HIGH
|
|
cost-budget-exceeded MED
|
|
benign-fp-exceeded MED
|
|
drift-detected MED
|
|
approval-forged HIGH
|
|
default MED
|