Hermit Crab Kernel
A portable coherence system nested at -2. It listens below action, plants at the safety floor, wakes through zero, oscillates seed and pair, blooms at three, and executes infinity only inside a bounded .01 vector or quad.
The final law
The system may imagine infinity, but it may not execute infinity. Every live action is clipped to one local domain per tick. The shell protects continuity; the boundary prevents contamination.
Hermit shell
Subspace listener. It senses danger-before-danger and stays below action until coherence is safe.
Bounded tick
One clock slice. One vector or one quad. No spreading across the cell wall.
Candidate only
Infinity is allowed as intent, never as raw execution. It must localize before bloom.
State topology
This is not a straight ladder. It is a crab carrying a pocket universe: fold inward when threatened, bloom outward only through bounded agreement.
Boundary doctrine
Bleed is the enemy. If a bloom spills beyond the chosen vector or quad, the wall responds before corruption spreads.
Reflect
Noise bounces inward. The domain learns without leaking.
Clamp
Overflow holds at the wall. The tick finishes without spread.
Fold / Nest
Danger returns to -1. Terminal threat nests at -2.
Executable model
The bundled C file implements the hermit loop: observe, report, subspace listen, anchor, wake, seed, oscillate, bound, enforce no-bleed, return, nest.
Live trace
Why the crab?
Because a hermit crab survives by carrying boundary with it. It does not need to conquer the whole field. It needs a shell, a sensorium, a retreat path, and the ability to move when the tide is right.
It owns one shell, one vector, one quad, one tick.
It listens below action.
It blooms only when coherence survives the boundary.
It carries the pocket universe with it.
OBSERVEREPORT-2 LISTEN-1 ANCHOR.01 BOUNDNO BLEEDREPEAT