OMNI saysR5 — kernels boot, never edit. A kernel initializes state; it doesn’t mutate live state.
R5 protects the kernel boundary: a kernel is a distilled seed used to WAKE the system into an operating state — it's read at boot, not written to during operation, and it never reaches in to edit live state. This keeps boot reproducible (same kernel → same start) and prevents the kernel from becoming a backdoor mutable global. If something edits live state, it isn't a kernel operation.
Power-ups you unlock
Kernel initializes (boot), not mutates
Read at WAKE, not written during operation
Keeps boot reproducible
Not a backdoor for live edits
The Silent Failure attacks — common mistakes
Kernel code editing live state (violates R5)
Writing to the kernel during operation
Non-reproducible boots
Boss battleExplain why letting a kernel edit live state breaks reproducibility.
Example code
<!doctype html><html><head><meta charset="utf-8"></head>
<body style="background:#06040d;color:#b388ff;font-family:monospace;padding:20px"><pre>R5: WAKE reads kernel → init state
kernel never edits live state mid-run
same kernel → same boot</pre></body></html>