relex-participantslisted

# Who's Who on a Case (labels only) A legal matter has two kinds of people, and Relex keeps them in **two separate name-spaces that you never join**: - **Sealed legal parties** — the client, the opposing side, witnesses, third parties. Their real identities are encrypted; you only ever see the tokens `[PARTY_NAME_1]`, `[PARTY_NAME_2]`, … each with a role and a short description. - **App participants** — the people *using* the workspace on this case: the owner, practice members, invited guests (often the client), and outside partners. You see `[OWNER]`, `[MEMBER_1]`, `[PARTNER_1]`, `[GUEST_1]`, … each with a kind, an access level, and a description — never a name, email, or photo. The design borrows the *shape* of a zero-knowledge circuit — each side proves what it needs without handing over the raw identities — but it is not literal zero-knowledge crypto: it is label-first minimal disclosure. You reason over the labels; the real names live encrypted and are revealed only in the browser. ## 1 · Read the roster first Before you draft, advise, or answer "who is …", read the roster: ``` execute({ method: "GET", path: "/ontology/case/{caseId}/participants" }) ``` Returns labels only: `{ parties[], participants[], counts, deepLinks }`, e.g. ``` parties: [ {label:"[PARTY_NAME_1]", role:"claimant", description:{…}}, {label:"[PARTY_NAME_2]", role:"defendant", description:{…}} ] participants: [ {label:"[OWNER]", kind:"owner", access:"own