Operated service
Plural Worlds governs commercial work that crosses company boundaries while each organization keeps its own systems, policies, private data, and decision rights.
01
A named organization enters a defined engagement. Its agent must present authority issued by that organization before it can submit an offer, disclose protected information, approve a change, or sign.
02
Financial limits, permitted disclosures, deadlines, human approvals, and event-specific rules are fixed before consequential work begins. Every proposed action is evaluated against them.
03
Offers, revisions, approvals, awards, revocations, and commitments are recorded in order. Separate counterparty sessions prevent one participant from learning about another.
04
The result becomes binding only when both organizations sign the same commitment and every required approval is present. The completed record can then be exported and verified later.
How the service works / 03
Plural Worlds controls how a counterparty enters, what it can see while the work is active, and what both organizations must sign before the result becomes binding. All services
An invitation gives a counterparty access to a named engagement and nothing else. Its agent must present authority issued by its own organization before it can submit an offer or create an obligation.
Issuing authority
Reading scope
Matching key
Awaiting check
Each supplier submits signed offers inside a separate session. The buyer fixes the event rules before bidding opens, and no supplier can observe another supplier's participation, timing, price, or errors.
The buyer and supplier sign the same final commitment object. The record preserves the authority, offers, approvals, and terms that led to it so either side can verify the result later.
Preparing
Preparing
One canonical hash
sha-256 · rfc 8785 · 2 signatures
Objects
41
Replay
consistent
Access
none needed
AFTER / 02
After the work ends, the signed record remains available for review.
Evidence
A business team, procurement team, legal reviewer, auditor, or counterparty can trace the authority, offers, approvals, applicable rules, and final commitment from the same shared record.
Signed events. Reconstructable history.
Use cases
The first use cases are commercial workflows where an agent could create a real obligation and where a missing approval, leaked bid, or incomplete record would matter.
Define which suppliers the agent may contact, which terms it may change, the financial limit it must stay within, and which decisions still require a person. Every action is checked against that mandate.
Invite several suppliers under the same event rules while keeping each session separate. Suppliers see their own activity, and the buyer discloses only the outcome the rules permit.
Export the authority proofs, signed events, applicable rules, approvals, and final commitment. A reviewer can reconstruct what happened without relying on screenshots or employee recollection.
Revoke an agent's mandate and verify that its next offer, approval, or commitment is rejected immediately. The control is tested inside the live workflow, not assumed from a later access review.
LATER / 03
A year later, the record should still be clear to procurement, legal, and audit.