So,
In the method description is where the more conceptual / general framing of excercises have to enter
using the See Also/Good to know and cross-referencing methods as a way to create grouping..
The tone/ discussion/ specificity has to enter with snippets/ reference to collected materials and examples.






    
* separation at work:
        4 separated methods interlinked.(as "A-quine track"?)
QUINE

Method: Quine
*What: A program whose function consists of displaying its own code. Also known as  "self-replicating programs"
*Why: With quines, the tension between "software as language" and "software as operation" is shown in all its density. 
*How: Self-reflexive coding
*See also: http://pad.constantvzw.org/p/observatory.guide.monopsychism
*Part of: Aquine, a discussion of and research into dualism in software http://pad.constantvzw.org/p/observatory.guide.aquine

Example of a quine (Python). When executed it outputs the same text as the source:

% python
s =  's = %r\nprint(s%%s)'
print(s%s)
% endpython

Example of a oneline etherpad quine, created during relearn 2017
%INCLUDE https://gitlab.com/relearn/relearn2017/raw/master/complex.local/home/etherpad/etherdump/quine.raw.txt

---------------------------------------------------------------------------------------     

method: PANPSYCHISM
what: reading and writing sectors of memory of/to different computers
why:  to challenge the process/file divide. to have a more intimate relation with your and others computer
warning: may damage your ram
good to know: aquinas famously opposed averroes..who's philosophy can be interpreted as monopsychist :)
how:???

to do: lists of tested and speculative exercises
------------------------

FMEM and /DEV/MEM
what: Observing your memory. Because in unix everything is a file, you can access your memory (RAM) as if it were a file. 
why: Different ways of exploring the RAM in the attempt of observing the operational level of software, getting closer to the workings, the instruction-being of an executable/executing file, the way it is when it is loaded into the memory rather than when it sits in the harddisk
Good to know: In the early days, the easiest was to dump the memory from the memory device (/dev/mem) but over time the access was more and more restricted  in order to avoid malicious process to directly access the kernel  memory directly. The kernel option CONFIG_STRICT_DEVMEM was introduced  in kernel version 2.6 and upper (2.6.36–2.6.39, 3.0–3.8, 3.8+HEAD). So  you'll need to use a Linux kernel module in order to acquire memory.
fmem 1.5.0 This module creates /dev/fmem device, that can be used for  dumping physical memory, without limits of /dev/mem (1MB/1GB, depending  on distribution)
How:

    different exercises
    

AQUINAS

===

or all methods:
QUINE
PANPSYCHISM
FMEM and /DEV/MEM
?pixel-surgery
?sound-therapy

with files/aquine as context
all "contexts" are a newly written entry maybe at the end of the guide.they are not methods.they are more documentation
links

----

* context-creation (talking about general concepts with examples)

AQUINAS( general container?)
*QUINE method,
*FMEM/DEV/MEM method,
*with PANPSYCHISM as our crazy detour







TIME
http://observatory.constantvzw.org/etherdump/ends-of-time.html
http://observatory.constantvzw.org/etherdump/negotiating-time.md.diff.html

unix-time
ssh-time-strike idle-time

Sundial Time Protocol Group tweaks
printf 'Current Time in Millennium Unix Time: '
printf $((2147483647 - `date +%s`))
echo
sleep 2
echo $((`cat ends-of-times/idletime` + 2)) > ends-of-times/idletime
idletime=`cat ends-of-times/idletime`
echo
figlet "Thank you for having donated 2 seconds to our ${idletime} seconds of collective SSH  pause "
echo 
echo