Conceptual Analysis & Observable Dimensions

1. Scope & Formal Attribution

The implementation provenance rules and permitted public inputs are defined in the Measurement Provenance and Methodology Boundaries page. Third-party artifacts are not used as implementation specifications or calibration oracles.

MotionScore publicly documents an S-to-F grading framework for evaluating animation performance according to rendering characteristics. The following section summarizes the publicly documented concepts referenced from https://score.motion.dev/methodology and does not reproduce MotionScore's internal implementation.

---

2. Publicly Documented Conceptual Classification

[PUBLIC] Documented by MotionScore (score.motion.dev/methodology)

Public documentation on https://score.motion.dev/methodology outlines an S-to-F qualitative hierarchy reflecting how deeply animations disturb the browser's render pipeline:

---

3. Observable Dimensions Under Investigation

[RESEARCH] SoraLabs Investigation & Research Areas

To evaluate web motion rigorously without assuming unpublished third-party scoring formulas, SoraLabs references the qualitative hierarchy on score.motion.dev/methodology while grounding its quantitative engine in four technical research dimensions:

1. Animation Execution Pipeline:

   • [PUBLIC] Qualitative distinction between compositor, paint, and layout operations as documented on score.motion.dev/methodology.
   • [OBSERVED] Observable CDP traces (Animation.animationStarted, style recalculations, paint rects).
   • [IMPLEMENTATION] Calibrated Blink pipeline stage cost vector ($\mathcal{P}_{\text{pipeline}}$: Compositor = 0, CSS Variable = 15, Paint = 20, Layout = 50), bounded per-animation (max 75 pts penalty) and aggregated via Amdahl bottleneck coupling ($0.3 \cdot \text{Worst} + 0.7 \cdot \text{Mean}$).

2. Scroll-Driven Mechanics:

   • [PUBLIC] Distinction between off-thread declarative scroll timelines and synchronous script listeners.
   • [OBSERVED] Main-thread event latency, passive flag compliance, and animation frame synchronization.
   • [IMPLEMENTATION] Logarithmic listener contention saturation ($\mathcal{P}_{\text{contention}} = \min(30,\, 7 \times \log_2(1 + N))$), non-passive blocking stall penalty ($+15$ pts), and NIST P75 concurrency interpolation.

3. Layout Thrashing & Mutation Patterns:

   • [PUBLIC] Concept of interleaved read/write mutations causing pipeline stalls.
   • [OBSERVED] Chromium Blink Document::UpdateStyleAndLayoutTree call stacks in Performance profiles and forced reflow getters (offsetHeight, getBoundingClientRect).
   • [IMPLEMENTATION] Calibrated base penalty ($\mathcal{B}_{\text{layout}} = 5$, $\mathcal{B}_{\text{style}} = 2$), consecutive reflow burst detection via $O(N)$ Hash-Set clustering with 8-frame budget exhaustion ($2.5\times$), invalidation scope factor ($1.5\times$ for root containers like html/body/#root), per-selector intra-frame chain repetition and distinct selector saturation, and framework hydration mount phase allowance ($\le 15$ pts).

4. GPU Texture & Memory Pressure:

   • [OBSERVED] Compositor layer quad bounds (LayerTree.layerTreeDidChange), layer counts, and DPR-aware texture and layer estimates.
   • [IMPLEMENTATION] Theoretical raw uncompressed RGBA8888 texture estimate ($\mathcal{M}_{\text{raw}} = W \times H \times 4 \times \text{DPR}^2$) alongside Chromium cc::TileManager discrete $256 \times 256$ tile pooling with a pre-raster lookahead horizon ($1.5\times$ viewport), evaluated via piecewise operational band interpolation against power-of-two GPU memory pools.

---

4. Contextual Modifiers & Perception Boundaries

Real-world execution cost diverges substantially based on geometric and temporal context:

• Surface Area Scaling:
  • [OBSERVED] Large raster invalidations bottleneck GPU fragment fillrate. Repainting a full-screen background is vastly heavier than repainting an icon.
  • [IMPLEMENTATION] Clamped paint surface scaling ratio ($\mathcal{S}_{\text{paint}} \in [0.25,\, 4.0]$) relative to a $10\%$ baseline interactive component viewport footprint.
• Visibility & Offscreen Culling:
  • [OBSERVED] Offscreen elements ticking animations consume main-thread execution time and power unnecessarily.
  • [IMPLEMENTATION] Selective offscreen mutation penalty ($\mathcal{M}_{\text{offscreen}} = 1.5$) targeting Layout and Paint modifications, while leaving off-thread compositor animations unpenalized ($1.0\times$) to prevent double-penalization with GPU VRAM auditing.
• Timing, Concurrency, and Frame Budgets:
  • [RESEARCH] $16.67\text{ms}$ ($60\text{Hz}$) and $8.33\text{ms}$ ($120\text{Hz}$) are used as reference frame budgets; actual runtime budgets depend dynamically on the display hardware's native refresh rate (ProMotion, $144\text{Hz}$, variable refresh rate).
  • [IMPLEMENTATION] Google RAIL instantaneous perception duration discount factor ($\mathcal{D}_{\text{time}} = \text{clamp}(0.25,\, 1.0,\, \frac{\text{Duration}_{\text{ms}}}{100})$ for micro-interactions $< 100\text{ms}$).
  • [IMPLEMENTATION] Effective concurrency balancing sustained load against peak bursts ($\mathcal{C}_{\text{effective}} = \text{round}(0.6 \cdot \bar{C}_{\text{mean}} + 0.4 \cdot C_{\text{peak}})$) alongside NIST $75^{\text{th}}$ percentile distribution mapping.