Agent & Instrument Diagram: Sui RWA Flow
This translates the physical world (investor identity and fiat money) into cryptoeconomic bounds (Sui capability enforcement).
| Element | Description | Flow Purpose |
|---|---|---|
| Agent: KYC Provider | SumSub checking passport & wholesale forms. | Yields a boolean is_verified. |
| Agent: Issuer Admin | Syndicator managing the portal. | Approves/rejects edge-case investors. |
| Instrument: Platform BFF | Node/Next API layer. | Translates Webhook from KYC provider into a command. |
| Instrument: Sui Objects | Issued investor capability tokens. | Enforces compliance at the compiler level. |
| Feedback Loop: Transfer | EVM requires runtime checks. | Sui inherently blocks transfers from wallets lacking the WholesaleInvestorCap object. |
The Control Loop Setup:
- User provides docs → KYC Agent approves → Webhook fires.
- Platform Instrument catches Webhook → Calls Sui RPC.
- Sui mints
WholesaleInvestorCap→ Sent to User's zkLogin address. - User initiates buy execution. Sui Network (Instrument) structurally enforces that only owners of the Capability can hold the
RealEstateShareCoin.
Questions
Which agent in the sui real estate tokenization diagram has the highest authority-to-accountability ratio — and is that appropriate?
- Where does human judgment remain essential in this agent-instrument flow, and where is automation safe?
- If one instrument in this diagram reported bad data, which agents would be most affected and how quickly?
- What would need to be true for a new agent type to be added to this diagram without breaking existing flows?