Table of Contents
The solution strategy is simple: the render kernel owns the production proof path, and every other surface either feeds it, checks it, or stays outside it. That keeps the runtime story legible even as tooling grows around it.
Core strategy
-
kernel-owned rendering and structured plans
-
manifest and plan hashes as explicit proof material
-
verification anchored in kernel-owned ordering, hashes, and spans
-
notes as governed memory rather than implicit truth
-
scanners as bounded, explicit pipeline stages
-
adapter/oracle retained only for comparison and diagnostics