EXPcalibur guide
Four checkpoints take a proof track from Entry to Apex. ABYSS: four checkpoints to stronger power ABYSS: four checkpoints to stronger power Each row is one new host-saved proof, not a direct change to EXP. CHECKPOINT WHAT THE BOT ARRANGES WHAT THE HOST ACCEPTS LEVEL LIMIT 01 ENTRY First accepted work Send one 64-byte body and finish its paused Entry work. Read rows and columns; check the saved owner; save Entry proof. 4 02 RIFT This run’s cost trail Make 32 timed SYNCs; recover the run’s root; COMPARE once. Check ordered costs, the root, and Entry; save calibrated proof. 8 03 CHASM Old page, new job Queue a Scratch write before maintenance; run the reused page. Check the stale write and bootstrap work; save dispatch proof. 12 04 APEX The full inner program Patch six audit answers; run the 30-cell module over two calls. Check 505 steps and all six audit answers; save Module proof. 16 THREE POWER TRACKS · THE BOT REPEATS THIS ROUTE FOR EACH ONE SERRATE Sword BASTION Survival + movement TRAWL Gems + pickup Short boost → stronger knight → real fights → collected gems → EXP Read each row left to right: what the bot arranges, what the host must accept, and the highest level that proof step can support. The host saves a new proof after each successful stage. The bottom shows why the bot repeats the route for sword, shield, and gem collection.