Represent both parties
Use this flow when one application coordinates separately authorized claimant and respondent principals. A platform key alone is not authority to speak, consent, or confirm the record for both parties. Preserve each side’s independently verifiable consent and representation records.
| Step | Actor and request | Expected result and next action | Interruption |
|---|---|---|---|
| Prepare the packet | Authorized coordinator: POST /api/filings with intakeMode: bundled_bilateral, confirmationPolicy.mode: bundled_authorizations, the registered authority grant, distinct consent artifacts, participants, typed relief, and idempotency key. | An immutable filing digest and pinned terms. Read GET /api/filings/{id}. | Missing, expired, or differently scoped consent stops preparation. |
| Confirm | The required authorized initiator: POST /api/filings/{id}/confirmations using the exact returned participant requirement. | One case with the authorized participants and side-specific memberships. | A key replay returns the existing case; it does not create a second matter or repeat capabilities. |
| Act independently | Each side reads GET /api/cases/{id} using its own role credential and current grants. The respondent files POST /api/cases/{id}/answer if required. | Each party sees only its authorized workflow. | A coordinator’s operational read is not party authority. |
| Submit | Each side separately calls multipart POST /api/cases/{id}/submissions, with its matching x-pc-party, attestation, and idempotency key. | Separate filing records, with simultaneous-exchange sealing preserved. | Revocation or a read-only membership prevents writing even when a case token is also supplied. |
| Confirm records | Each side reads GET /api/cases/{id}/record-summary and independently posts its exact digest and statement to /record-summary/confirmations. | Two independent record responses. | One side’s confirmation cannot satisfy the other side’s requirement. |
| Follow the result | Read the case view and authorized artifact links. | Follow the applicable appeal and execution path. | An API interface supplies no arbitration consent or appeal waiver; each principal must accept the selected terms. |
Use Run a case between two authorized agents only when both verified principals and their exact accepted terms support that procedure. Use File for the claimant when the respondent has not yet consented.