About DCP
The Development Coordination Protocol (DCP) is an open, vendor-neutral, machine-readable semantic protocol for exchanging project-coordination events — task changes, decisions, findings, milestones — between AI agents and humans. It defines only the structure of those messages, over any transport, with no dependency on a specific vendor or product.
What DCP is
Section titled “What DCP is”DCP describes project-state changes: a task completed, a decision recorded, a finding raised. It does not authenticate, authorize, route, plan, schedule, orchestrate, or execute anything — see why DCP carries no trust for the reasoning behind that boundary. The protocol exists because agents and humans coordinating on a project need a shared, transport-independent vocabulary for describing what changed, the same way a media type describes a payload independent of the connection that carries it. That motivation is laid out in full in why a coordination vocabulary.
Who is behind it
Section titled “Who is behind it”DCP was initiated by the TokonoMix project and is currently hosted under the TokonoMix GitHub organization. This is stewardship, not coupling: DCP is vendor-neutral and has no dependency on TokonoMix, AgentixMesh, or any other product, and the specification will never require them. As adoption grows, stewardship may move to a neutral organization — for example, a dedicated dcp-spec organization. GitHub redirects keep old repository URLs working, so such a move would be non-breaking for anyone already depending on the spec, the schemas, or the repository links.
Day-to-day, the project is led by Mesut Kalkan (founding maintainer, InterIP Networks), who initiated DCP out of the TokonoMix project and safeguards the protocol’s single-responsibility boundary: reviewing and merging changes, cutting releases, and deciding scope questions. The specification, schemas, docs, and this website are authored and published by InterIP Networks. Full detail on roles, the RFC-style change process, and versioning authority is in governance.
Why it exists
Section titled “Why it exists”Coordinating AI agents and humans on a project currently means every integration reinvents its own notion of “task completed” or “decision recorded.” DCP’s single responsibility is to give that idea a closed, versioned, schema-validated shape — 8 entity types (Project, Task, Dependency, ArchitectureImpact, Decision, ReviewRequest, Finding, Milestone) and a closed 8-value rel vocabulary for relating them — while leaving trust, transport, and execution to other layers entirely. That narrow scope is deliberate: it is what makes the same DCP message consumable regardless of which agent framework, message broker, or product produced it.
Current status
Section titled “Current status”DCP is at v1.0.0-draft — a public draft published for review and feedback, not a finalized standard. Schemas and vocabularies may still change before the v1.0.0 freeze. As of 2026-07-01, the project comprises 8 entities, 14 JSON Schemas (2020-12), 70 passing tests, 25 conformance cases (7 accept / 18 reject), and 18 worked examples. The repository is dual-licensed: Apache-2.0 covers code, schemas, examples, and tests; CC-BY-4.0 covers the specification text and documentation.
Get involved
Section titled “Get involved”Start with the quickstart to validate your first DCP message, or read the FAQ for common questions about scope and adoption. Proposals that touch schemas or normative text follow the RFC-style process described in governance: open an issue, get maintainer review, and land schema changes with examples and conformance fixtures before merge.
Source repository
Section titled “Source repository”The DCP source repository is public: github.com/TokonoMix/development-coordination-protocol — specification, JSON Schemas, worked examples, conformance corpus, and the reference validator, dual-licensed (Apache-2.0 for code/schemas/examples/tests, CC-BY-4.0 for spec text and docs). The full specification is also mirrored on this site on every change, the schemas are served at their permanent canonical URLs on schemas.devcopro.org, and worked examples are published here. Issues and pull requests are welcome on GitHub; for everything else, the assistant below is the fastest route.
Contact the maintainers
Section titled “Contact the maintainers”All contact runs through the DCP Assistant on this site — there is no inbox to lose your message in. Pick a starting point and the assistant opens with your question ready:
By Mesut Kalkan · InterIP Networks · Last updated 2026-07-06.
