Skip to content

Juggling notation

A formal symbolic or diagrammatic representation of juggling throws, catches, hands, timing, crossings, and object trajectories used to communicate and analyze repeatable patterns.

Version
v1 · 2026-09-08 · History
Domain-specific #
5160
Origin domain
juggling theory and performance notation
Subdomain
juggling theory and performance notation

Core Idea

Siteswap, ladder, causal, state, beat-map, and related notations encode different carriers and can support pattern validity tests, transformations, synchronization, and discovery. A convention maps timed performance events and hand-object relations to symbols or graphical paths; syntactic rules constrain legal sequences and a decoder reconstructs the intended pattern. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

The load-bearing residual is not the broad topic of juggling theory and performance notation. It is the domain-specific identity determined by the juggling mode and objects, time discretization, hand and body indexing, throw-height or trajectory semantics, crossing and multiplex rules, start state, periodicity, validity test, and notation dialect are explicit.

Scope of Application

Juggling notation belongs to juggling theory and performance notation and is useful where the analyst can specify the typed juggling theory and performance notation carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, then evaluate the juggling mode and objects, time discretization, hand and body indexing, throw-height or trajectory semantics, crossing and multiplex rules, start state, periodicity, validity test, and notation dialect are explicit. The scope is broad within that domain but bounded by the need for the juggling mode and objects, time discretization, hand and body indexing, throw-height or trajectory semantics, crossing and multiplex rules, start state, periodicity, validity test, and notation dialect are explicit.

Clarity

The abstraction clarifies a crowded vocabulary by making the juggling mode and objects, time discretization, hand and body indexing, throw-height or trajectory semantics, crossing and multiplex rules, start state, periodicity, validity test, and notation dialect are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test.

Manages Complexity

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Juggling notation. Juggling notation compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning

  1. Identify the carrier. State what the elements, states, objects, or observations are: the typed juggling theory and performance notation carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express the juggling mode and objects, time discretization, hand and body indexing, throw-height or trajectory semantics, crossing and multiplex rules, start state, periodicity, validity test, and notation dialect are explicit independently of one notation or implementation.

Knowledge Transfer

Knowledge transfers strongly among subfields of juggling theory and performance notation because they reuse the typed juggling theory and performance notation carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, A convention maps timed performance events and hand-object relations to symbols or graphical paths; syntactic rules constrain legal sequences and a decoder reconstructs the intended pattern., and type the carrier, state every parameter and convention in the definition, test that the juggling mode and objects, time discretization, hand and body indexing, throw-height or trajectory semantics, crossing and multiplex rules, start state, periodicity, validity test, and notation dialect are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions

Local relationship map for Juggling notationParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Juggling notationDOMAINPrime abstraction: Symbolic Representation — is a kind ofSymbolicRepresentationPRIME

Current abstraction Juggling notation Domain-specific

Parents (1) — more general patterns this builds on

  • Juggling notation is a kind of Symbolic Representation Prime

    The proposed strict upward parent is prime:symbolic_representation.

Hierarchy path (1) — routes to 1 parentless root

Neighborhood in Abstraction Space

Juggling notation sits in a moderately populated region (59th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Compiler Representations & Nested Control (7 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08