Primitive is a bit of a word conflict here; primitives are what we'd
expect our callables to be named eventually. However, these parser
"primitives" are just well known symbols that we want to optimise the
representation of for later stages. Thus, KNOWN is a bit better for
signalling intent then PRIMITIVE is.
Main reason is so we don't have that stupid arl prefix directory in
our source code. Now our source code is flat, and we can still
reference headers by linking from root.