Golden Examples Corpus
The Vox documentation utilizes a “Golden Example” architecture to prevent documentation drift and ensure that all documented code actually compiles against the latest compiler version.
How goldens and docs feed Mens training (lexer vs HF tokenizer, corpus roots): Vox source → Mens pipeline SSOT. Pair layout and hygiene: Mens training data contract.
How Golden Examples Work
Section titled “How Golden Examples Work”Instead of writing raw code blocks directly inside Markdown files, documentation should pull snippets from the examples/golden/ directory.
CI enforces goldens in two layers: (1) vox-compiler integration test all_golden_vox_examples_parse_and_lower — every examples/golden/**/*.vox must parse, lower to HIR, pass WebIR validation, and emit Syntax-K metrics; (2) mdBook / doc pipeline — pages that use {{#include}} must resolve to real golden .vox files (examples_ssot test). A full vox build per golden may run in additional doc or integration jobs; do not assume “build-only” is the only gate.
Adding a Golden Example
Section titled “Adding a Golden Example”To document a feature with machine verification:
- Create the file: Create a valid
.voxfile inexamples/golden/. - Write the code: Add the required logic to the file. Ensure the file works when compiled.
- Define regions: If your file is large but you only want to document a specific function, wrap the target logic in
[REGION:name]anchors. - Include it: In your Markdown document, use the standard
mdbookinclude syntax:
{{#include ../../../examples/golden/my_example.vox:my_region}}Inline Doctest Verification
Section titled “Inline Doctest Verification”Sometimes a page includes brief, self-contained inline .vox examples alongside or instead of {{#include}} regions.
Every ```vox code fence in active documentation is compiled and type-checked by vox-doc-pipeline during linting. Inline examples must be complete, valid .vox declarations (for example, wrapping a snippet in a fn or component declaration):
fn double_value(x: int) to int { return x * 2}By ensuring every ```vox code fence is either a golden include or a self-contained, compiler-verified declaration, Vox guarantees accuracy across its documentation corpus.