For learners
Start with fundamentals, then move gradually into tooling, systems, and robotics.
Follow the learning path →Systems · Embedded · Robotics
Program the systems that move the real world.
Avisna is a programming-language platform for systems, embedded networks, and robotics. Learn the language, inspect the toolchain, and build toward robotic software.
// Evidence-backed language example
fn main() -> int {
let value = 2 + 3
value
}In one sentence
Avisna connects language learning with systems and robotics work.
The project is focused on helping learners and engineers move from understandable programming concepts toward compiler, embedded, and robotics-oriented work while keeping the evidence boundary visible.
For engineers
Inspect compiler stages, diagnostics, native execution, and the current boundaries of the toolchain.
Inspect the compiler →For robotics work
Connect programming concepts to movement, navigation, simulation, and tested scenarios.
Explore robotics →Why Avisna
One platform, several layers of the system.
Systems
Explore compiler stages and low-level execution without hiding the machinery behind the language.
Embedded
Build toward constrained targets, runtime behavior, diagnostics, and embedded execution.
Robotics
Connect programming concepts to robot behavior, simulation, and physical systems.
Your first five minutes
A clear path through Avisna.
If this is your first visit, you do not need to read the whole site. Start with the project direction, learn the fundamentals, then use the evidence-backed reference as your map.
Understand the project
See what Avisna is trying to solve, who it is for, and what it deliberately does not try to be.
Read About Avisna →Start learning
Follow a gradual path from language fundamentals toward tooling and robotics.
Open the learning path →Verify what exists
Use the documentation status model to distinguish verified behavior from demonstrated or not-yet-established areas.
Open documentation →Compiler architecture
From source to target.
The supplied project material supports this high-level compiler/toolchain view. Detailed language semantics remain subject to verification.
Avisna source
Lexer
Parser → AST
Semantic analysis
↓
↓
↓
↓
MIR
Code generation
LLVM
Target / runtime
Documentation status
Build the docs from the compiler.
Documentation is classified by evidence level. Verified, Demonstrated, Planned, and Not established content are kept distinct so the site does not overstate the current project evidence.
The current documentation is derived from the supplied project source, tests, and audit reports. Areas without sufficient evidence remain explicitly limited or unestablished.