FAQ.

The development preview includes a Windows x64 installer, a Debian 13 amd64 package, and a Visual Studio Code VSIX. The editor extension is also available directly from the VS Code Marketplace.

No. Both extensions have the same syntax and semantics. They communicate whether a file is mainly used as a program or a script. Either can be interpreted, bundled, or compiled when its features are supported by the native backend.

The Windows installer adds Galeikan to your user PATH. Close and reopen Terminal so it receives the updated environment, then run galeikan --help. Install the latest setup if you used an earlier preview installer.

No. Use galeikan run file.gaks for direct execution, or choose the VM with --engine vm. Compilation is an additional workflow for supported programs. The extension is a convention, not an execution restriction.

It supports offline project-local packages through a manifest and lockfile, with reproducible content checks. A hosted registry and automatic remote downloads are not part of this preview.

Yes, for project-local Python modules. Declare requires { python.exec }, import with a py.* path, and grant Python access at launch. Calls use bounded typed values through a process bridge.

Yes, in supported native programs. The compiled executable can call the Python bridge, but a compatible Python installation and the imported module files must remain available. Python code is not compiled into the Galeikan executable.

Yes. The optional galeikan_bridge Python package can call Galeikan functions. A session can keep the Galeikan process alive for repeated calls and stateful work.

Not yet. Native Galeikan and Python remain separate runtimes connected through the bridge. Shipping a program that uses Python means shipping or requiring its Python modules and a compatible Python runtime.

Python remains excellent for broad automation and existing libraries. Galeikan adds research-specific Source lineage, format and disassembly primitives, explicit effects, verifiable case records, and a native compilation path for supported code. The bridge lets you combine them where each helps.

No. Its APIs help collect, inspect, and document evidence. PE and ELF fields, byte patterns, and protection signals are observations that an analyst must interpret.

No. The declaration and matching runtime grants make supported effects explicit and bounded, but they do not replace OS isolation for untrusted code. Python modules also run with their normal OS permissions.

Yes, where operating-system permissions allow it. Process APIs expose regions and bounded snapshots; a program must declare process.inspect and receive a PID grant.

A case can store source hashes, lineage, observations, findings, relevant artifacts, and a manifest. The verify-case command checks the stored integrity relationships without executing the program again.

No. It supports a growing x86-64 subset and rejects unsupported constructs. The interpreter and VM currently cover more of the language.

There is no fixed date. Native parity, stable language semantics, security review, English documentation, and platform validation are release criteria.