Ready.
Includes a file, by reading it from the disk. By default, \i is active, i.e., the included file is processed/interpreted by FIX.
After a successful reading of a file for include, the next line is not processed. You should leave an empty line after an include, if you do not mean to mutually-exclude the next line with the include being able to read that file (whether it is later revoked, or not). Wait a while till I release idioms (re-usable code examples), using this as part of a conditional-processing strategy.
Starting with Beta-1 release, I plan to (implicitly) define the file name of an unquoted filename, upon successful include operation, with a pointer at its start, with the file name (and maybe, another at the end). For example, for RunStart.afr, a pointer named "RunStart.afr" at its start (and maybe a pointer with a name "End_of_RunStart.afr", etc.) This may facilitate active inlines, skeleton-remappings (e.g. for structs/type[re]defs), and maybe calls, too.
\i= When there is an equal-sign in its ASK, an include service passively reads the bytes, i.e., places them at the current offset of the target pointer/cursor, without further FIX-processing.