A clearing hall where parallel chutes carry printed records to one shared counter.

Concordia · Governed transactions

Negotiate and commit with a counterparty under rules both sides can check.

Concordia is shared ground. Plural Worlds acts for neither side, and each organization keeps its own systems, data, and decision rights.

Isolated sessions
Dual signature
Portable record

How it runs Bring us a transaction

Where teams would use it first.

Workflows where an agent could create a real obligation, and where a missing approval, leaked bid, or incomplete record would matter.

The Meridian mandate surface in the Plural Worlds console: a root authority with its holder, scope, ceiling, expiry, and revocation controls.

Delegate a first commercial task to an agent

Define which suppliers the agent may contact, which terms it may change, its spending limit, and which decisions still need a person. Every action is checked against that mandate.

Authority

A sealed competitive event in the Plural Worlds console: frozen rules ledger, root hash, award rule, and isolated supplier sessions.

Run a multi-supplier sourcing event

Invite several suppliers under the same rules while each session stays separate. Suppliers see only their own activity, and the buyer discloses only what the rules permit.

Sealed bids

An evidence replay in the Plural Worlds console: hash and signature checks reported independently, replayed on a machine with no access to the control plane.

Prepare evidence for audit or dispute

Export the authority proofs, signed events, rules, approvals, and final commitment. A reviewer can reconstruct what happened without screenshots or recollection.

Evidence

A revoked mandate in the Plural Worlds console: the delegated buying agent withdrawn, with the revocation record and live status endpoint reading revoked.

Test revocation before production

Revoke an agent's mandate and confirm its next offer, approval, or commitment is refused at once. The control is tested inside the live workflow.

Fail closed

A year later, the record should still be clear to procurement, legal, and audit.

How a transaction runs

Four stages, and only the last one binds.

Nothing binds either organization until both sign the same commitment object.

Admit the parties

A named organization enters a defined engagement. Its agent must show authority its own organization issued before it can act.

Set the rules

Financial limits, permitted disclosures, deadlines, and required approvals are fixed before consequential work begins.

Coordinate signed actions

Offers, revisions, approvals, and awards are recorded in order. Separate sessions keep one counterparty from learning about another.

Commit and export

The result binds only when both organizations sign the same commitment. Either side can then export the record.

What is included

Sessions and events

Each counterparty negotiates in its own signed session. No participant learns about another from content, sequence numbers, timing, or errors.

nothing shared between sessions

Sealed-bid events

Bids are submitted under verified authority, the rules freeze when bidding opens, and one award is made per unit. A losing bidder can verify that its session stayed isolated.

sealed until closeone award per unit

Onboarding and custody

A counterparty with no agent of its own can join one named transaction. We can hold its signing key, and every act needs a human approval bound to that action. The invited side never pays.

key custodiedauthority never

Evidence export and retention

Every completed transaction produces a signed record either organization can export and verify without our systems. Longer retention is available where statute requires it.

verifies without our systems

Recourse

A determination can be contested through a defined route. Raising a dispute is free, and no fee depends on an outcome.

appeal freeno outcome fees

Hosted or dedicated delivery

Concordia runs hosted, or inside an agreed infrastructure or regional boundary where security or regulation demands it. Both produce the same record.

hosted or dedicatedsame signed objects

Three controls inside cross-company commerce.

How a counterparty enters, what it can see while the work is active, and what both organizations must sign before the result binds. All solutions

Admit one counterparty to one governed engagement

An invitation gives access to one named engagement and nothing else. The agent must show authority from its own organization before it can offer or commit.

Principal

Issuing authority

Mandate

Reading scope

Agent key

Matching key

Signed action

Awaiting check

Every link verified

Authority verifiedAccess limited

Run a sealed sourcing event without cross-bid leakage

Each supplier submits signed offers in a separate session. The rules are fixed before bidding opens, and no supplier can see another's participation, timing, or price.

Bidder APreparing

Bidder BPreparing

Bidder CPreparing

Sealed eventRules frozen

Offers received: 0
Rivals visible: none

Exactly one award

Event rules fixedSessions isolated

Create a commitment both organizations can verify

Buyer and supplier sign the same commitment object. The record keeps the authority, offers, approvals, and terms behind it, so either side can verify the result later.

Buyer key

Preparing

Supplier key

Preparing

One canonical hash

sha-256 · rfc 8785 · 2 signatures

Audit bundleAssembling

Objects

Replay

consistent

Access

none needed

Both signed the same bytes

Both sides signRecord exportable

After the work ends, the signed record remains available for review.

A JSON-like record impressed into pale mineral dust, ending at an orange marker.

Reconstruct the full history from signed events.

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.