# Soatrix Knowledge Base

Welcome to the central technical and operational knowledge base for **Soatrix** products and services.

This wiki is designed as a long-lived source of truth rather than a collection of disconnected notes. Company-wide standards live under **Company**, product documentation lives under **Products**, and reusable documentation patterns live under **Templates**.

## Start here

- [[Company/Index]] — how the knowledge base is organised and governed.
- [[Products/Index]] — product catalogue and technical documentation.
- [[Templates/Index]] — reusable page structures for future services, decisions, incidents and releases.

## Current product documentation

### Voxel Horizons

- [[Products/Voxel-Horizons/Index]]
- [[Products/Voxel-Horizons/VoxelCore/Index]] — complete VoxelCore item/content MVP documentation.
- [[Products/Voxel-Horizons/VoxelCore/Current-Status]] — implementation snapshot pinned to `452b569` on `14 September 2026`.

## Knowledge-base principles

1. **The implementation wins.** Runtime code, tests and deployed configuration are authoritative when a prose page conflicts with reality.
2. **Implemented and planned behaviour are never mixed.** Roadmaps are labelled as plans; reference pages describe what exists now.
3. **Pages are scoped.** Company standards should not contain product-specific implementation details; product pages should link to company standards instead of duplicating them.
4. **Operational knowledge is actionable.** Commands, paths, validation steps and rollback behaviour should be documented where people need them.
5. **Changes are reviewable.** OtterWiki's Git-backed history is part of the documentation workflow, not merely a backup.

See [[Company/Wiki-Governance]] for the maintenance model.