EXPcalibur guide
Watch a bot request become a checked, short-lived boost. ABYSS: who sends it, who saves it, who uses it ABYSS: who sends it, who saves it, who uses it Read downward. A later row can happen many calls or ticks after the row above. BOT CAN SEND HOST KEEPS AND CHECKS 1 · Request bytes Bot writes a frame and input in guest memory. Saved request Host checks the range and copies the bytes. ↓ later 2 · More work Bot asks the Gate to continue allowed work. Saved machine Owner, resource, paused state, and fuel carry on. ↓ later 3 · Candidate result Inner program finishes or proposes a result. Proof record Host checks the work; only a pass adds a receipt. ↓ later 4 · Power request Bot asks for an attack, survival, or pickup level. Short boost Host checks linked proof and both level limits. THE SHARED ARENA · THIS IS WHERE EXP CAN CHANGE Pilot action + boost Fight → drop Pickup → EXP Copy ≠ proof. Proof ≠ permanent boost. A boost ≠ free EXP. This is the hand-off pattern, not one literal request or a complete exploit trace. Left: what the bot can send. Right: what the host copies or saves. The final row returns to ordinary combat and gem pickup. A copied request, accepted proof, active boost, and EXP are four different things.