Ecosystem Architecture
A conceptual map of product responsibilities.
Conceptual diagram. This is not a map of deployed infrastructure.
The proposed stack separates what a person sees from where data is stored and from which actions require a blockchain transaction. Social software can remain responsive while ownership and payment actions stay explicit.
Responsibility split
| Layer | Responsibility | Status |
|---|---|---|
| Experience | Screens for social, wallet, and creator tasks | Planned |
| Social application | Profiles, feeds, communities, messages | Planned |
| Identity | Account, session, and permission concepts | Foundational design only |
| Wallet | Connection and transaction approval | Planned |
| Data | Off-chain content and settings | Not deployed in this repository |
| Contracts | Selected payment and ownership logic | Not deployed |
| Networks | Base and Ethereum Mainnet | Target networks, not a live integration |
