# Implementing OpenWOP

> Source: https://openwop.dev/implement/ · OpenWOP, the open-source protocol for multi-agent workflow orchestration.

Four entry points cover every shape of OpenWOP work. Pick the role that matches what you're building — each card links to the role-specific landing with the specs, schemas, and conformance scenarios that role actually touches.

## Roles

### [Workflow authors →](https://openwop.dev/for/workflow-authors/)

You're wiring durable multi-agent runs into a product and calling a compliant host over REST + SSE. Start here if you've already picked (or had picked for you) which host you're talking to and you need to know the exact request shape, event order, and replay contract.

### [Host implementers →](https://openwop.dev/for/host-implementers/)

You're implementing the OpenWOP wire surface against your own runtime (or one your customers picked). Start here for the capability advertisement contract at `GET /.well-known/openwop`, the reference hosts in [`openwop/openwop-examples`](https://github.com/openwop/openwop-examples), and the conformance suite that gates your host's leaderboard row.

### [Pack authors →](https://openwop.dev/for/pack-authors/)

You're publishing reusable workflow components — node packs, workflow-chain packs, or agent definitions — to a registry that hosts can consume. Start here for the pack manifest format, signing requirements, and the registry submission process.

### [Production evaluators →](https://openwop.dev/for/production-evaluators/)

You're evaluating OpenWOP as a substrate for a production workflow. Start here for the production-profile claim, scale tiers, BYOK secret handling, the observability taxonomy, and the conformance evidence that backs each claim.

## Common surface

Regardless of role, every implementer touches:

- **The wire contract** — [`/spec/v2/`](https://openwop.dev/spec/v2/) prose specs + [REST](https://openwop.dev/api/rest/) reference + [`schemas/`](https://github.com/openwop/openwop/tree/main/schemas) JSON Schema corpus.
- **Conformance** — [`@openwop/openwop-conformance`](https://github.com/openwop/openwop/tree/main/conformance) plus the live [leaderboard](https://openwop.dev/conformance/).
- **RFCs** — the [in-flight](https://openwop.dev/rfcs/) protocol evolution channel; each major stays additive-only per [`COMPATIBILITY.md`](https://github.com/openwop/openwop/blob/main/COMPATIBILITY.md).
- **SDKs** — TypeScript on npm, Python on PyPI, Go module — all in [`openwop/openwop-sdks`](https://github.com/openwop/openwop-sdks).

## Not sure which one you are?

If you're calling somebody else's host → **workflow author**.
If you're answering somebody else's call → **host implementer**.
If you're shipping reusable nodes for either of the above to consume → **pack author**.
If you're choosing which of the above to commit to → **production evaluator**.