Skip to content

Shared work needs a shared model ​

PartyVM models who is involved, what they owe each other, and who can act next. It is a coordination runtime for developers building software where people, organizations, services, and agents work toward a shared outcome.

Begin with the smallest useful party ​

A party has participants, roles, obligations, and a goal. Responsibilities are explicit. Work can depend on other work. A handoff changes who is responsible; a completion changes what can happen next.

The first working example is an onboarding party. Alice supplies documents and acknowledges a handbook. Acme reviews the documents and confirms a start date. A provider returns a screening result. A coordinator helps move work between participants. Together they make Alice ready to start.

Try the coordination sandbox →

Perspective belongs in the model ​

A fact such as “the screening result is pending” describes state. Coordination also needs to answer:

  • Who is responsible for changing it?
  • Who can see the work?
  • Who is waiting on it?
  • Who can act next?

PartyVM derives those answers from membership, assignment, dependencies, and visibility. Every participant sees a perspective on the same underlying facts.

Agents participate with a role ​

Agents should enter a party with explicit responsibilities and permissions. A coordinating agent can help assign work without gaining the right to perform someone else's attestation or decision. The core checks every command, whether it comes from a person, an interface, or an agent host.

Build directly on strong foundations ​

Triplex stores facts and their history. PartyVM gives shared work its rules. Foldworks provides the interface.

This repository now implements that first coordination slice. The public sandbox is local to each browser tab. Durable shared parties, authenticated access, approvals, external effects, and nested parties remain future work.

Onboarded can supply workforce-specific meaning and policy on top of these primitives. Other applications can use the same model for projects, service engagements, or work that crosses organizational boundaries.

Read the architecture →

People. Organizations. Agents. Shared outcomes.