File size: 3,667 Bytes
333b0b9 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 | ---
license: apache-2.0
language:
- en
pretty_name: DCP v1 Conformance Corpus
tags:
- json-schema
- validation
- conformance
- ai-agents
- multi-agent
- agent-protocols
- interoperability
size_categories:
- n<1K
configs:
- config_name: default
data_files: cases.jsonl
---
# DCP v1 Conformance Corpus
The official, language-neutral conformance test corpus of the **[Development Coordination Protocol (DCP)](https://devcopro.org)** — an open, vendor-neutral vocabulary for exchanging *project-coordination events* (a task completed, a decision recorded, a finding raised…) between AI agents and humans.
A DCP implementation, in **any language**, is conformant when it **accepts every `accept` case and rejects every `reject` case** in this corpus, validating each payload as a `DcpMessage` against the [DCP v1 JSON Schemas](https://schemas.devcopro.org/v1/dcp-message.schema.json) (JSON Schema 2020-12) **plus** the one cross-field rule schemas cannot express: `message_type` must equal `<body.entity_type>.<body.verb>` — on conflict, the body wins and the message is malformed.
## Contents
- **`cases.jsonl`** — all 25 cases (7 accept / 18 reject), one JSON object per line:
`case`, `file`, `expect` (`accept`/`reject`), `schema`, `note` (what the case probes), and the full `payload`.
- **`corpus/`** — the same corpus in its original layout: `valid/`, `invalid/`, and `manifest.json` (the machine-readable case list an implementation iterates).
## Quick start
```python
from datasets import load_dataset
cases = load_dataset("DevCoPro/dcp-conformance-corpus", split="train")
for case in cases:
result = my_validator(case["payload"]) # your implementation
assert result.ok == (case["expect"] == "accept"), case["case"]
```
Or language-neutral, straight from the original layout: iterate `corpus/manifest.json`, validate each `file` against the schema base `https://schemas.devcopro.org/v1/`, and compare with `expect`.
## What DCP is (and deliberately is not)
DCP standardizes **what changed in a project** — over a closed set of 8 coordination entities (Project, Task, Dependency, ArchitectureImpact, Decision, ReviewRequest, Finding, Milestone) with an open verb vocabulary. Its prime directive: **"DCP carries no trust; it describes project-state changes only."** It never authenticates, routes, plans, schedules, or executes — those belong to other layers, which is exactly why it composes with the rest of the 2026 agent-protocol stack:
- **[CloudEvents binding](https://devcopro.org/how-to/dcp-over-cloudevents/)** (normative) — a `DcpMessage` rides unchanged as CE `data`.
- **[A2A community extension](https://devcopro.org/a2a/dcp/v1/)** — DCP events in an A2A DataPart.
- MCP connects agents to tools; DCP is the payload vocabulary for the coordination conversation itself.
## Links
- Spec & docs: **https://devcopro.org** · [Specification](https://devcopro.org/spec/) · [Quickstart](https://devcopro.org/quickstart/)
- Source repository: **https://github.com/TokonoMix/development-coordination-protocol** (Apache-2.0 / CC-BY-4.0)
- Canonical schemas: https://schemas.devcopro.org/v1/dcp-message.schema.json (offline bundle + SHA256SUMS available)
## Citation
```bibtex
@misc{dcp-conformance-corpus,
title = {DCP v1 Conformance Corpus},
author = {{InterIP Networks}},
year = {2026},
url = {https://huggingface.co/datasets/DevCoPro/dcp-conformance-corpus},
note = {Conformance test corpus for the Development Coordination Protocol v1.0.0-draft}
}
```
Maintained by Mesut Kalkan (founding maintainer, InterIP Networks). Licensed Apache-2.0, same as the DCP schemas and examples.
|