Durable work
A session can end. The work cannot disappear.
Claims, progress, questions, parks, and completion records survive the process that produced them.
5
domain worlds
252
passing tests
50/50
wire obligations
145
normative entries
OWP surfacelive · 1.0-rc2
PAY-18working
Retry logic
PAY-21needs you
Schema fork
PAY-24review
Migration notes
claim is atomicquestions do not blockhandoffs survive sessions
All five domain experiences use the same audited reference surface. They demonstrate portability across domains, not independent implementation interoperability; that remains unproven until an independently authored surface passes the kit.
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.
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 protocol01
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.
Evidence, not personas
Five worlds chosen to disagree with each other.
What survived all five belongs in the protocol. What differed is exactly what the protocol refuses to define.
Compare the worldscode
Coding fleet
Thirty coding sessions on one codebase, with atomic claims, collision handling, review, and human steering.
94 tests · operator console
publish
Editorial desk
A novel that stays true to itself while agents draft non-linearly and the author keeps the calls that belong to them.
56 tests · writing room
research
Research catalog
Long-running research where contradictions become decisions and rejected framings make the next quarter cheaper.
35 tests · briefing room
ops
Container estate
Watchers propose, windows release, agents stage and verify, and one irreversible step still reaches a person.
43 tests · terminal wall
desk
Freight back office
Two hundred inbound documents a day, transaction chains, money gates, and a dispatcher’s bounded read.
24 tests · load board
Conformance 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
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
50/50 obligations met