Captain Bob, 2026-11-14: "we're supposed to be working on f18 opcode as well as our composed f18 dictionary"; ruled every loop on both, "and an easy revert if opcodes are too granular". - The engine: a hook at retire (exec.h on_retire), as Part A's at call; NULL unless set. test_exec.c. - The mesh: 32 opcode records per node, an opcode window, opcode transitions under L4; at every retired instruction decay at the opcodes' own slope, heat, temperature, the window, the transition; in each cycle all 32 cooled, the opcode window's service, inference on its heat. L8 scores from the words and its gates govern both; the tick stays paced by word calls. The window is now one type for words and opcodes. - The revert: OPCODE_PHYSICS (Kconfig.physics, default y; the kernel's flags) -- 0 and the opcodes are counted and charged to the Stadium as in Phase 1. make -C v4 mesh-boot-noop builds and tests it. - Tests first: test_mesh_boot.c 77 checks as built, 86 with pipelining on, 74 with the revert. - Measured on amd64, back to back: 219 s on, 196 s off (+12% under TCG). Both boots' logs labelled. Not pushed (held to the end of Phase 7). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
Timing comparison, not acceptance evidence (2026-11-14): amd64 with OPCODE_PHYSICS=0 (the revert, #189 Phase 7 ruling 7), booted straight after the same tree with it on. RESULT: PASS in 196 s, against 219 s with opcode compudynamics on: about +12% for the loops at every retired instruction.