CricketStudioOKF
Home/Spec/Conformance

Cricket OKF Conformance Levels

Five levels (0–4) for cricket OKF bundles. Each level includes all requirements of levels below it. Self-certification is honest — a bundle claims only the level it can demonstrate.

CricketStudio OKF self-certification

The cricketstudio-okf reference bundle is self-certified at Level 3 — Agent-Safe (July 2026). CI-validated on every PR via python scripts/validate_okf.py && pytest.

Level 0

Cataloged

Cricket data in OKF markdown files with type, title, and description. No provenance, metric definitions, or citation rules.

  • Every .md file has valid YAML frontmatter
  • Every file has a non-empty type field (cricket OKF vocabulary)
  • Every file has title and description
Level 1

Citable

Every file has a canonical URL and declared source boundary. Claims can be independently cited.

  • Every data-bearing file has canonical_page or resource (citable URL)
  • Every file declares source_boundary
  • Every file declares license
  • Every file declares source_system
Level 2

Evidence-Backed

Every data-bearing claim has traceable evidence, freshness date, metric definitions, and sample-size rules.

  • Every data-bearing file has provenance.source and provenance.confidence
  • Every file has last_verified (ISO date)
  • Metric files exist for every cited metric
  • Each metric file has: formula, floor, limitations, ranking rule
  • Methodology files exist for: sample-size floors, phase definitions, ranking eligibility
  • Ranking files declare floor and scope
Level 3

Agent-Safe

✓ self-certified

Machine-readable claim objects with structured evidence, eval cases, and agent usage rules.

  • Machine-readable claim objects (claim_id, entity_refs, metric_refs, evidence_refs, scope, sample_size, confidence)
  • JSON Schema for claim objects published
  • Evaluation cases published at /evals
  • Agent usage spec with machine-parseable rules
Level 4

Auditable

roadmap v1.0

Versioned releases with regression tests, published conformance reports, and external implementations.

  • Versioned schema releases with breaking-change documentation
  • Published conformance reports per release
  • Automated regression test suite
  • Eval results published per release
  • External implementation or community validation

How another provider uses this

Any cricket data provider can implement the cricket OKF profile — no license fee, no registration, no approval required.

  1. Use Google OKF v0.1 as the base format
  2. Follow the cricket type vocabulary
  3. Declare provenance per the provenance convention
  4. Write metric files per the metric standard
  5. Apply floors from the sample-size doctrine
  6. Self-certify at the level you achieve using the checklist above
← Spec indexFull conformance spec →Releases →