EXPcalibur guide
What the two saved CLASSIC binaries show. CLASSIC apex: what changed in the saved binary CLASSIC apex: what changed in the saved binary WHAT THE CLASSIC APEX README DESCRIBES One apex region, several readings Changed code later runs (PHOENIX). An operand byte also runs (JANUS). A computed value chooses a jump (VECTOR). Apex response inside the bot The VM computes an economy reply. The host still checks whether each chain counts. THE PRESERVED BEFORE / AFTER COMPARISON Predecessor Seven accepted chains. Its exact construction is not saved. Keff = 7. CLASSIC apex The same seven, plus LOCKSMITH. Image and stack roles overlap in guest memory. Keff = 8. one additional chain The extra chain affects limited power after its host check passes and its meter fills. A pilot still needs hits, drops and pickups; the exact original pilot source is not saved. We know the chain counts. We do not know if both bots use the same bytes. The apex README describes one code region with several uses and a program that calculates economy replies. The earlier bot earns seven chains. Its exact byte method is unknown. The larger apex adds LOCKSMITH.