A
Trace every source
Publish a source and dependency inventory, including generated code, bootstrap compilers, runtime libraries, and build-time tools.
From source to execution
Every layer matters.
Every dependency, too.
A toolchain is only as independent as its least visible dependency. Our proposed scope connects the essential tools into one understandable, verifiable stack.
Proposed scope · No releases yetExplore the building blocks
SELECT A COMPONENT ↓01 / Proposed component
Compilers
Translate source code into reliable machine instructions, with a transparent path from language semantics to executable output.
SOURCE → PARSE → OPTIMISE → GENERATE
Intended responsibilities
- Define an initial language subset and a documented intermediate representation.
- Build a testable front end and target-specific code generation.
- Make every bootstrap step inspectable and repeatable.
An open design question
Which language and CPU target give us the smallest useful, independently verifiable starting point?
More than a collection of tools
Independence is
an acceptance criterion.
These are proposed checks for future releases. Each one needs documented evidence—not just a label.
B
Build without the network
Start from documented inputs held in the EU. Disable network access and reproduce the full build without external registries or APIs.
C
Verify independently
Compare outputs across separate EU-operated environments. Make provenance, verification steps, and any remaining limitations public.
A careful starting point, not a promise to replace everything.
Languages, architectures, licensing, and the bootstrap strategy are not yet selected. Hardware sovereignty and a complete operating system are outside the initial proposed scope. These boundaries should be revisited openly as the project develops.
Bring your technical perspective
Help define the first working stack.
Good architecture starts with the right questions.