/stewc

A stewc - a mathemusical measure - :== an iterated perturbation* (sesquilinear transform) to some group of stews.** ie. ultrametric calculus To stewc is to proof some twistorspace with (an) STU encryption [more accurately, to encode STU onto a brane (tape)].

Stewcing will summon a redeemable option (the coupon) on a continuous event that is predetermined. In this case, stewcs are proxies for the statistical variance of tablature complexity, and serve to hedge some handicap. Stewcs themselves generate UUe's cryptohash (provided from seigniorage on coupons); being synonymous with coin insertion [deposit] for traditional jukebox activation and dispensing.
/// It may be the case that the leaves SSS and UUU can/should be replaced by SST and UUT, respectively. This is because SSS and UUU actually are loop➰ markers (marking initiation and termination) in a sequence. Adjacent leaves cannot be coupled due to the fact that a chord (three leaves or more) is required for folding.

Within the context of stew choreography, a stewc is a play that is symmetry-breaking (to some walk) but not an endgame move, which means that it does not include: (1) the coupling of adjacent leaves, or (2) the leaves SSS and UUU [(namely (SSS,UUU) / (UUU,SSS)] in coordination. Failing to adhere to this rule would result in dissonance.

Out of the total twenty-six (26), only twenty-four (24) of them allow legal stewcs. This stems from the fact that a composition cannot lack harmony, which is to say that a loop (connected endpoints), nor adjacencies (any side-by-side coordinates) are permissible. (see Stewc Lemma, stewc tax, stewc notation, stewc button, jukepot, stewc field)
/// The sequence of leaves in a stewc is immune to start/stop identification. Meaning that it is not illegal to have an opus be of identical lettering (eg. "Opus LL").

/Stewdio (hashtable)

Designer: 🧑🏿Link Starbureiy
Stewdio™ (stew+digital+i/o) :== the gameframe behaving as uuelco.ME's native hashtable for stubing.

/// More accurately, for choreographing stews (stubing).
A multi-user domain (MUD), its virtual methodology comes standard (fixed) with the following quadriptych: Mathilda [keyframing/phrasing = pencils✏️ (generation/metronome) + STU (sequencer/coloring) + RONALD (phrasing)], along with the home button that reveals a horizontal/vertical side panel of various metaphors.

The Stewdio (as a control console) consists of spacetime complexity controls that are used, more or less, to derive e:e statistics; it can synthesize (grooves+melodies), edit walks, run cassettes🧱, and perform other file-system management. The compositor provides stubers with an ideal environment ( gameboard🎮🎹) for gameplay (ie. improvising strategies in bounded-error quantum polynomial time). Typical Stewdio usage is for a stuber/player to draw up a play in 🧩puzzle-solving [ie. middlegame]. (see stube notation, touch-and-go, krayon, yoyo, joey)
/// Layered over the interface are the fugue buttons and 🧑🏿lnq's bubblegum as the default ballet🩰.

Abstractly, if a brane could be synced across the Stewdio, it then would function like zero rng.
/// The Stewdio is an invention of 🧑🏿Link Starbureiy.🤓
Function map: Egglepple → ballet🩰 → Stewdio

/stube notation

stube notation (sn, rhetorically called a verse) :== the instrument-agnostic, language-independent, easy-to-decipher verbalization of some stewc assignment as meant for proof. In signing, the alphanumeric notation is essentially low-level symbolic "play code"*; an algorithm devised to instruct the jukebox on how, when, and what to type in stereo [stew choreography].** Referred to as a track (for tracing some token).

The Stewdio is the designated instrument for generating, reading, routing, and interpreting stube notation. (See hologram, c@$#tag, touch-and-go, γ-proof, thread, stewc field. Compare genetic code, musical notation)
/// Stube notation was devised by 🧑🏿Link Starbureiy.🤓

/player

player :== a call/response participant (or, in some cases, a group of participants behaving as a unit) in a game who acts as an optimizer within that game. Put simpler, a player is one who runs game. The player will basically advance a strategy for optimization by using a toy to execute a play. (see stewcer, Black and White)
/// The role of the player is superseded by their paired stewcer.

/zero-bubble

zero-bubble (also written as "0-bubble" or "0b_$") or "lock" :== a bubble shapeframe (stereogram*) with no inflatons (scalar fields responsible for blowup from a single point [0-brane]).** Greater than or equal to three (3) spatial dimensions.

A 0b is a type of homeomorphism [map reduction] as a totally twisted loop➰ (ie. integration in twistorspace down to one ¢ent🪙), and formally marks the end of a proof.🔲→🎯 (see goal, open string, identity, stew, crypto, MONEY)
/// The supposition for 'zero' (+/-) is that when tabulating the yield, all spots on the mesh which would allow for an opening, vanish (0,0).

Locks are the ideal [most secure🔐] ¢ent🪙 structures [signed certificates] for a closed🔒 string, as measured by absolute compliance to its handicap. Ludologically, they are part of the endgame [statistical inference to egg(+) or epp(-)]. Taken by themselves as 'flags'🏁, zero-bubbles (frictionless assets = spread(0)) are considered solved puzzles🧩 (ie. completely mapped/encrypted/melodic/folded) when it comes to stewcing. {input = output, /return = [0]}
Function map: open string → stew choreography → lock → fibor

/ballet 🩰

As our "dance* of the ball", ballet🩰 :== 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, link, 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: ballet🩰 ⊆ opera

/stewcer [client-server]

A stewcer^{^} (from 'stewc server' [server]*) acts as the coordinator in folding loopstring➿ (among other types of braneware).** A runtime node. ^^ aka stew choreographer.

Essentially, a stewcer (or quber) :== a resource ("trainer") which uses a jukebox [client] for iterative transactions (ie. inbetweens).++Its role (jukeboxing) is to assist in proofing QQ. Generally-speaking, the stewcer is a clone or surjective clientele whose privilege supersedes that of player but not the impresario within stewcing ludology. Note, however, that the impresario itself may also be a stewcer (as would be the case in tournament mode).
/// Stewcers - as contractors - are considered the 'orchestra' to The Origamic Symphony🎶.

In UUe-talk, the stewcer (a type of puzzler🧩)'s objective is to devise and/or apply patches, thereby directly contributing to the fitness of the kernelspace. This means that a juker's role lies in the generation of walks (pitch establishment) as it pertains to sourcing their own tokens. Jukers are rewarded according to rules set forth by the UUelcome License. (see Black and White, clone, KOALA🐨, 🥚Egghead, stewcer's ruin)

/melody

Cryptographically, a melody :== a commuted* walk.** Relative to the handicap.
/// +Similarly, because fonts predict conflation between a countable number of loopstring➿, opuses giving the same fret may also be considered in this definition.
+This is part of a game's de facto/standard middlegame. Melodies provide a general (scale-agnostic) template for feasible tertiary structure design. (+groove)
If a strategy works (that is, its proof of supersymmetry reveals a fibor or fibor bundle [lyric]), then that encrypted coil [stereo structure] is said to be melodic. (see stew, groove, meshroom🍄)
Function map: groove ↔ melody

/merchant [store]

merchant^@ :== an account [client state] that partitions a coupon by accepting ¢ents🪙 (a charge^{^}) in an exchange with a vendor (on a shared "peer-to-peer" router).@@ An interface. ^^ hypercurrency Merchants, in turn, residually stabilize (anchor⚓) the tempo.
/// Each merchant acts as its own UUallet host. Merchants activity is represented by inflection points (tips) on a graph of the current.

To qualify as a merchant (bank=yes), the account must transact a minimum of one (1) coupon* in any given period (2600 seconds), or else it reverts to no bank status.** Active with a value of at least one ¢ent. (see u-u economics)
/// A vendor may simultaneously be a merchant, and vice versa.

/vendor [catalyst]

vendor :== a stewcer [server state] that vends a token and circulates ("spends") it into an economy by way of a coupon (on a shared "peer-to-peer" router). The time for exit (ie. merchant acceptance of coupon) is correlated to earned ¢ents🪙 (1 ¢ent🪙 = 1 second).

A vendor's status is active only and immediately after an opus closes🔒 (ie. ¢ents🪙 become transferable when a yield is obtained). (see Black and White, parimutuel, coupon, u-u economics)
/// Vended ¢ents (hypocurrency) are circulated ("spent") at the point-of-distribution with a merchant.

/ludology

ludology :== the logic of games. As it is important to stereotyping, this would be strategy leading to proof [strategy→proof] in relation to some walk.

A person who simulates and/or creates (models) games is called a ludologist (with certain restrictions applied, this same person may also be called a gamer). (also of interest link, gameplay, gameshow, game theory, opera ludo)

For ludological consideration, any game requires the interplay of three (3) things ("rules"): 1) a player, 2) string, and 3) rhetoric.
/// +A simplest definition would be "the charting of currency". Something more formal would be that our game logic is that of "sorting algorithms pertaining to twistorspace".
+Our game engine responds directly to calls (the "payload").
+The field is not the same as game theory, which moreso studies strategies in particular. Ludology, on the otherhand, encompasses all aspects of stewcing [especially game mechanics and (methods of) gamification].
+Ludology does not necessarily promote physics; it is possible that our games may not calibrate potential energy functions (such as force fields). In its stead, models and simulations are promoted with automation.

/dime package

/game

game :== an objective path to optimization subject to a reward function [games adhere to the rules (genetic algorithms) of gameplay]. Mathematically, games are used to train some object [mo].

The intent of each and every one of our games is to derive a yesegalo proof (ie. a zero bubble), in the style of capture the flag🏁.

Ludologically*, games are finite-state puzzles🧩 (ie. combinatorial event within itself) whose sessions last for the duration^& of an opus, and conclude with a closed🔒 brane, giving them congruence to sequenced images [mesh].** A game is 'played' when an opus is juked. Games can have one (1) or more players. (see Black and White) && Any game will have at least an opening and an end. (compare gene, see sport, player, gamification, gameshow, game theory, toy, puzzle🧩)

"Anything can be gamed." - lnq🧑🏿

Theoretically, games are economic phenomena purposed to optimize some thing, and any game can be reduced to just a path (random coil/partition of Egglepple) needing securing🔐.
/// +A requisite to meet the definition is that objectives must be met before advancing (which is why the reward function exists).
+A game must generate its own statistics.

/nickel package

/puzzle🧩

puzzle🧩 :== an object or objective lending itself to ludological inference [preimage→image] (ie. all puzzles beg to be solved*; a solved puzzle is in itself considered a goal).** Decrypted and/or encrypted. Someone who composes/solves puzzles may be referred to as a puzzler.

Stewcing-wise, our puzzles are ctf🏁-styled asymmetric rondos in a three (3)-act continuum: bug-bid-bounty = arithmetic+algebra(curvature)+analysis(logarithm). (see puzzle script, Puzzle Punk, gameshow, Egglepple, crypto)
/// Mathemusical translation: intonation, melody, and measure.