tokitai-operator 0.1.0

Verified DL kernel compiler: formally-checked GEMM, p-adic, sheaf, contract-carrying ops. Paper-artifact grade.
Documentation
# Release Progress (P370)

This document tracks the status of each `*_claim_allowed` flag in
`CLAIMS.md` and each required paper-submission artifact. It is the
single dashboard a reviewer or contributor can read in 2 minutes to
understand the project's release state.

**Generated by:** P370 (2026-06-05).
**Sync source:** `cargo run --offline --example claim_status_report`
prints the same data as text.
**Authoritative source of claim values:** `CLAIMS.md` lines 17-29.

## Claim flags (8 total)

| Flag | Value | Status | What unblocks |
|------|-------|--------|---------------|
| `primary_claim_allowed` | true | done | supported by code + tests; see `src/verify/release_gate.rs` |
| `production_speedup_claim_allowed` | false | blocked-external | reviewed external baseline + profiler capture + repeated timings + measured speedup (P374) |
| `portable_rocm_claim_allowed` | false | blocked-external | ≥2 reviewed passing device/compiler combinations (P375) |
| `verified_hip_machine_code_claim_allowed` | false | blocked-external | HIP bitcode inspection OR formal proof of kernel correctness (P376) |
| `full_formalization_claim_allowed` | false | partial | `lean/Tokitai/Ultrametric.lean` skeleton (P372) added; full mechanical verification is P377 |
| `sci_q2_claim_allowed` | false | blocked-external | all C10 paper claims verified end-to-end (P378) |
| `submission_readiness_claim_allowed` | false | partial | LICENSE (P368) and CITATION.cff (P367) added; remaining work in P379 |
| `acceptance_probability_claim_allowed` | false | blocked-external | statistical analysis + complete submission package (P380) |

Status legend:
- **done** — the flag is `true` and the supporting evidence is
  sufficient.
- **blocked-external** — unblocking requires evidence that cannot
  be produced in this development environment (multi-vendor hardware
  access, reviewer-style audits, external baselines).
- **partial** — some supporting work is in this repo, but more is
  needed before the flag can flip.

## Required artifacts (10 total)

| Artifact | Status | Path / next |
|----------|--------|-------------|
| `LICENSE` (Apache-2.0) | done | `LICENSE` (P368) |
| `CITATION.cff` | done | `CITATION.cff` (P367) |
| `CHANGELOG.md` | done | `CHANGELOG.md` (P360) |
| `CONTRIBUTING.md` | done | `CONTRIBUTING.md` (P361) |
| `docs/operators.md` | done | `docs/operators.md` (P364) |
| `docs/theory_support_matrix.md` | done | auto-generated from `src/verify/support_matrix.rs` (P355) |
| `target/paper-results/paper-results.{json,csv}` | done | regenerated by `scripts/regenerate_paper_artifacts.sh` (P371) |
| `lean/Tokitai/Ultrametric.lean` (proof skeleton) | partial | P372; full mechanical verification is P377 |
| Comparative baseline benchmark | missing | P374; `criterion` benchmarks (P358) are characterization, not comparison |
| Cross-vendor ROCm portability matrix | missing | P375; current matrix is local-only |

## Cross-references

- `CLAIMS.md` — authoritative source of the 8 flags.
- `CHANGELOG.md` — what changed in P335-P373.
- `CONTRIBUTING.md` — the 7-step process for adding a new op.
- `docs/operators.md` — the public operator surface index.
- `docs/theory_support_matrix.md` — auto-generated support matrix.
- `examples/claim_status_report.rs` (P366) — single-command
  one-page report; `rg claim_allowed=false` on its output
  reports 7 (the 7 blocked flags).
- `tests/support_matrix_coverage.rs` (P359) — fail-closed walk.
- `tests/witness_proof_replay.rs` (P357) — proof-replay
  witness section tests.
- `tests/proptest_stress.rs` (P363) — 10k-case stress tests.
- `benches/ops.rs` and `benches/finite_field.rs` (P358) —
  criterion benchmarks for the new surface.

## How to update this file

1. After each P-numbered phase lands, re-run
   `cargo run --offline --example claim_status_report` to get the
   current flag values.
2. Update the rows in the two tables above.
3. Update the "Generated by" line.
4. Commit with the phase number in the message
   (`docs: P### release progress update`).

When a flag's value flips from `false` to `true`, also update
`CLAIMS.md` (in a P-numbered commit; see the carry-over list for
`submission_readiness_claim_allowed`).