Compiler · Integration

Compiler integration

Avisna integration is documented at the compiler and command-line boundaries. The website documents the toolchain contract without embedding a compiler or execution service.

Compiler path

The compiler pipeline connects source processing, semantic analysis, MIR, code generation, LLVM output, native linking, and the runtime. These stages are documented separately so each claim can be traced to the supplied compiler implementation and tests.

Source → Lexer → Parser → Semantic → MIR → CodeGen → LLVM → Native output
VERIFIED: the documented pipeline corresponds to the current compiler/toolchain architecture reviewed for the website.

Command-line boundary

The local CLI is the public operational boundary for checking, building, and running projects. The website documents these commands and their evidence without introducing a browser-side compiler.

avisna check <path>
avisna build <path>
avisna run <path>

Scope

  • Compiler and CLI integration are documented as local toolchain concerns.
  • No hosted compiler service is claimed.
  • No browser-native compilation or native execution is part of the website.
  • Editor protocol capabilities remain documented separately under Tooling.

Evidence

The compiler CLI implementation and the supplied regression corpus provide the evidence base for the documented integration boundary.