# v0.3.0-alpha Docs Claim Audit

Review date: 2026-05-07

Reviewed public HEAD: `4e4461c79495bf386185693415de0526ed681541`

Status: documentation cross-link and public claim-boundary audit for the bounded `v0.3.0-alpha` runtime evidence flow. This report does not approve a tag, GitHub Release, release asset upload, package version change, raw benchmark artifact upload, or claim expansion.

## Files Reviewed

- `README.md`
- `docs/README.md`
- `experiments/README.md`
- `CHANGELOG.md`
- `docs/design/v0.3.0-runtime-integrated-benchmark-evidence-architecture.md`
- `docs/reports/benchmark_artifact_policy.md`
- `docs/reports/v0.3.0-alpha-runtime-evidence-reviewer-guide.md`
- `docs/reports/v0.3.0-alpha-release-readiness-checklist.md`
- `docs/telemetry-and-observability.md`

## Cross-Link Audit Results

The current documentation links the `v0.3.0-alpha` runtime evidence flow through the expected entry points:

- Runtime evidence architecture design: `docs/design/v0.3.0-runtime-integrated-benchmark-evidence-architecture.md`
- Runtime benchmark command: `python3 -m kora run runtime_integrated_benchmark -- --offline`
- Runtime benchmark JSON output flow: `python3 -m kora run runtime_integrated_benchmark -- --offline --json-out /tmp/kora_runtime_integrated_benchmark.json`
- Markdown evidence packet flow: `python3 examples/runtime_integrated_benchmark/report.py --input /tmp/kora_runtime_integrated_benchmark.json --md-out /tmp/kora_runtime_integrated_benchmark.md`
- Telemetry summary flow: `python3 -m kora telemetry --input /tmp/kora_runtime_integrated_benchmark.json --json-out /tmp/kora_runtime_integrated_benchmark.telemetry.json --md-out /tmp/kora_runtime_integrated_benchmark.telemetry.md`
- Reviewer-facing runtime evidence guide: `docs/reports/v0.3.0-alpha-runtime-evidence-reviewer-guide.md`
- Release-readiness checklist: `docs/reports/v0.3.0-alpha-release-readiness-checklist.md`
- Benchmark artifact policy: `docs/reports/benchmark_artifact_policy.md`

One discoverability link was added from `docs/README.md` to this audit report.

## Claim-Boundary Audit Results

The public documentation was searched for the following risk terms:

- `production cost`
- `real API`
- `API-cost`
- `energy`
- `energy savings`
- `production benchmark`
- `full runtime-integrated`
- `superiority`
- `validated`
- `proof`
- `cost reduction`

Findings:

- Current `v0.3.0-alpha` runtime evidence docs use these terms in explicit non-claims, release restrictions, artifact policy notes, or historical/background contexts.
- The runtime evidence reviewer guide and release-readiness checklist preserve the claim boundary.
- No unsafe production cost, real API-cost, production benchmark, full runtime-integrated benchmark, broad workload superiority, formal validation, partner validation, guaranteed adoption, funding, or energy claim was found in the reviewed current evidence path.
- Older historical/background docs contain terms such as `superiority`, `validated`, and earlier benchmark notes, but the current docs index labels them as historical/background or routes readers to the current claim registry and public language guide.

## Safe Current Claim

> In a reproducible 100-task deterministic-heavy benchmark workload, KORA-controlled execution avoided 80 of 100 simulated model invocations versus a naive direct baseline.

## Explicit Non-Claims

KORA does not currently claim:

- production cost reduction proof
- real API-cost reduction proof
- production benchmark proof
- full runtime-integrated benchmark evidence
- broad workload superiority proof
- energy reduction evidence
- formal government validation
- signed partner validation unless actually signed and documented
- guaranteed adoption or funding

## Commands Validated

- `python3 -m pytest`
- `python3 -m kora run direct_vs_kora -- --offline`
- `python3 -m kora run runtime_integrated_benchmark -- --offline`
- `python3 -m kora run runtime_integrated_benchmark -- --offline --json-out /tmp/kora_runtime_integrated_benchmark_task175.json`
- `python3 examples/runtime_integrated_benchmark/report.py --input /tmp/kora_runtime_integrated_benchmark_task175.json --md-out /tmp/kora_runtime_integrated_benchmark_task175.md`
- `python3 -m kora telemetry --input /tmp/kora_runtime_integrated_benchmark_task175.json --json-out /tmp/kora_runtime_integrated_benchmark_task175.telemetry.json --md-out /tmp/kora_runtime_integrated_benchmark_task175.telemetry.md`

Validation result: passed on 2026-05-07.

- `python3 -m pytest`: 54 passed.
- `python3 -m kora run direct_vs_kora -- --offline`: passed.
- `python3 -m kora run runtime_integrated_benchmark -- --offline`: passed.
- Runtime JSON generation to `/tmp/kora_runtime_integrated_benchmark_task175.json`: passed.
- Markdown evidence packet generation to `/tmp/kora_runtime_integrated_benchmark_task175.md`: passed.
- Telemetry JSON and Markdown generation to `/tmp/kora_runtime_integrated_benchmark_task175.telemetry.json` and `/tmp/kora_runtime_integrated_benchmark_task175.telemetry.md`: passed.

## Generated-Artifact Policy Confirmation

- Runtime benchmark JSON outputs should stay in `/tmp` or user-provided ignored paths unless a future task explicitly changes artifact policy.
- Generated Markdown evidence packets should stay in `/tmp` or user-provided ignored paths unless a future task explicitly selects a reviewed public report.
- Telemetry JSON and Markdown summaries generated from benchmark runs should stay in `/tmp` or user-provided ignored paths unless explicitly approved.
- No generated benchmark JSON, generated Markdown evidence packet, generated telemetry summary, release asset, or raw benchmark artifact should be committed by this audit.

## Release Restrictions

- No tag without explicit approval.
- No GitHub Release without explicit approval.
- No release assets without explicit approval.
- No raw benchmark artifact upload without explicit approval.
- No package version change without explicit approval.
- No production/API-cost/energy, broad workload superiority, formal validation, partner validation, adoption, or funding claim expansion without reviewed evidence and explicit approval.

## Recommended Next Step

If maintainers approve moving toward `v0.3.0-alpha` release preparation, prepare a changelog and release validation packet next. Do not create a tag or GitHub Release yet.
