Five standalone experiences

One protocol. Five different instruments.

Clone one repository and the whole experience is there: the same pinned reference runtime, a distinct domain interface, agent guidance, deployment notes, and executable evidence.

01npm ci
02npm test
03npm run demo

owp-code

01

Coding fleet

Thirty coding sessions on one codebase, with atomic claims, collision handling, review, and human steering.

The operator sees the fleet, the work that needs a decision, and the exact evidence behind it—without opening thirty terminals.

  • Atomic claims under concurrency
  • Agent collision and recovery
  • Scoped review delegation
94 testsoperator consolestandalone
Open the repository
Real example · Fleet and decisions
OWP coding fleet overview showing active sessions and decisions requiring operator attention
Real example · Review queue
OWP coding fleet review queue showing scoped work ready for review

owp-publish

02

Editorial desk

A novel that stays true to itself while agents draft non-linearly and the author keeps the calls that belong to them.

The book stays central. Contents, page, and margin join manuscript recall to continuity decisions while the author keeps reading.

  • Continuity as a human decision
  • Non-linear drafting
  • Knowledge edited in place
56 testswriting roomstandalone
Open the repository
Real example · Seeded demo
OWP writing room showing a manuscript page, chapter contents, and editorial margin

owp-research

03

Research catalog

Long-running research where contradictions become decisions and rejected framings make the next quarter cheaper.

The dossier opens on what is contested, then shows coverage, active reading, and the catalog evidence that makes a ruling possible.

  • Contradictions as the product
  • Coverage as assignment rank
  • Rulings that compound
35 testsbriefing roomstandalone
Open the repository
Real example · Brief and contents
OWP research briefing room opening brief and portfolio contents
Real example · Contested evidence
OWP research dossier showing contested evidence and a study requiring a ruling
Real example · Active studies
OWP research dossier showing active studies, evidence coverage, and queued work

owp-ops

04

Container estate

Watchers propose, windows release, agents stage and verify, and one irreversible step still reaches a person.

The estate reads like an instrument panel: quiet when verified, loud when blocked, and explicit about the one gate a machine cannot cross.

  • Watchers own clocks and cursors
  • Staged upgrade with rollback
  • Trigger-scoped authority
43 teststerminal wallstandalone
Open the repository
Real example · Seeded demo
OWP estate terminal wall showing upgrade chains, gates, and infrastructure state

owp-desk

05

Freight back office

Two hundred inbound documents a day, transaction chains, money gates, and a dispatcher’s bounded read.

A dense dispatch grid keeps every load in one line; the slip underneath carries history, authority, and the next operator gesture.

  • Volume with bounded reads
  • Transaction chains, not state mutation
  • Money and liability gates
24 testsload boardstandalone
Open the repository
Real example · Seeded demo
OWP freight load board showing a dense grid of tenders, quotes, and dispatch work

The convergence test

Difference is evidence too.

The five interfaces share no shell. Their vocabularies, knowledge planes, clocks, and operator gestures remain local. A candidate belongs in the protocol only when unrelated worlds need the same semantic—or when an invariant already carried by the protocol demands it.