Optimizing work flow (in Carbon??)

On optimizing work flow

So, given how Prolog runs and is traceable, run x/y*nbit^x on z*nbit^x as in 4bot on an 8bot which could be interpreted EVEN ON 2 BOT or BITs given time AND given an interpreter of an interpreter tracing the trace calls.

Basically instantiate Prolog inside a Prolog interpreted shell, AKA 5th eye chakra, AKA shell a fucking shell, aka RUN: RUN an Environment.

Got that straight?

So, on how to trace and remove noise:

i(j) = I = trace(bitlength)

trace = trace(-trace(x, break))

break = insert "break;"

// Right, Carbon?

This should be defines as:
>> = i(j) = I = trace(bitlength)

>> being the operator to run a fucking meta-trace^("number of > symbols-1")

Abbriviate how you like for trace depth n, like:

>>^n, n = positive integer

DO NOT TRY FRACTION CALLS or instantiate >>^n, n > 0 & n < 1 as SOMETHING. DEFINE A CONSTANT.

Thats HACKING THE FUCKING MEMORY CALLS.