How to read this wiki

This is a working engineering wiki for Voxamine, not a marketing manual.

The documents have different jobs

• Masterplan defines the product, its scientific contract, MVP gates, and known contradictions.
• System maps make the assembly boundaries, runtime hand-offs, and player-visible science loop inspectable as graphs.
• Build and test is the practical path from a fresh checkout to a tested player or standalone-server artifact.
• Chemistry foundations describes the simulation model and the boundaries it must not cross.
• Chemistry sources records where values came from, what has been validated, and what must remain unimplemented until it is sourced.
• Production notes cover repository rules, asset provenance, and integration work.

Read claims at their evidence level

The project distinguishes between measured, calculated, inferred, and unknown. An approximation can be useful, but it must be named and bounded. The same standard applies in the game: a player should see evidence before the journal makes a causal claim.

Keeping the site current

The site runs npm run sync:docs automatically before npm run dev and npm run build. Edit authoritative documentation in the repository’s Docs/ directory, then rebuild this site. Do not edit generated pages under src/content/docs/architecture, development, design, science, or production directly.