CricketStudioOKF
SpecificationMethodologyVerified 2026-06-22

Cricket OKF v0.3 — Cricket OKF Standards Layer

Release notes for CricketStudio OKF v0.3 (2026-06-22). Adds the formal Cricket OKF Standards layer — type vocabulary, provenance convention, metric standard, claim discipline, identity rules, sample-size doctrine, conformance levels, releases, and Google OKF alignment. Prepares a standalone contribution bundle for the Google OKF upstream repo.

Released: 2026-06-22

What's in v0.3

Cricket OKF Standards Layer (new in v0.3)

This is the major addition: a formal specification for the Cricket OKF domain profile, hosted at okf.cricketstudio.ai/spec.

okf/spec/ directory — 8 specification files:

File What it defines
spec/index.md Entry point, scope, relationship to Google OKF v0.1
spec/types.md 19 cricket OKF type values with definitions and example frontmatter
spec/provenance.md Provenance convention (source_boundary, confidence, freshness, license)
spec/metrics.md What every cricket metric file must include (10 required sections)
spec/claims.md Cricket claim discipline — scope, sample size, claim types, non-negotiables
spec/identity.md Entity identity rules — slug conventions, aliases, same-name disambiguation
spec/sample-size.md Sample-size floors (batting, bowling, H2H, venue, phase)
spec/conformance.md Conformance levels 0–4 and self-certification checklist

okf/releases/ directory — 3 release files:

  • releases/v0.1.md — v0.1 release notes (initial bundle)
  • releases/v0.2.md — v0.2 release notes (MLC enrichment)
  • releases/v0.3.md — this file

okf/sources/google-okf-alignment.md — new methodology file:

  • Documents how CricketStudio OKF fields map to Google OKF v0.1 recommended fields
  • Confirms cricketstudio-okf as a conformant Google OKF domain bundle

Google OKF Contribution Bundle (new in v0.3)

examples/cricket/ at the repository root contains a standalone cricket domain example bundle:

  • 13 files prepared as a PR contribution to GoogleCloudPlatform/knowledge-catalog
  • Demonstrates cricket type vocabulary, provenance convention, sample-size doctrine, and metric definitions
  • Clean: no internal paths, no proprietary data, CC BY 3.0 attribution where applicable
  • Canonial URLs point to okf.cricketstudio.ai (public, live)

Viewer Updates

  • /spec/* pages served by existing [...slug] catch-all (no new routes required)
  • /conformance dedicated styled page with conformance checklist UI
  • /releases dedicated styled page with release history
  • Header: "Spec" nav link added
  • Homepage: "Spec" and "Conformance" cards added; hero copy corrected (removed overreach language about CricketStudio.ai)

Schema Changes

  • Added spec to type enum in schema/frontmatter.schema.json

Validator Updates

  • Added soft warnings for Google OKF alignment: files with canonical_page but no resource, and files with last_verified but no timestamp

llms.txt Updates

  • Added /spec section with all spec page URLs
  • Added conformance level declaration
  • Added Google OKF alignment statement

Conformance Level

Level 2 — Evidence-Backed. Self-certified 2026-06-22 via CI (python scripts/validate_okf.py && pytest).

See spec/conformance for the full checklist and self-certification statement.

Breaking Changes

None. All existing files, slugs, and entity IDs are unchanged.

Migration Notes

No migration required for existing OKF consumers. The spec/ directory and releases/ directory are new paths; the [...slug] catch-all serves them without configuration changes.

Known Limitations at v0.3

  • Machine-readable claim objects (Level 3) are not yet implemented. Claims appear as verified prose in dossier files, backed by frontmatter provenance — not as structured JSON claim objects.
  • Eval cases (/evals) are not yet built. Planned for v0.4.
  • Agent usage rules are published in /agents as human-readable prose; not yet machine-parseable (Level 3 requirement).
  • MLC 2026 data is not yet included. Season 4 (started 2026-06-18) will be added after the season concludes.
cricketokfreleasespecstandard