A dataset that states what agents may do with it, and a contract that can be checked without seeing inside the implementation.

Specification plus reference implementation. The contract runs to fifteen assertions and eighty-five executable steps, portable across languages, and has been exercised against four runtimes, two dataset boundaries and one unrelated codebase — every one of them passing, with seventeen deliberately broken variants all caught.

An open specification and reference implementation for datasets that carry their own behavioural contract. A dataset declares the operations it admits and the conditions under which it admits them, so a caller can decide from the descriptor alone rather than by convention or by asking someone.

The contract is fifteen normative assertions expressed as eighty-five language-neutral vector steps, which is what makes it checkable against an implementation without access to that implementation's internals. The reference architecture passes all fifteen across four runtimes and two dataset boundaries; a second implementation sharing no code with it passes all fifteen as well.

Mutation analysis is the part that keeps the suite honest: seventeen targeted violations, seventeen detected, with every assertion independently exercised. Mean detecting assertions per mutant is reported at 2.2 and deliberately not treated as an optimization metric, because tuning a suite to raise it would measure the suite rather than the contract.

References

1. Gebru et al. (2021). Datasheets for datasets. Communications of the ACM 64(12), 86–92. doi:10.1145/3458723
2. Wilkinson et al. (2016). The FAIR Guiding Principles for scientific data management and stewardship. Scientific Data 3(1), 160018. doi:10.1038/sdata.2016.18
3. Jia and Harman (2011). An Analysis and Survey of the Development of Mutation Testing. IEEE Transactions on Software Engineering 37(5), 649–678. doi:10.1109/TSE.2010.62

agenticdatasets.orgLive showcasesReference implementationagentic-dataset-conformance on PyPI