# Orchestration Context Protocol > OCP is an open JSON format for agent orchestration runs: what ran, what it cost, and whether it was accepted. ## Get started - [Orchestration Context Protocol](https://orchestrationcontextprotocol.io/index.md): An open JSON format for agent runs: what ran, what it cost, and whether the result was accepted. - [What is OCP?](https://orchestrationcontextprotocol.io/docs/getting-started/intro.md): An open file format for the record of an agent orchestration run. - [Quickstart](https://orchestrationcontextprotocol.io/docs/getting-started/quickstart.md): Write a first OCP document, validate it, and read a finding. - [FAQ](https://orchestrationcontextprotocol.io/docs/getting-started/faq.md): Short answers to the first questions people ask about OCP, each with a link to the rule behind it. ## Concepts - [How OCP fits](https://orchestrationcontextprotocol.io/docs/learn/architecture.md): Producers, documents, consumers and the checker, and the layers inside one document. - [Evidence](https://orchestrationcontextprotocol.io/docs/learn/evidence.md): Why edges, signals, inferred labels and outcomes carry an evidence tier, and how to choose one. - [Privacy](https://orchestrationcontextprotocol.io/docs/learn/privacy.md): How to write useful documents that hold no prompt, completion or transcript text. - [Versions in practice](https://orchestrationcontextprotocol.io/docs/learn/versioning.md): Which version to write, how readers handle older documents, and how to migrate. ## Implement OCP - [Write OCP from your tool](https://orchestrationcontextprotocol.io/docs/develop/producers.md): Where a producer hooks in, how to map your tool's records onto nodes and attempts, and the choices every producer makes. - [Read OCP](https://orchestrationcontextprotocol.io/docs/develop/consumers.md): What a consumer must accept, what it should weigh, and a small reader. - [Validate](https://orchestrationcontextprotocol.io/docs/develop/validate.md): Check documents with loopmath ocp validate, upgrade old ones with migrate, and validate in CI. - [Implementations](https://orchestrationcontextprotocol.io/docs/implementations.md): How the records of common agent tools map onto OCP 0.3, what each can fill, and where an exporter hooks in. ## Examples - [Examples](https://orchestrationcontextprotocol.io/examples.md): Complete OCP documents: one run per workflow shape, one with every v0.3 field, and a pass and a fail file for each numbered rule. ## Specification - [Specification](https://orchestrationcontextprotocol.io/specification/0.3.md): OCP 0.3: an open format that records one agent orchestration run per JSON document. - [Changelog](https://orchestrationcontextprotocol.io/specification/0.3/changelog.md): What changed in each version of OCP. - [Versioning](https://orchestrationcontextprotocol.io/specification/0.3/versioning.md): How OCP versions work, what stays stable, and how older documents are upgraded. ## The document - [Document](https://orchestrationcontextprotocol.io/specification/0.3/document.md): The top-level object, the producer block, identifiers, timestamps and vocabularies. - [Run graph](https://orchestrationcontextprotocol.io/specification/0.3/run-graph.md): The run, and the graph of work inside it: groups, nodes and edges. - [Attempts](https://orchestrationcontextprotocol.io/specification/0.3/attempts.md): Each try at a node: harness, model, effort, cause, status, outcome and evidence. - [Cost](https://orchestrationcontextprotocol.io/specification/0.3/cost.md): Token and dollar cost of one attempt, how it was attributed, and the price table behind it. - [Artifacts](https://orchestrationcontextprotocol.io/specification/0.3/artifacts.md): Files one attempt wrote and other attempts read: the hand-offs between agents. - [Events](https://orchestrationcontextprotocol.io/specification/0.3/events.md): The optional, append-only log of what happened when. ## The observation - [Task](https://orchestrationcontextprotocol.io/specification/0.3/task.md): The task a run attempted: its type, its place in a chain of groups, its features and where it came from. - [Configuration](https://orchestrationcontextprotocol.io/specification/0.3/configuration.md): What ran: a workflow of pieces and artifacts, a setting per piece, and an id derived from both. - [Signals and acceptance](https://orchestrationcontextprotocol.io/specification/0.3/signals.md): Timestamped verdicts, scores and late events about a run's result, and the rule that turns them into success. - [Slates and preferences](https://orchestrationcontextprotocol.io/specification/0.3/slates.md): Runs started together on one task to be compared, and the judgements between them. - [Provenance, rescue and receipt](https://orchestrationcontextprotocol.io/specification/0.3/receipt.md): Who chose the configuration, the fallback used when a run failed, and a recommender's prediction set against what happened. ## Conformance - [Conformance](https://orchestrationcontextprotocol.io/specification/0.3/conformance.md): What makes a document conforming, every numbered rule, and what the reference checker does not test. - [Privacy](https://orchestrationcontextprotocol.io/specification/0.3/privacy.md): The two privacy profiles, what a metadata_only document may hold, and how the promise is kept. - [Extensions](https://orchestrationcontextprotocol.io/specification/0.3/extensions.md): The ext object, namespaces, and how a consumer treats data it does not know. ## Reference - [Schema reference](https://orchestrationcontextprotocol.io/specification/0.3/schema.md): Every object and field of OCP v0.3, generated from the JSON Schema. ## Get involved - [Contributing](https://orchestrationcontextprotocol.io/community/contributing.md): Ways to help: report a problem, map a tool, add an example, or propose a change. - [Proposals](https://orchestrationcontextprotocol.io/community/proposals.md): How a change to OCP is proposed, discussed and released. ## Governance - [Governance](https://orchestrationcontextprotocol.io/community/governance.md): Who maintains OCP, how decisions are made, and what the versioning promise covers.