A party is anyone or anything a matter involves: a client, a counterparty, a company, a regulator. The registry holds one governed record per party and keeps it current, so the people and companies on a matter are not scattered across documents and spreadsheets but live in one place that the matter, the agent, and the firm all read from. On top of the basic record it carries the relationships between parties, the know-your-client standing that compliance depends on, and the lifecycle moves (suspend, reactivate, archive, merge) that keep the roster honest over time.
What it does
A single governed record per person or company. Add a person or a company, look them up, and edit the core fields (display name, email, identity-grade details) as they change. Each party is one record that every matter, document, and agent reads from, rather than a name re-typed in a dozen places. An identity-grade change to a party fires a fire-and-forget deduplication pass, so the registry works to keep one record per real-world party rather than quietly accumulating duplicates.
Relationships between parties, including the company registers. Parties relate to one another, and those relationships are first-class rows: directors, shareholders, ultimate beneficial owners, and secretaries, each with a role, a share percentage, a status, appointed and resigned dates, and a nominee flag. Listing the relationships on a company is the company-registers read - the live picture of who holds what office and what stake, filterable by role, status, or party.
Know-your-client review and standing. Run a KYC review on a party and the registry records the outcome as standing: the KYC status, risk level, PEP flag, sanctions match, and nationality. A review is a re-verify of the standing fields rather than a fresh write, and on a verified transition it derives an expiry date from the verified date plus the tenant’s configured validity period, so a verified party never lands without an expiry. The sensitive identity material that backs the review is held as encrypted, typed facets and is deliberately preserved untouched when the standing is updated.
A firm-wide KYC-expiry register. Because every verified party carries a derived expiry, the party list doubles as a compliance register: filter it to surface which parties have expired KYC, which are expiring soon, and the earliest expiry across the roster. Expiry standing is always derived from the underlying facts, never a stored status that can drift, so the register you read is the register as it actually stands today.
Richer profiles and typed facets. Beyond the core record, a party can carry typed facets - KYC, corporate, equity, and portal-principal - that enrich it for the work it is part of. The profile read returns the full picture: the core record, the relationship graph, and the KYC standing in one bundle. The most sensitive facets hold regulated personal information, the most sensitive data in the product: they are encrypted before they are written, every read of them is audited, and the list view returns standing only, never the unredacted facet.
Lifecycle and clean-up, on the admin side. Suspend a party that should not be active, reactivate one that should (the suspend and reactivate moves are status changes with a reason on the record, never an inferred timestamp), and archive a record that is done with. When two records turn out to be the same party, merge them. These are sensitive, admin-tier moves: archive is terminal, so reactivate refuses a record that has already been archived.
How you use it
Add and find a party. Create a person or company with their core details, then look them up by id or pull a filtered list by type, status, or feed. Update the core fields whenever they change; an identity-grade edit re-runs deduplication in the background so the registry tends back toward one record per real party.
Read the full picture of a party. Open a party’s profile to see the core record, the relationship graph, and the KYC standing together. Reading the sensitive facets is audited every time, so there is always a record of who looked at regulated personal data and when.
See who relates to whom. List a company’s relationships to read its registers - directors, shareholders, UBOs, and secretaries with their roles, share percentages, statuses, and appointment and resignation dates - filtered by role, status, or party.
Run and track KYC. Run a KYC review to set or refresh a party’s standing (status, risk level, PEP and sanctions flags, nationality); a verified outcome gets an expiry derived for you. Then filter the party list as a firm-wide expiry register to see what has lapsed, what is about to, and where the next deadline falls.
Keep the roster clean. As an admin, suspend or reactivate a party with a reason, archive a record that is finished, and merge duplicates into one. Each of these is a governed, audited move, so the lifecycle of every party is on the record.
The kernel verbs behind it
Every action on a party is a named verb through the kernel’s one front door: permission-checked, scope-checked, and audited before it runs. The sensitive identity facets are encrypted before they are written and read-audited, so regulated personal data is governed the same way whether a person or an agent touches it (see Security and permissions).
The record:
party.create- add a new person or company as a governed record.party.get- read one party record.party.list- list and filter parties; filtering on KYC standing gives the firm-wide expiry register.party.update- edit a party’s core fields, with a dedup re-run on identity-grade changes.party.profile- read the full profile: core record, relationship graph, and KYC standing.
Relationships and KYC:
party.relationship.list- read a party’s relationships (the directors, shareholders, UBOs, and secretaries of the company registers).party.kyc.review- re-verify the KYC standing fields and derive the expiry on a verified transition, preserving the encrypted PII facets.party.facet.set- write a typed facet (KYC, corporate, equity, or portal-principal); regulated facets are encrypted before write.
Lifecycle and clean-up (admin):
party.suspend- suspend a party, with a reason on the record.party.reactivate- flip a suspended party back to active (refused on an archived record).party.archive- archive a record that is done with.party.merge- merge two records that turn out to be the same party.
See the full set in the party verb reference.