Global Business Rules
These rules define the intended cross-product constraints. The owning API and compliance systems must enforce rules that protect eligibility, money, custody, or legal state. The frontend may guide, validate, or hide an action but is not the authorization boundary.
Fund Rules
| ID | Rule |
|---|---|
| BR-FUND-SETUP-01 | A fund identifier and public slug must be unique in the owning fund service. |
| BR-FUND-SETUP-02 | A fund cannot be made investable until required terms, materials, eligibility configuration, and approval/readiness requirements are satisfied. |
| BR-FUND-SETUP-03 | Financial terms and availability must be controlled by the fund owner after publication; the exact post-publication edit policy belongs to that owner. |
| BR-FUND-SETUP-04 | A client must not present a fund as investable when the service or release configuration reports it unavailable. |
| BR-FUND-SETUP-05 | Capacity, share arithmetic, pricing, and close decisions must use canonical decimal values in the owning service. JSON floating-point conversion is not an authoritative financial calculation. |
Profile and Eligibility Rules
| ID | Rule |
|---|---|
| BR-PROFILE-01 | A dashboard action for a profile requires an authenticated user and an owned profile identifier. |
| BR-PROFILE-02 | Profile type determines required information and associated-party collection. The server remains authoritative for completeness. |
| BR-PROFILE-03 | KYC, accreditation, suitability, and regulation-specific checks must be evaluated for the profile and fund before an investment is accepted. |
| BR-PROFILE-04 | An approved or pending accreditation profile is not sent to a duplicate accreditation-upload route by the Dashboard guard. |
| BR-PROFILE-05 | Eligibility status shown in the client is informational until confirmed by the owning compliance service. |
Investment and Funding Rules
| ID | Rule |
|---|---|
| BR-INVEST-01 | A user may begin an investment only for an available fund and an owned selected profile. |
| BR-INVEST-02 | Amount, ownership, funding selection, required signatures, and review are separate user-visible steps. The service determines whether a step may advance. |
| BR-INVEST-03 | An investment submission must be attributable to the profile, fund, actor, and submitted terms accepted by the service. |
| BR-INVEST-04 | Bank, wallet-balance, and USDC paths have distinct settlement and provider behavior. A requested transfer is not evidence of settled funds. |
| BR-INVEST-05 | Cancellation eligibility is state- and service-dependent. A requested cancellation, an approved cancellation, a reversal, and a refund are distinct outcomes. |
| BR-INVEST-06 | Retrying a client request requires an idempotency or recovery guarantee from its owner; the UI must not claim that an arbitrary retry is safe. |
Wallet, Custody, and Servicing Rules
| ID | Rule |
|---|---|
| BR-CUSTODY-01 | Wallet and transaction data displayed to an investor must be scoped to the selected owned profile. |
| BR-CUSTODY-02 | Wallet verification, upgrades, and signing handoffs require the applicable identity or wallet-provider confirmation. |
| BR-CUSTODY-03 | Vault deposit fulfillment, share issuance, redemption fulfillment, and investor claims are separate custody actions. |
| BR-CUSTODY-04 | Distribution records and notifications describe information returned by their services; calculation, payment, and delivery are not performed by the Dashboard. |
| BR-CUSTODY-05 | Documents are accessed using service-provided authorization and URLs. The UI must not treat a visible document row as proof of download authorization. |
Fund Manager Rules
| ID | Rule |
|---|---|
| BR-FUND-01 | Fund publication requires the readiness conditions reported by the fund-management system. |
| BR-FUND-02 | Fund page access does not make a manager the fund-wallet owner. Fund-owned signing requires the separate wallet-owner verification flow. |
| BR-FUND-03 | Subscription acceptance, fulfillment pricing, vault fulfillment, redemption approval, and redemption fulfillment require the relevant fund permission and are individually auditable operations. |
| BR-FUND-04 | An auditor is read-only. An investor can perform only investor-owned request or claim actions. |
Control Rules
| ID | Rule |
|---|---|
| BR-CONTROL-01 | State-changing operations must have a durable actor, timestamp, target, outcome, and failure-reason record in their owning system. |
| BR-CONTROL-02 | Client route guards and control visibility improve the experience but do not replace backend authentication or authorization. |
| BR-CONTROL-03 | Regulatory, privacy, retention, incident, and reconciliation requirements must be approved and maintained by their accountable owners. |
See the Reference section for the verification boundary and Actors, roles, and permissions for the actor model.