Fr0zkaandClaude Opus 5 58bdfb32de docs: WORK-NEXT.md -- the queue after Sol's read-only audit
Ordered by importance then size. Sol (read-only, xhigh) audited experimental @ aa62971
against main and delivered the two-sentence diagnosis this queue is built on:

  "The operator abstraction leaked into the innermost loop, and streaming treats
   'work submitted/applied' as 'safe to stand on.'"

Two corrections it made to us, both recorded in the doc:

- The fall-through is NOT a removed correctness barrier. main has no spawn gate
  either, marks tiles loaded before applying, and collides only LOD0. It was fast
  enough to hide the race. The owner's evidence was real; the inference was not.
- The loop inversion did not recover the 8x because it traded PER-SAMPLE
  short-circuiting (~70% of deep-solid samples skipped the cave suite) for per-block
  pruning. The fix is lowering the operator graph into a fused evaluator, not more
  dispatch removal.

It also found that RMC cooks collision ASYNCHRONOUSLY and we never record
cook-complete -- apply_s ends at submission, so nothing we have ever measured says
when physics could actually collide.

Reading Plugins/RealtimeMeshComponent is now permitted for item 1, READ ONLY, by the
owner's decision.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012aheo2crrZmHuYtPpdY2Cb
2026-09-11 22:01:47 +02:00
S
Description
No description provided
107 MiB
0 Stars 1 Watchers 0 Forks
Languages
C++ 97.6%
C 2.3%
C# 0.1%