docs: PROBE-SPRITE-REPLAY spec — x265 I/P/B grammar over HHTL sprites + helix motion; two standing corrections#247
Conversation
…+ helix motion) + two standing corrections New plan x265-sprite-replay-probe-v1.md (operator-directed, crawl-first scope): moving object = HHTL-anchored Gaussian-splat sprite with a helix direction code as the motion primitive, mapped onto the x265 GOP grammar — I = splat set at anchor; P = ONE helix code per sprite (object-level motion replacing per-block MV search, x265's dominant encode cost); B = parametric interpolation along the helical path. Explicitly NOT H.268 and NOT x265 bit-parity; CPU/wasm carries bit-exactness (sprite states from helix codes, pinned math), wgpu is render-grade per C5/C9. The minimal wgpu harness doubles as PROBE-GPU-LUT's missing harness. §5 probe-queue row added with pass/ KILL bands (KILL = helix object-motion collapses into a dense per-splat MV field). Standing corrections folded (flagged in the prior round): - §10(i) honesty amendment: the 192B/3-cache-line tile claim is fully honest only under the analytic Fisher-z canon (materialized 256^2 u16 = 128KB, L2-resident not L1D); analytic drops table residency to 8B and rail reads become |delta-i8| arithmetic. - PROBE-WH-MAG-2 deferral-condition amendment: the Skip/Merge/Delta/ Escape mode grammar already IS the per-tile escape tier (analog of classify_rows_by_lfd Passthrough; shader analog = FailureTicket); WH-MAG-2 = WH under the mode grammar. Blackboard entry appended. Knowledge-doc suite green (117/117). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01K3RyLEbuNSHxxB3NTTrGki
|
Warning Review limit reached
Next review available in: 43 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_1d06203e-642d-4c6f-91b2-cb654f6e8a65) |
2 participants
Summary
Operator-directed next amortization, spec'd crawl-first (plan
x265-sprite-replay-probe-v1.md+ §5 probe-queue row + blackboard):Verification
E-SPRITE-IPB-HELIX-1(companion PR).🤖 Generated with Claude Code
https://claude.ai/code/session_01K3RyLEbuNSHxxB3NTTrGki
Generated by Claude Code