Released: 2026-06-29 (versions 0.5.0 through 0.5.3)
What's in v0.5
Deep-Research Verified Content (Sprint 6)
v0.5 introduces OKF content generated from a 104-agent deep-research workflow with adversarial verification (3-vote majority per claim). Only claims reaching 2-of-3 or 3-of-3 agent agreement were published. Claims that failed verification are explicitly excluded and noted in affected files.
6 new adversarially verified dossier files:
| File | Key claim | Confidence |
|---|---|---|
suryavanshi-72-sixes |
72 sixes in IPL 2026 — IPL single-season record | 3-0 |
suryavanshi-youngest-500-runs-ipl |
Youngest to 500+ IPL season runs (15y 27d) | 2-1 |
kohli-9000-ipl-runs |
First batter to 9,000 IPL career runs (April 27 2026) | 3-0 |
kohli-ipl-2026-final |
75* off 42 balls, fastest IPL fifty (25 balls), PoM | 3-0 |
ipl-2026-chase-dominance |
8 of 12 early-phase matches won by chasers | 3-0 |
impact-player-rule-controversy-2026 |
Axar Patel opposition; top-5 run chases all post-2023 | 3-0 / 2-1 |
4 new advanced metric files (research gaps confirmed):
| File | Content |
|---|---|
fantasy-cricket-strike-rate |
Dream11 IPL SR tiers (-6 to +6 points), 10-ball minimum floor |
expected-runs-xR |
Delivery-difficulty-adjusted batting metric; academic concept (CricketSavant 2016) |
expected-wickets-xW |
50-nearest-neighbour wicket probability; academic concept (CricketSavant 2017) |
win-probability |
Two-model chain (first-innings + chase model); Win Probability Added (WPA) |
Claims excluded after verification failure:
- IPL 2026 Final specific scorecard (GT 155/8, RCB 161/5) — refuted 0-3 by secondary sources
- "All ten captains opposed the Impact Player Rule" — refuted 0-3
- "BCCI refused rule change until 2027" — refuted 0-3
- Suryavanshi prior-record holder single-season sixes count (Gayle's count) — refuted 0-3
4 Impact Player Narrative Stories (v0.5.1)
impact-player-captains-dilemma— "The Card You Can Only Play Once"impact-player-rule-alone— "The Rule That Only IPL Dared Try"impact-player-bowlers-displaced— "The All-Rounder's Dilemma"ipl-2026-most-impactful-player— "The Most Impactful Player of IPL 2026 (Both Meanings)"
SEO Schemas + Viewer
- FAQPage, BreadcrumbList, and Article JSON-LD on dossier and story pages
- Type-aware
<title>suffix enrichment per page type - WebSite schema + SearchAction on homepage (Google Sitelinks Searchbox)
- Per-page OG images: 135 unique images for stories, dossier, research, metrics (v0.5.2/v0.5.3)
.well-known/ai-plugin.json— OpenAI plugin manifest for agent discovery
Google OKF Alias Field Coverage
All 532 OKF files now include:
resource— alias forcanonical_page(Google OKF alignment)timestamp— alias forlast_verified(Google OKF alignment)
Validator result: 532 files, 0 errors, 0 warnings (was 681 warnings at v0.4).
scripts/fix_okf_aliases.py added as a reusable idempotent maintenance tool.
7 World-Class Sprint Dossiers + 5 Metrics (also in this release)
Dossiers: fastest-century-ipl, best-spin-bowler-ipl-2026, ipl-2026-best-team, best-powerplay-batter-all-time-ipl, ipl-vs-other-t20-leagues, ipl-salary-cap-explained, best-all-time-death-bowler-ipl
Metrics: net-run-rate, run-rate, average-vs-strike-rate, phase-split-economy, partnership-value
Bundle Size
532 files at initial release (2026-06-29) · 45 stories · 19 metrics · 83 dossiers. Bundle has grown substantially since — see manifest.yaml for current counts.
Conformance Level
Level 3 — Agent-Safe. Self-certified 2026-07-08.
Initial release (2026-06-29) shipped at Level 2. Elevated to Level 3 within the v0.5.x series when Trust OS v1 was committed on 2026-07-08, adding: machine-readable claim ledger (/claims.jsonl), JSON Schema (schema/claim-object.schema.json), eval benchmark (/evals/cricket-qa-v1.jsonl, 1,000 rows), and trust manifest (/trust-manifest.json).
python scripts/validate_okf.py → 0 errors, 0 warnings
pytest → 24 passed
Breaking Changes
None. All existing file paths and entity IDs unchanged.
Security
ROADMAP.md (internal Claude Code planning document) was inadvertently committed during this sprint and immediately removed. Added to .gitignore to prevent recurrence. No sensitive data, credentials, or proprietary feed data were exposed — confirmed by full repository security audit.