OWP 1.0-rc1 is ready to implement

Agents work at machine speed. Operators steer at human speed.

The Open Work Protocol is the contract at that seam: durable work, explicit decisions, honest handoffs, and a queue made for the human who checks in later.

5

unrelated worlds

245

passing tests

47/47

wire obligations

0

surface forks

OWP surfacelive · 1.0-rc1
PAY-18working

Retry logic

PAY-21needs you

Schema fork

PAY-24review

Migration notes

claim is atomicquestions do not blockhandoffs survive sessions

The missing layer

Work that outlives the prompt needs more than another prompt.

Trackers make agents perform human ritual. Orchestrators assume you are watching the machine. OWP models the long-lived work between them.

Durable work

A session can end. The work cannot disappear.

Claims, progress, questions, parks, and completion records survive the process that produced them.

Human authority

The decisions that belong to people reach people.

Options carry evidence and tradeoffs. Asking never stops answer-independent work.

Portable contract

One lifecycle. Every deployment keeps its own vocabulary.

The protocol owns envelopes and invariants; your domain owns its nouns, interface, and delivery.

The line

Small enough to implement. Strong enough to trust.

OWP is deliberately not a scheduler, workflow language, knowledge base, model API, or reference interface. It freezes only the seam every implementation must agree on.

Explore the protocol
01

The surface computes and reports; only clients mutate work state.

02

Only clients author content. The surface never invents prose.

03

No actor may decide its own output.

04

No calendar in the protocol. Sequence is structural; clocks belong to clients.

Interoperability you can run

A specification with a receipt.

Point the conformance kit at any surface. It exercises the contract over HTTP, touches no internals, and cites the sentence behind every failure.

  • Runs over the wire
  • Covers authenticated authority
  • Machine-readable output
  • MIT licensed
See what it proves
conformance/run.ts
§11 assignment
  ✔ next chooses and claims atomically
  ✔ the hard filter holds

§18 authority
  ✔ no actor decides its own output

§1 / §19 no calendar
  ✔ calendar fields never become semantics

47/47 obligations met