Everstrat Docs home
Contributing

System and responsibilities

Runtime relationships and ownership boundaries across Everstrat's standalone repositories.

Ownership boundaries

Repository / directoryOwns
everstrat-xyz/contractsProtocol implementation, role model, deployment scripts, tests
everstrat-xyz/keepersOff-chain Mimic decisions, relay logic, gas policy, task runbooks
everstrat-xyz/governanceProposed and executed privileged operations
everstrat-xyz/appWallet UX, mint/burn, Portfolio, Metrics, and transaction lifecycle
everstrat-xyz/app/subgraphIndexed event model and deployment configuration
everstrat-xyz/websiteLanding page and product introduction
everstrat-xyz/docsPublic explanations, references, search, and LLM exports

Documentation describes these boundaries; the logic lives in the owning repository. For live protocol assertions, verify chain state as well as source.

Runtime relationship

Users mint or redeem through AMM. Controller and StrategyManager coordinate registered strategies. Mimic functions call authenticated executor contracts to perform routine work. ADMIN changes parameters and upgradeable components through governance; SECURITY has designated immediate emergency powers.

The app reads live state and indexed history. It does not itself price batches or operate strategies. Documentation records implementation and dated deployment evidence. It does not guarantee uninterrupted operation.

User and protocol surfaces

Source locations

Protocol implementation lives in everstrat-xyz/contracts/src; diagrams in mermaid/. Application features, address configuration, and the subgraph live in everstrat-xyz/app/src and everstrat-xyz/app/subgraph. Mimic tasks and governance records have their own repositories.

Last updated on

On this page