System Overview
Six components, one direction of value, one data seam.
Frontend01
Server components, client islandsProtocol adapter02
The only data seamContracts03
Not deployedEvents04
Emitted per actionIndexer05
Not connectedProtocol data06
Series, activity, accountingComponents
| Component | Responsibility | State |
|---|---|---|
| PILE | Liquid supply and transfer | Not deployed |
| vPILE | Claim accounting | Not deployed |
| Wrapper | Mint and unwind the claim, charge wrap fees | Not deployed |
| Stockpile vault | Custody acquired assets, report balances | Not deployed |
| Reserve engine | Convert fees into acquisitions | Not deployed |
| Fee router | Collect and account for fees per source | Not deployed |
| Oracle registry | Valuation for NAV and claim value | TBD |
| Lending market | Credit against the claim | Phase II |
Direction of value
Value moves one way. Fees enter the router, the router forwards to the reserve engine, the engine buys assets, assets settle in the Stockpile. Nothing in the design moves assets out of the Stockpile except a redemption, which requires burning the claim that entitled it.