Know who is involved.
Bring humans, organizations, services, and agents into the same context. Give every participant an explicit role.
Appearance
Skip to contentA shared world.
Party · Participant · Role Obligation · Assignment · Handoff Dependency · Completion · Shared goal A role. A scope.
Facts become responsibilities.
Read the architecture
Built on Triplex + Foldworks · Early runtime
A shared world.
A way forward, together.
People, organizations, and agents have work to do together. PartyVM models who is involved, what they owe each other, and who can act next.
A working coordination core. Try participant views, handoffs, and shared goals.
Facts. Coordination. An interface.
- 01 / MemoryTriplex
Facts, time, and provenance
- 02 / CoordinationPartyVM
Participants, work, and goals
- 03 / InterfaceFoldworks
Make shared work tangible
- 04 / WorkforceApplications
Start with onboarding
01 / Perspective
One fact. Different responsibilities.
A background check is pending. The useful questions are who is waiting, who owns the next step, and what each participant is allowed to do.
Alice · Acme onboarding Working sandbox
- Alice
- Submit documents and acknowledge the handbook.
- Acme
- Review documents, then confirm the start date.
- Provider
- Return the screening result or hand it off.
Switch perspectives and act on a real, in-memory Triplex store. Every completion and handoff leaves a transaction.
Open the coordination sandbox ↗02 / Coordination
Give shared work a boundary.
A party brings participants, assigned work, and a shared goal into one boundary. Its state and changes are stored directly as Triplex facts.
Make responsibility explicit.
Describe what participants owe each other, who owns the work, and when responsibility moves to someone else.
Move toward a shared outcome.
Connect prerequisites and remaining obligations to the outcome everyone is coordinating around. Readiness follows from completed work.
03 / Agents as participants
A role. A scope.
A reason for every action.
An agent joins a party with specific capabilities. Its context comes from the facts it may see, the goals it is helping with, and the obligations still open.
Committed actions record the actor, role, policy version, and changed facts in Triplex. The core checks permissions before any write.
Explore the agent boundary Participant context Example role
- Party
- onboarding/alice-acme
- Role
- coordinator
- Goal
- Alice is ready to start
Permitted by this example role
- See all party obligations
- Add a participant
- Hand off work within its required role
Outside this role
Complete another participant’s work
Bypass an obligation’s prerequisites
The direction
Facts become responsibilities.
Responsibilities become progress.
Explore the core, try the sandbox, and build the next coordination loop.