SLOTS

Handlers by woven slot. Hand-rolled copy-on-write, not ConcurrentHashMap / CopyOnWriteArrayList / AtomicReferenceArray: each puts a class — and a hash of the key with it — on the path EVERY patch dispatches through, so patching that one class would break patches its installer never wrote. A volatile array read names none of them.

Slots are never reused. Advice a failed unweave left behind keeps firing, and a recycled slot would hand it to whoever took the index next; burned, it reads null and no-ops. So this grows with installs ever made — each of which costs a stop-the-world retransform, which is what bounds it.