We have made the documentation bundle by means of the emacs command M-x make-elucidator. This command creates the documentation file, the first program file, and the setup file. It also creates the necessary and underlying file and directory structures. When we execute this editor command we are asked to process the LAML file, and to activate another emacs command setup-elucidator. We just do that.
In this entry we can start discussing the Scheme program. Just to have something on the program side, we have made the well-known fak function in meta-demo. So we make a reference to it. If we have lost the editor context we can always say C-e C-r (or M-x elucidator-reset-elucidator) to establish the characteristic split view editor panes with documentation in the top window and program in the bottom window.
Now let us discuss fak. The reference just inserted is conveniently made by selecting the fak header in the Scheme file and entering C-e C-p (elucidator-program-ref). It turns out that this makes a full qualified reference (file and name). The reason is that the editor - at this point in time - does not known any thing about fak. If the documentation bundle had been processed (abstracted) we would have this knowledge. We may change this policy in the future.
We now process the documentation bundle by C-e C-o (or M-x elucidator-elucidate).
The functions in meta-demo are list-prefix and its helping function list-prefix-1. Notice first the strong reference (red) and the weak reference (blue). We may also just make typographic emphasis, like list-prefix-1 (C-e C-w).
At the bottom of other-source we see a definitions of key-list and val-list. Following these definitions we see aref-assignment, which in a rather informal way denotes a section of the program via use of a so-called sectional comment in other-source.