3. Parties
- Repository
- bloque-app/aledgent
- Commit
5ca6b8a- Version
- 0.4.27
- Status
- draft
- Rendered
- 2026-10-17T19:30:18Z
Five kinds of party interact with aledgent. Everything else, such as a product, a workflow, a bank or a card network, sits on the far side of one of them.
| Party | Who | Holds an identity in the book? | Authority | Interacts through |
|---|---|---|---|---|
| Identity holder | A person, an organisation or an agent | Yes | Owner authority over its own accounts. Delegated authority over others’ accounts where granted. An agent holds delegated authority only | Command, query and event surfaces (§7.A–C). Disclosure surface as subject (§7.E) |
| Operator | The party running the deployment | Only when it holds value of its own, and then as an ordinary organisation identity | Operator authority over delegated-custody accounts, bounded by kind (§5.9). The identities principal’s role, unless another principal plays it: it alone opens identities, and it may open accounts (REQ-ID-6). The deployment’s own configuration, which is its alone (REQ-ID-7). The operator surface (§7.D) |
Operator surface. The settlement adapter it runs |
| Verifier | An auditor, a regulator or a counterparty to a disclosure | No | None | Disclosure surface as recipient (§7.E). The settlement layer’s public record |
| Settlement counterparty | A party on the settlement layer that sends value to aledgent or receives value from it | No | None | The settlement layer only. Never a surface of aledgent |
| Recovery authority | A party, distinct from the operator, that verifies a holder out of band and co-signs recovery of an owned-custody account | Only for value of its own | Recovery authority (REQ-AU-15). Never owner, delegated or operator authority |
The operator surface’s recovery commands (§7.D) |
The operator and an identity holder differ in authority and accountability, not in authentication. Both authenticate with credentials. Two things set the operator apart. (a) It may hold operator authority, a custodial power over accounts whose holders chose delegated custody, and act through the operator surface. (b) It is the party whose conduct the provability model of §4.6 exists to make checkable by everyone else. When the operator holds value of its own, it does so as an identity like any other. The same invariants apply.
A customer is an identity holder in its commercial relationship with the operator. This document does not distinguish customers by what they build or whom they serve. A business integrating aledgent to run a product, an organisation managing its treasury, a person and an agent are all identity holders. They differ only in the authority they hold and in whose behalf they act.
REQ-PN-1 Every operation MUST record the principal that initiated it and, where the caller acted for
another, the principal on whose behalf it acted. An operation whose initiating principal cannot be
determined MUST NOT be accepted.
© 2026 Pagos Cube LLC · Code: Apache-2.0 OR MIT · agents/: AGPL-3.0-or-later · Docs: CC-BY-4.0