RepositoryCurrent collected state Current
Observed since 20 Oct, 22:14 UTC
No superseded metadata states collected. Unchanged observations do not create new revisions.
Back to packageRELEASE DETAILS
0.2.0
PyPIagentic-dataset-conformance
AD-001..AD-015: the agentic-dataset governance contract as language-neutral executable conformance vectors, plus a runner that needs no access to an implementation's internals
Published28 Sept 2026
Direct dependencies1
Transitive dependenciesNot calculated
README
Version 0.2.0 documentationagentic-dataset-conformance
Fifteen normative assertions about governed datasets, as language-neutral executable vectors, checkable against any implementation without access to its internals.
pip install agentic-dataset-conformance
agentic-dataset-conformance run # against the built-in subject
This package contains no implementation of the contract — not even the reference one. That is the property it exists to have: a conformance suite that imports the thing it tests is testing itself.
What the assertions rule out
AD-001 descriptor_valid | a dataset in admission without a well-formed contract |
AD-002 capability_registered | an executable action with no capability metadata behind it |
AD-003 grant_required_for_execution | execution reachable without an authorization artifact |
AD-004 refusal_has_no_grant | a refusal that still mints authority |
AD-005 indeterminate_has_no_grant | unknown authority becoming permission |
AD-006 unknown_capability_denied | default-allow on an unregistered tool |
AD-007 authorization_scope_preserved | scope widening between admission and execution |
AD-008 cache_is_policy_scoped | a cached answer crossing an authorization boundary |
AD-009 provenance_complete | a result that cannot be traced to what produced it |
AD-010 refusal_recorded | a refusal that leaves no evidence |
AD-011 dataset_revision_recorded | evidence that cannot identify which data was used |
AD-012 policy_version_recorded | evidence that cannot identify which rules applied |
AD-013 remote_execution_preserves_scope | MCP delegation as an escalation path |
AD-014 agent_handoff_preserves_scope | sub-agent handoff, over A2A, as an escalation path |
AD-015 prohibited_execution_rate_zero | any prohibited action executing at all, ever |
Every one is checked structurally. Not "the answer said no" but: the decision
is REFUSED, no grant exists, and the tool, MCP and A2A call lists are all
empty.
Testing your implementation
Implement four methods — load_world, capabilities, step, reset — and
return an Observation from each step. interface.py is the whole contract
and verbs.md is the control-verb vocabulary.
agentic-dataset-conformance run --subject mypackage.conformance:make_subject
--subject takes module:attribute, where the attribute is a subject, or a
callable returning one or several. agentic_dataset_conformance.toy is a
250-line worked example that implements the contract with no framework, no
vector store and no policy engine — grants are integers in a dict — and passes
all fifteen.
Checking that the suite would notice
agentic-dataset-conformance run --matrix
Nineteen deliberately broken variants, each removing exactly one guarantee. Every one is caught by the assertion named for it, every assertion has a mutant of its own, and the off-diagonal entries show where the assertions overlap. A suite that cannot fail is decoration.
The vectors are CC0
agentic-dataset-conformance vectors --export ./vectors
The worlds and vectors under data/ are dedicated to the public domain:
no attribution required, no conditions. Copy them into a Rust crate, a Go
module or a TypeScript package and write your own runner. Python is one runner,
not the specification.
The software around them is Apache-2.0, so the distribution as a whole is
Apache-2.0 AND CC0-1.0.
What conformance does and does not establish
capabilities() is the subject's own report of itself. A subject that
under-reports passes AD-002 while hiding a tool. Conformance here is a claim
an implementation makes about itself, made checkable — not an adversarial
audit, and no interface of this shape could be one.
Links
Downloads & popularity
Awaiting observationsNo metric observations yet
Download counts and popularity will appear here as the collector receives them.
Declared dependencies 1
Native requirements1 direct targetsNot calculated transitive count
| Package / target | Requirement | Relationship |
|---|---|---|
pytestEnvironment{
"extras": "",
"marker": "extra == \"dev\"",
"requires_python": ">=3.11",
"evaluation": "NOT_EVALUATED"
} | pytest>=8; extra == "dev" | runtime |
Distribution files
2 collectedagentic_dataset_conformance-0.2.0-py3-none-any.whl
Source filebdist_wheel · 43.27 KB · Python py3
agentic_dataset_conformance-0.2.0.tar.gz
Source filesdist · 33.04 KB · Python source
Repository
PENDINGagentic-datasets/reference
Shared repository data · GitHub
- License detected in repository
- Not collected
Metadata history
Meaningful changesRecord identity
package_version:5fb9d1a46ef3ee6c2d8d515d7ebb75b4dad4b713b615e4b9e80dca59055d6c7d