The enterprise module provides chain-side primitives for organizations that need more structure than a single account: enterprise records, members, roles, treasuries, payment requests, approval, rejection, execution, and policy metadata.
Product boundary
The module can express an on-chain control workflow, but it does not replace an institution’s off-chain identity, KYC, accounting, sanctions, or approval process. A front end should show which steps are on-chain and which evidence is external.
Safe composition
- Use a treasury policy to restrict denom, amount, recipient, or approver scope.
- Keep encrypted metadata and public metadata hashes separate from payment value.
- Bind an execution to the approved request ID and current status.
- Record operator identity and reason notes in the institutional application layer where needed.
- Reconcile the final payment with chain state and the institution’s own ledger.
The institutional settlement workflow describes how Enterprise, Stables, Bank, and Router can fit together without turning a demo console into an attestation system.