A loop is not a data-structure, but a phenomenon, stupid!

I've lost my way to whether Loop shall be a class or such-a-name of phenomenon.
To track loops are copied, joined, paraphrased, and deleted etc., I need a Class (of Java) or such a programming jargon.
But it would do harm to (the (ability|performance)  to emulate the virtual machine of INTELLIGENCE. | clarity of model).

Loop is not bound by a priori structure. Vivid and lively sequence of firing of synapses are stuck in some limit-cycle or attracted in some patterns, we just say 'I found a loop'.
So I need some criteria to call something as 'loop'.

Here is my idea on API.

Criterion:
Network.isLoop(time-coverage t, place-coverage p) : Network object instance method

Matching:
metric-type Network.similar(Network.coverage a, Network.coverage b): Network Class static method

Copy (Dup?):
void Network.map(Network.coverage c): Network object instance method

for Join (concatenate),  Divide, Connect, Merge, Overlap, Head, Tail, Cur, Cdr can be given if Loop is just a sequence of objects as Lisp. But I want to see how a loop is established, long-run, diminished,, the dynamics of it.
Dynamics and structure of (dynamic and plastic) network is the key, I think.

So, I need to see the very moment of 'birth of the loop', in various type of network model.