Start with Why WE Exists — the vision, the problem, and what WE is for.
New to WE? Start here.
- Developer Setup — Prerequisites, clone, build, run
- Seed System — How
we-seed.jsonconfigures everything
How WE is designed and why.
- Codebase Map — Start here. Current package layering, AD4M runtime, render pipeline, framework-agnosticism strategy
- Package Conventions — How packages are structured and named in the monorepo
- Why a Meta-App Instead of Many Separate Apps? — Why shared continuity and cumulative evolution matter
- Practical Examples — Simple examples of how WE ideas work in practice
How to build with WE.
- Launcher UI Customization — Customizing boot screen and settings via seed
- Cesium Layers — Using the 3D globe layer system
- Cesium Implementation — Implementation details and status
Working notes for maintainers — plans, design decisions, and superseded documents.
- decisions/ — Design decisions and rationale (block system, schema system, template storage, semantic predicates, AI integration)
- plans/ — Strategy docs for upcoming work
- old/ — Superseded documents, kept for historical context
Note: documents under
internal/old/and some underinternal/plans/describe designs that are aspirational or have drifted from the implementation. They carry a warning banner. For the current state of the codebase, always use the Codebase Map.