Vitte Source
Repository organization, contribution flow, and entry points for developers.
Compiler Vitte
The source view reads the project through the Vitte compiler stack: driver surface, grammar surface, snapshots, and repo checks are aligned around the same code paths.
Understanding the compiler
The Vitte compiler reads as a series of simple layers: parser, resolution, IR, then backend, with the driver and linting surface expressed in the same language as the rest of the repository.
- Parser : reads the code and builds the AST.
- Resolution : connects names, imports and symbols.
- IR : lowers to an intermediate representation.
- Backend : produces the target code.
Example read path
# Read the parser entry point
open src/vitte/compiler/parser/main.vit
# Read the HIR/MIR lowering path
open src/vitte/compiler/middle/lower/mir_to_ir.vit
# Inspect the bootstrap contracts in docs
open docs/bootstrap_seed.html
This example shows how to follow the source path from parser, through lowering, to bootstrap and documentation contracts.
Flow
- Main flow:
source -> parser -> AST -> resolve -> IR -> backend -> output - Reading errors:
diagnostic -> layer -> cause -> minimal fix -> rerun
Current compiler notes
- The driver implementation lives under
src/vitte/compiler/driver. - The grammar and parser sync work now point at
src/vitte/grammar/vitte.ebnfand the parser coverage report. - Repo-level checks such as package layout, legacy import lint, and docs path checks are tuned to the Vitte-only tree.
Useful references
- Compiler Pipeline
- Overall Architecture
- AST Mapping -> IR
- Bootstrap Native IR
- Bootstrap Seed Contract
- Module Reference
- Grammar Diagrams
- Grammar Reference
- Railroad SVG
Source-backed reading paths
Governance and long-term maintenance
- Governance pack index
- Long-term ecosystem maintenance
- Platform governance complete
- Platform maturity baseline
- Release engineering
- Migration and editions
- Version compatibility matrix
Contribute
- Read CONTRIBUTING.html
- Open the Sitemap
- Open the Book Home
- Open the Technical Index
- Prepare a short patch, then restart validation.