# v0.3.0-alpha Release Validation Packet

Validation date: 2026-05-07

Public HEAD reviewed: `0e777b56eb384e3b4675df42a5966ca162309670`

Status: release-preparation validation packet for a future `v0.3.0-alpha` release decision. This packet prepares for release review only. It does not approve or create a tag, GitHub Release, package version change, release asset upload, raw benchmark artifact upload, or claim expansion.

## Release-Preparation Status

- Validation packet prepared.
- No tag created.
- No GitHub Release created.
- No release assets uploaded.
- No raw benchmark artifacts uploaded.
- No package version change included.

## Files Reviewed

- `README.md`
- `CHANGELOG.md`
- `docs/README.md`
- `experiments/README.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/reports/v0.3.0-alpha-docs-claim-audit.md`
- `examples/runtime_integrated_benchmark/run.py`
- `examples/runtime_integrated_benchmark/report.py`
- `tests/test_runtime_integrated_benchmark.py`
- `docs/telemetry-and-observability.md`

## Validation Commands

- `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_task179.json`
- `python3 examples/runtime_integrated_benchmark/report.py --input /tmp/kora_runtime_integrated_benchmark_task179.json --md-out /tmp/kora_runtime_integrated_benchmark_task179.md`
- `python3 -m kora telemetry --input /tmp/kora_runtime_integrated_benchmark_task179.json --json-out /tmp/kora_runtime_integrated_benchmark_task179.telemetry.json --md-out /tmp/kora_runtime_integrated_benchmark_task179.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_task179.json`: passed.
- Markdown evidence packet generation to `/tmp/kora_runtime_integrated_benchmark_task179.md`: passed.
- Telemetry JSON and Markdown generation to `/tmp/kora_runtime_integrated_benchmark_task179.telemetry.json` and `/tmp/kora_runtime_integrated_benchmark_task179.telemetry.md`: passed.

## Expected Runtime Benchmark Counters

| Counter | Expected value |
|---|---:|
| `total_tasks` | `100` |
| `deterministic_route_count` | `80` |
| `fallback_or_model_candidate_route_count` | `20` |
| `simulated_baseline_model_invocations` | `100` |
| `kora_controlled_model_invocations` | `20` |
| `avoided_simulated_model_invocations` | `80` |
| `avoided_simulated_model_invocation_rate` | `0.8` |
| `deterministic_outputs_checked` | `80` |
| `mismatch_count` | `0` |
| `runtime_path_execution_status` | `ok` |
| `telemetry_event_count` | `100` |

## Expected Telemetry Counters

| Counter | Expected value |
|---|---:|
| `total_llm_calls` | `20` |
| `events_ok` | `100` |
| `events_fail` | `0` |
| `events_skipped` | `0` |
| `stage_counts.ADAPTER` | `20` |
| `stage_counts.DETERMINISTIC` | `80` |

## 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 yet
- broad workload superiority proof
- energy reduction evidence
- formal government validation
- signed partner validation unless actually signed and documented
- guaranteed adoption or funding

## Artifact Policy

- Generated benchmark JSON outputs stay in `/tmp` or user-provided ignored output paths.
- Generated Markdown evidence packets stay in `/tmp` or user-provided ignored output paths unless a future release task explicitly selects a reviewed public report.
- Generated telemetry JSON and Markdown summaries stay in `/tmp` or user-provided ignored output paths.
- Generated raw benchmark artifacts are not committed.
- No release assets are uploaded without explicit approval.

## Release Restrictions

- No `v0.3.0-alpha` 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.

## Release Decision Checkpoint

This packet prepares for release review only. Any release action requires explicit approval in a later task.

Recommended next step after this packet is reviewed: review the [`v0.3.0-alpha release approval checkpoint`](v0.3.0-alpha-release-approval-checkpoint.md), open a PR for that release-approval checkpoint branch, merge if safe, refresh local project context, and then request explicit approval before any tag or GitHub Release task.
