Introduction

Monorepo map

A contributor-oriented map of the workspaces that feed the docs site.

Top-Level Map

Path	Responsibility
`frontend-app/landing`	Brand surface and product messaging
`frontend-app/web3-app`	Wallet UX, mint/burn UX, activity feed, transaction flow
`frontend-app/web3-app/subgraph`	GoldSky / Graph indexing workspace
`frontend-app/everstrat-docs`	Public docs site
`smart-contracts`	Protocol contracts, interfaces, tests, scripts
`mermaid`	Architecture, role, and deployment diagrams

Practical Reading Order

Use landing files for tone and terminology.

Use smart contracts and tests for protocol truth.

Use the web3 app for current shipped behavior.

Use subgraph docs for entities, lifecycle indexing, and query examples.

Drift Rules

When addresses change, docs must follow web3-app/src/config/index.ts.
When queue semantics change, docs must follow smart-contracts first and subgraph mapping second.
When the app ships new UX behavior, docs should describe the shipped path, not the old one.

Last updated on

How the system is organized

The relationship between the landing site, docs app, web3 app, contracts, subgraph, and supporting diagrams.

Core concepts glossary

Shared vocabulary used across the product, protocol, app, and data model.

On this page

Top-Level Map Practical Reading Order Drift Rules