Repository map
Current standalone repositories and the legacy hackerhouse source history.
Current repositories
| Repository | Source responsibilities |
|---|---|
| contracts | Protocol contracts, interfaces, libraries, tests, deployment scripts, and Mermaid diagrams |
| keepers | Mimic W1/W2 functions and automation runbooks |
| governance | Safe/timelock proposal payloads, operation IDs, and execution records |
| app | Web3 app, Portfolio/Metrics, and subgraph/ |
| website | Landing page |
| docs | This documentation site |
The app, website, and docs build from their own repository roots. Some repositories require organization access even though their deployed sites are public.
Legacy history
Guide-DAO-Organization/hackerhouse contains the source history preceding extraction.
It is private and requires repository access, so it is not a public contributor entry point. Old references to
frontend-app/web3-app, frontend-app/landing, and frontend-app/everstrat-docs
are historical paths. They do not match the current standalone checkout layout.
Evidence hierarchy
Use deployed code and pinned chain reads for live behavior, contracts source and tests for implementation, app source for UI behavior, and governance payloads for proposed changes. Keep proposals separate from execution receipts; repository main can be ahead of deployed code.
Reading order
- Use contracts and tests for implementation details.
- Compare deployed versions, Registry state, and pinned chain reads before calling a change live.
- Use governance records to distinguish proposed, scheduled, ready, and executed operations.
- Use keepers for off-chain execution and gas-policy behavior.
- Use app features and
subgraph/for UI, indexed data, and accounting behavior. - Use website copy for introduction and docs for the detailed public explanation.
Drift rules
- Registry peers and strategy registration can change without changing an app's core addresses.
- A Controller source upgrade can be merged while its proxy still runs the earlier version.
- A deployed strategy is not part of NAV until registered.
- A signed Safe proposal is not a timelock execution.
- Indexer history is not the authority for current wallet balances or request eligibility.
See System and responsibilities for runtime relationships and ownership boundaries.
Last updated on