Populi data pipeline (control plane vs Mens corpus)
Populi in this repo names the HTTP mesh / control plane (VOX_MESH_*, node registry, A2A, optional GPU hints). That is runtime coordination data, not the same artifact stream as Mens training JSONL.
Mesh / control plane (operational)
- SSOT: mens / Populi reference (env contract, HTTP API shapes).
- Telemetry: optional Codex rows for control events—see orchestration unified.
- Examples: mesh worker script lives at
examples/golden/mesh/noop.vox(Docker/opt/vox/mesh-noop.vox).
Mens training corpus (offline ML)
- SSOT: Vox source → Mens pipeline, Native ML pipeline, Mens native training.
- Sources: primarily
examples/golden/**/*.voxplus configured mix paths (vox mens pipeline,vox_corpus).
Rule of thumb
| Question | Answer |
|---|---|
Where do I add a verified .vox snippet for docs? | examples/golden/ + {{#include}}; see examples.ssot.v1.yaml. |
| Where do mesh nodes register? | Populi HTTP client + registry—see Populi reference. |
| What tokenizes Mens supervised strings? | HF tokenizer for the base model on the QLoRA path—not the Vox lexer. |