Citation
The software carries a CITATION.cff, which GitHub renders as Cite this
repository.
v0.1.0 does not exist yet, so do not cite it. During the release
candidate, cite the tag and the commit:
Chernov, A. (2026). Agentic Dataset Reference Implementation and
Conformance Suite (v0.1.0-rc.2) [Computer software].
https://github.com/agentic-datasets/reference
A commit SHA is better still, because a release candidate is expected to move: the point of the window is that findings change the artifact.
ORCID: 0009-0007-3198-2712
There is no DOI yet. One will be minted from the v0.1.0 tag once the
window closes.
Citing an assertion
The identifiers AD-001 … AD-015 are stable and may be referred to freely.
Cite the assertion, not a line number:
…refuses on an unregistered capability (AD-006) and records the refusal (AD-010).
Citing the metric
Authorized Recall@K is defined in its own package, which has no dependency on this architecture. If you use the metric without adopting the control plane, cite the package rather than the reference implementation.
Papers
Three conference papers argue the model. All were accepted for 2026 and none is in published proceedings yet, so there are no DOIs to cite.
| Venue | Title |
|---|---|
| IEEE CCECE 2026 | Agentic Datasets as an Engineering Control Plane |
| IEEE EMBC 2026 | Dataset Descriptors for Autonomous and Observable Biomedical Data Pipelines |
| IEEE BigDataService 2026 | Agentic Data Services: A Control-Plane Architecture for Adaptive Data Workflows |
Nothing in this repository depends on them: the assertions, the vectors and the measurements are reproducible from a clone.