Skip to content
DraconiticResearch
Search Sources API
197,787 studies31 sourcesUpdated 42 min ago
PreprintCC BY 4.0arXiv

Benchy: towards a universal language for task-oriented AI benchmarks

Abstract

Benchy is a semantic language and execution engine for benchmarking AI programs. A benchmark is completely specified by a program, a scoring function, and a dataset, B=(P,S,D), and is separate from the AI-system taking it; a run binds the two, R=(B,AI). Benchmarks are authored as canonical YAML in which each semantic concept has one valid syntax, classified by a shared task/domain/language ontology, and deterministically compiled into a canonical JSON intermediate representation that the engine executes. Compilation changes representation, not meaning: it does not repair invalid definitions or inject hidden defaults. Programs use fixed schemas of named input and output fields, the leaf output fields are the scoring dimensions, and the engine exposes one universal runtime contract --- a named-field input object in, a named-field output object out --- to which external AI-systems adapt at the boundary, so integration mechanics never propagate into benchmark semantics. This paper gives the semantic object model, the ontology and task-to-program validation rule, the scoring and failure semantics, the compilation and execution architecture, and the scope of the current language. An appendix fixes the normative engineering contract for the first engine implementation.

Related

  1. Task- and Session-Level Model Routing: A Common-Interface Hybrid Evaluation of Four Open-Source Routers Across Four Benchmarks
    Kiran N. Kumar, Santhosh K. Saminathan
    arXivPreprintCC BY 4.0Full textStatisticsarXiv
  2. MAP-Based Task-Oriented Precoding for Multiuser Communication
    Mohammad Javad Ahmadi, Zhentian Zhang, Rafael F. Schaefer +1
    arXivPreprintCC BY 4.0Full textGeneral mathematicsarXiv
  3. Task-Oriented Quantization for Quadratic Scheduling: Centroid Water-Filling and Power-Diagram Encoders
    Joss Armstrong
    arXivPreprintarXiv licenceFull textGeneral mathematicsarXiv
  4. AI-Native Task-Oriented Semantic Communications over a Relay: Benefits and Vulnerabilities
    Yalin E. Sagduyu, Tugba Erpek, Aylin Yener
    arXivPreprintarXiv licenceFull textGeneral mathematicsarXiv
  5. More Interactions Make Communications More Efficient: A Directed Information Bottleneck Approach to Task-Oriented Communication
    Zhirun Zheng, Yiqin Deng, Phone Lin +1
    arXivPreprintCC BY 4.0Full textGeneral mathematicsarXiv
BibTeX
@misc{daniel2026benchy,
  title = {{Benchy: towards a universal language for task-oriented AI benchmarks}},
  author = {Francis F Daniel and Mauro Ibañez and Francis Perelman and Marian Basti},
  howpublished = {arXiv},
  year = {2026},
  month = sep,
  doi = {10.48550/arxiv.2609.30550},
  eprint = {2609.30550},
  archivePrefix = {arXiv},
  url = {https://arxiv.org/abs/2609.30550},
  note = {CC BY 4.0},
}
RIS
TY  - UNPB
TI  - Benchy: towards a universal language for task-oriented AI benchmarks
AU  - Francis F Daniel
AU  - Mauro Ibañez
AU  - Francis Perelman
AU  - Marian Basti
PY  - 2026
DA  - 2026/09/24
PB  - arXiv
DO  - 10.48550/arxiv.2609.30550
UR  - https://arxiv.org/abs/2609.30550
AB  - Benchy is a semantic language and execution engine for benchmarking AI programs. A benchmark is completely specified by a program, a scoring function, and a dataset, B=(P,S,D), and is separate from the AI-system taking it; a run binds the two, R=(B,AI). Benchmarks are authored as canonical YAML in which each semantic concept has one valid syntax, classified by a shared task/domain/language ontology, and deterministically compiled into a canonical JSON intermediate representation that the engine executes. Compilation changes representation, not meaning: it does not repair invalid definitions or inject hidden defaults. Programs use fixed schemas of named input and output fields, the leaf output fields are the scoring dimensions, and the engine exposes one universal runtime contract --- a named-field input object in, a named-field output object out --- to which external AI-systems adapt at the boundary, so integration mechanics never propagate into benchmark semantics. This paper gives the semantic object model, the ontology and task-to-program validation rule, the scoring and failure semantics, the compilation and execution architecture, and the scope of the current language. An appendix fixes the normative engineering contract for the first engine implementation.
ER  -