# v0.3.0-alpha Release Approval Checkpoint

Approval checkpoint date: 2026-05-07

Current public HEAD reviewed: `7826cd12b0319679ad8d54bcd6c002e275788ce2`

Release candidate label: `v0.3.0-alpha`

Status: release approval checkpoint for a future `v0.3.0-alpha` release decision. This document does not approve or create a tag, GitHub Release, package version change, release asset upload, raw benchmark artifact upload, or claim expansion.

## Current Release-Preparation State

- Draft/pre-release changelog entry exists in `CHANGELOG.md`.
- Release validation packet exists: `docs/reports/v0.3.0-alpha-release-validation-packet.md`.
- Reviewer-facing runtime evidence guide exists: `docs/reports/v0.3.0-alpha-runtime-evidence-reviewer-guide.md`.
- Release-readiness checklist exists: `docs/reports/v0.3.0-alpha-release-readiness-checklist.md`.
- Docs cross-link and public claim-boundary audit exists: `docs/reports/v0.3.0-alpha-docs-claim-audit.md`.
- Runtime evidence architecture design exists: `docs/design/v0.3.0-runtime-integrated-benchmark-evidence-architecture.md`.
- Initial runtime-path benchmark harness exists.
- Runtime benchmark JSON output path exists.
- Markdown evidence packet/report generator exists.
- Telemetry-connected runtime benchmark summary path exists.

## Validation Commands Required Before Release

- `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_task183.json`
- `python3 examples/runtime_integrated_benchmark/report.py --input /tmp/kora_runtime_integrated_benchmark_task183.json --md-out /tmp/kora_runtime_integrated_benchmark_task183.md`
- `python3 -m kora telemetry --input /tmp/kora_runtime_integrated_benchmark_task183.json --json-out /tmp/kora_runtime_integrated_benchmark_task183.telemetry.json --md-out /tmp/kora_runtime_integrated_benchmark_task183.telemetry.md`

## 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

## Release Actions Requiring Explicit Approval

The following actions require explicit human approval before execution:

- creating tag `v0.3.0-alpha`
- creating GitHub Release `v0.3.0-alpha`
- marking the release as prerelease or latest
- uploading any release asset
- uploading any raw benchmark artifact
- changing package version

## Recommended Approval Wording

Use explicit approval wording in a future task. Examples:

- "Approved: create tag v0.3.0-alpha only."
- "Approved: create GitHub Release v0.3.0-alpha as prerelease only."
- "Approved: no release assets."
- "Approved: do not upload raw benchmark artifacts."

## Release Blocker Checklist

Do not proceed with release execution if any of these are true:

- tests are failing
- runtime benchmark counters mismatch
- telemetry counters mismatch
- unsafe claim wording is present
- generated benchmark JSON, Markdown evidence packet, or telemetry outputs are staged or committed
- package version change is present without explicit approval
- release asset upload is not explicitly approved
- raw benchmark artifact upload is not explicitly approved

## Final Recommendation

Prepare release execution only after explicit human approval. If approved, the next task should create tag only, or create tag plus GitHub Release, depending on the exact approval wording.

Do not proceed automatically.
