thanhnvandClaude Opus 4.8
3e7f76f6f5
Empty package/app skeleton for the harness restructure. No harness files moved yet; full gate baseline stays PASS=64 FAIL=0 SKIP=3. Subdirs materialize via git mv in Phases 1-5. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
18 lines
967 B
Markdown
18 lines
967 B
Markdown
# casan-harness (package skeleton)
|
|
|
|
Core CASAN harness (gate H1→H7) as a reusable package, independent of domain data.
|
|
Populated incrementally by Plan-01 (Phase 0→6). During migration, files move here from
|
|
`.specify/` wave-by-wave; the full harness gate must stay green (`PASS=64 FAIL=0`) after each phase.
|
|
|
|
Layout:
|
|
- `scripts/` — bash + powershell gate logic (H1→H7), path resolver `casan-paths.sh`
|
|
- `security/` — filter/policy rules (prompt-filter, pii-rules, output-policy, ...)
|
|
- `governance/`, `agentops/` — H5/H6 code
|
|
- `level5/` — L5 config (drift/kpi/model-fallback/tool-registry YAMLs)
|
|
- `templates/`, `config/` — spec/plan templates, loop-policy
|
|
- `tests/` — reproducible harness test suites + integrity manifest
|
|
|
|
Runtime state (logs, audit chain, tenant state) is NOT part of this package — it stays with
|
|
the app under `CASAN_STATE_ROOT`. Domain data (golden-runs, corpus, input) lives in
|
|
`apps/okr/domain/` under `CASAN_DOMAIN_ROOT`.
|