Showing posts with label programming. Show all posts
Showing posts with label programming. Show all posts

### +The Origamic Symphony🎶

The Origamic Symphony™℗ (Q) is the totality of Egglepple('s) movements (ie. keys in sequence).

Resting atop the hypothesis that every brane arrangement is (geometrically) convertible, solvable, and scorable, Q♯ is responsive to the calculus of Egglepple resonances (the program of the portfolio imagined as frets pertinent to stereotyping EGP).

"There is this beautiful symphony playing - everywhere, all the time."^ - 🧑🏿Link Starbureiy
^^ Symphonic evidence is its subject (UUelcome).

The symphony treats the entire portfolio as a (single loopstring*) path integral (line) subject to integration (including integration-by-parts [the twisting of pencils]) and derivation.** A continuous `function`. -- All walks are integrated in twistorspace, and output some stew derivative. (see UUelcome, quantumquotient, UUhistlegrass, 🧑🏿lnq's Starting Five, Juke Lemma)
/// +The Origamic Symphony is the subject of 🧑🏿lnq's recital.
+Here "origami" specifies "p-`brane` (`membrane`/`frame`) folding". Namely, it is the `twisting` of `measures` (length) between the Planck and nano `data`.

### +ballet 🩰

As our "dance* of the ball", ballet is an improvisational program [opus] that synthesizes walk categories from random coil.~** In the Egglepple scenario, the 'dance' is `stew choreography`, and the band of dancers is yots. ~~ What I refer to as 'walking the `string`'.

Each ballet is a frame arrangement [lyrically, the bundling of two (2) or more fibors (either by encryption or decryption) into gameplay]. (see Starbureiy ballet, groove (scheme), opera, #opéra-ballet, #libretto)
/// We may consider ballet to be the transition from `opening` to `endgame`. I prefer to think of a ballet as an `opera's` lemma.
Function map: balletopera

### +opus

As it pertains to juking, an opus [technically, "opus number", as some quotient (1/676) of Stewart] or developus is a finite stew choreographical instance resulting in a completed typeface mutation. Plainly, an opus is the computation (ie. encrypting EGP on a discretized brane*, subjugating some thread) of some partition of Egglepple (ie. movement).

Each new opus (an event [game]) will commence at the request [draw] of its ballet, thereby instantiating a unique node on Big-O Tree. Opus conclusion occurs when its 🧩puzzle is solved, and should validate a fibor, which is to be then readied for kernel registration.

Depending on its texture, an opus may be referred to as an opera@, operetta (diminutive), or opéra-ballet (ob).@@ Which is technically a `kernel`'s `logic` path or `operation` (a walk involving non-impresarial decision-making).
/// Actually, an opus may overlap with, but is of a different genus than a `developus`.

An opus is a method of cataloging a juke (much like with symphonies, operas, regular pieces, etc.). Publication assignment gives opus sets a maximum of six-hundred seventy-six (676) [corresponding to the alphabetical varietals of stew, (A-Z), in binary form]. For example^, a work may be published as "Opus AB, Number 14" (written as Opus AB.14), where "Number 14" - is the fourteenth iteration of the ballet performed on the loopstring, "AB" (its port - the letters of the start and , respectively).^^ Default opus is #LS.35[64].

For all intents and purposes, opus titles say, "". Each iteration itself may also be nested (eg. "Opus AB, no.14c"). (see toonage, mixtape)
/// Iterations are basically variations of pencil quantities, and by necessity, `font` count. In nesting, we let p stand for 'pencil', and f stand for '`font`'. The opus' title and number remain as is; they are established. The iteration only changes either the pencil or `font` count. So, for example (purely meant to be hypothetical and unofficial), let Opus GU, No. 4 have a (830 x 4,116) tab. An iteration of this would be Opus GU, No. 4f2885, where the pencil count (830) is unchanged and the `font` count has been reduced to 2,885. Or, we could have Opus GU, No.4p910, where the font count (4,116) remains unchanged and the pencil count has increased to 910. Again, purely hypothetical.

### +hash

A hash (#) is some declarable datum (eg. measurable in ¢ents), plus an operator* on that datum, mapped to an arbitrary function space.** Each index is a specific hash. The act of hashing would be congruent to bifurcation at some limit. (see patch, flageolet pencil, thread, UUhistlegrass, crypto, twistorspace, hash opera, ca\$htag, juke notation)