> Say I dump UXN machine code and encounter an immediate branch but have no symbolic information of the code, how should this then be shown?

The way I display it in disassembly usually is like -9/+9 type things,
because having the direction of the jump sometimes helps to understand
what it is, especially for loops. But normally, in disassembly, I have
the symbols file, so I grab the symbol at the relative absolute
address:

https://wiki.xxiivv.com/site/bicycle.html

Bicycle is also a good tool to test assembly/disassembly, how uxntal
maps to bytes, you should try it out :)

> Oh, all these runes confuse me... Can someone write a rune tutorial, please? :-)

There's a small tutorial here:

http://wiki.xxiivv.com/site/uxntal_syntax.html

The difference between raw and literal, is the literal opcode prefix, so

[ LIT _label ], is equivalent to ,label
[ LIT -label ], is equivalent to .label

For most things, you should not need to be writing raw runic labels.

Have you seen Nettie's cheatsheet?

https://raw.githubusercontent.com/weeble/uxn-cheatsheet/main/uxntal-cheatsheet-normal.svg