Lead with Purpose
Every page should answer what the system is for, who owns it, and what boundaries protect it.
How to extend the manual
Documentation Style Guide
The public manual should explain the engine clearly without exposing implementation noise or promising unfinished workflows.
Use Stable Terms
Prefer glossary terms such as Asset, FragmentAsset, SceneAsset, Actor, and ComponentDefinition.
Separate Current and Future
Mark planned capabilities as future work. Do not describe deferred features as already supported.
Keep It Offline
The manual must work from the built site without external scripts, fonts, or CDNs.
Page Checklist
- Clear title and lead paragraph.
- Navigation matches the rest of the manual.
- Related Reading links point to real local pages.
- Architecture boundaries are explicit.
- Mobile layout remains readable.