18Platform
Protocol Interfaces and Integrations
Narrow, reviewable module families and an illustrative data model. Not deployed ABIs.
Motes' architecture is built around narrow, reviewable interfaces. This page explains the integration categories without presenting unpublished contract addresses as deployed facts.
Proposed module families
| Module | High-level role | Safety boundary |
|---|---|---|
| NFT registry | Map token ID to account | Immutable, verified identity relation |
| Account validator | Verify signer and owner policy | No unconstrained delegation |
| Execution module | Run authorised calls | Restricted targets and calldata |
| Strategy registry | Version and revoke policies | Owner-signature authority |
| Fee accounting | Classify billable activity | Single-charge accounting |
| Oracle and risk adapter | Value exposures and limits | Freshness and manipulation checks |
| DeFi adapter | Integrate a supported protocol | Router and function allowlists |
| Prediction adapter | Connect an eligible market venue | Venue and jurisdiction checks |
| Monitoring system | Reconcile results and alert users | Cannot expand spending limits |
Illustrative read-only data model
AgentIdentity { chainId, nftContract, tokenId, smartAccount }
OwnerPolicy { policyId, owner, validUntil, targets, assets, limits }
Activity { agentId, policyId, actionType, proposedAmount, status }
Receipt { chainTxHash | venueOrderId, settledAmount, fees, timestamp }