Fe Language Reference

This page is a placeholder

A formal Fe language reference — special forms, evaluation rules, scoping, tail-call semantics, error handling, the standard library beyond NoshAPI, arena lifecycle — is a known gap in the platform reference. It is queued as a v2 deliverable.

In the meantime, the authoritative material lives in:

• ADR-0001 — Lisp as the sole cartridge authoring language — substrate decision, memory envelope, arena/no-GC discipline, dual-target (emulator + device) constraints. Includes worked examples.
• ADR-0010 — ICE Breaker Lisp re-expression — a complete reference cartridge expressed in Fe Lisp. Read alongside ADR-0001 for syntax-by-example.
• ADR-0007 — Scripted mission FFI & contract model — pure-computation builtins available to mission-context Lisp (if, let, lambda, map, filter, reduce, car, cdr, cons, null?, quote).
• Fe VM Benchmark Results — measured latency and footprint.

The upstream Fe project (rxi/fe) is the canonical source for VM-level semantics; KN-86 does not fork the language.

What’s missing here

A v2 deliverable will fold the following into structured pages on this site:

1. Special forms and evaluation rules.
2. Scoping and closures.
3. Tail-call behavior and the call-stack envelope.
4. Error semantics — propagation, recovery, the dispatch contract for handler exceptions.
5. The Fe standard library beyond NoshAPI (arithmetic, comparison, type predicates, string ops, list primitives).
6. Arena lifecycle — when arenas reset, what survives across resets, save/restore patterns at mission boundaries.
7. Macro behavior, if any (likely out of scope for v0.1).