gitea-admin/CASAN
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: align all documentation with the new repo structure

Browse Source 
Update agent protocols (.claude/agents, .github/agents), guides, runbooks and READMEs
to the post-restructure layout: .specify/{scripts,tests,security,config,templates,
governance,memory,level5-config} -> packages/casan-harness/...; docs/input +
golden-runs + traceability-map -> apps/okr/domain/...; drop AINative_OKR_CASAN5/ prefix.
Runtime-state paths (.specify/logs, .specify/agentops, .specify/level5/central-governance)
kept as-is. Historical evidence under docs/output/ left untouched (immutable run records).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
thanhnv
2026-07-08 14:36:27 +09:00
co-authored by Claude Opus 4.8
parent 36a4812ef3
commit 18997caf49
53 changed files with 167 additions and 167 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/agents/okr.bossbuiltin.md
+9 -9
View File
@@ -151,10 +151,10 @@ report-nn: <NN> # for speckit.implement only
report-phase: <phase> # for speckit.implement only
casan-harness:
required: true
h4-security: ".specify/scripts/bash/security-check.sh"
h5-governance: ".specify/scripts/bash/governance-check.sh"
h6-agentops: ".specify/scripts/bash/agent-metrics.sh"
wrapper: ".specify/scripts/bash/casan-harness.sh"
h4-security: "packages/casan-harness/scripts/bash/security-check.sh"
h5-governance: "packages/casan-harness/scripts/bash/governance-check.sh"
h6-agentops: "packages/casan-harness/scripts/bash/agent-metrics.sh"
wrapper: "packages/casan-harness/scripts/bash/casan-harness.sh"
evidence:
trace-dir: ".specify/logs/trace"
audit-log: ".specify/logs/audit/audit.jsonl"
@@ -174,20 +174,20 @@ For every delegated step, Boss MUST:
1. Write the step input payload to `docs/output/output_logs/<feature-id>/casan/<step>-input.txt`.
2. Run H4 input security:
```bash
.specify/scripts/bash/security-check.sh <step-input> <safe-input> input
packages/casan-harness/scripts/bash/security-check.sh <step-input> <safe-input> input
```
3. Run H5 governance:
```bash
.specify/scripts/bash/governance-check.sh <safe-input> <approved-input> <action-name>
packages/casan-harness/scripts/bash/governance-check.sh <safe-input> <approved-input> <action-name>
```
4. Execute the real agent/tool step under H6 metrics:
```bash
CASAN_AGENT_NAME=<agent> CASAN_STEP_NAME=<step> \
.specify/scripts/bash/agent-metrics.sh <approved-input> <raw-output> -- <real command>
packages/casan-harness/scripts/bash/agent-metrics.sh <approved-input> <raw-output> -- <real command>
```
5. Run H4 output security:
```bash
.specify/scripts/bash/security-check.sh <raw-output> <final-output> output
packages/casan-harness/scripts/bash/security-check.sh <raw-output> <final-output> output
```
6. Update `pipeline-context.yaml` with the H4/H5/H6 trace paths and status.
@@ -204,7 +204,7 @@ Side-effecting action names:
High-risk actions are denied by default unless `CASAN_APPROVAL_DECISION=approve` and `CASAN_APPROVER=<name>` are set in the environment. Boss must log denied actions and stop that action instead of bypassing governance.
For side-effecting actions, Boss MUST also call `.specify/scripts/bash/tool-registry-gate.sh <action-name>` with `CASAN_IDEMPOTENCY_KEY` set. Cache hits are allowed only when H4 input, H5 governance, H6 metrics, and H4 output evidence are still written for the current run.
For side-effecting actions, Boss MUST also call `packages/casan-harness/scripts/bash/tool-registry-gate.sh <action-name>` with `CASAN_IDEMPOTENCY_KEY` set. Cache hits are allowed only when H4 input, H5 governance, H6 metrics, and H4 output evidence are still written for the current run.
---