# AI-Optimized Structure

## Why Optimize

The project now contains source files, policy files, generated evidence, dashboards, and reports. For humans and AI reviewers, the risk is context overload. The optimized structure should separate:

- Entry points
- Runtime harness
- Evidence
- Presentation materials
- Generated logs

## Recommended Top-Level Structure

```text
Output_CASAN5_REFINED/
├── README_CASAN4_DELIVERABLE.md
├── AINative_OKR_CASAN5.zip
├── AINative_OKR_CASAN5/
│   ├── .claude/
│   ├── .github/
│   ├── .specify/
│   │   ├── scripts/bash/          # executable harness controls
│   │   ├── security/              # H4 policies
│   │   ├── governance/            # H5 policies
│   │   ├── agentops/              # H6 policies
│   │   ├── level5/                # Level 5 configs
│   │   └── tests/                 # verification suite
│   └── docs/output/casan/         # reports and evidence
└── 00_SUBMISSION_PACKAGE/
    ├── README.md
    ├── docs/
    ├── presentation/
    ├── video/
    ├── evidence/
    └── ai_context/
```

## AI Reading Order

1. `00_SUBMISSION_PACKAGE/README.md`
2. `00_SUBMISSION_PACKAGE/ai_context/AI_README.md`
3. `AINative_OKR_CASAN5/docs/output/casan/before-after-scorecard.md`
4. `AINative_OKR_CASAN5/docs/output/casan/evidence/harness-test-report.md`
5. `AINative_OKR_CASAN5/.claude/agents/protocols/casan-harness-protocol.md`
6. `AINative_OKR_CASAN5/.specify/tests/run-casan4-harness-tests.sh`

## Markdown Optimization Rules

- Keep one claim per section.
- Link each claim to one evidence path.
- Separate Level 4 achieved from Level 5 demonstrated.
- Put commands in fenced code blocks.
- Keep Q&A concise and adversarial.
- Avoid long raw logs in narrative files; link to logs instead.