Sparring Partner, an opponent that learns you out loud
Zed keeps a decayed histogram of every move you commit, per situation —
range band × your stance. It predicts your next attack from that table and
scores every possible answer against the prediction; when two answers land
within 0.3 points, the engine arbitrates with your recorded habits
in the question. The table is exposed in the stats overlay and one button
wipes it.
What decides what
The fight is pure code. Frames, ranges, chip damage,
the meter, the clock — same seed, same fight, bit for bit. Duck slips
under hook and special; jab hits low; block chips to 20%.
Your habits decide zed's read. Every move you commit
lands in a decayed histogram keyed by situation (close/mid × your
stance). Spam jab and zed's prediction converges to jab — measured in
the tests.
The engine arbitrates close calls. When zed's top two
answers score within 0.3 points, that near-tie is a real
choice request with the habit table in the state —
abstention falls back to the habit argmax, and the trace names the rung.
Ring control is a labelled rule. At long range zed
walks in by rule, never by choice — counted as a rule rung, the way the
racer labels traffic.
Honest edges
The engine never picks an answer that didn't near-tie — with the engine
off zed fights on the same habit argmax, marked on the trace.
The learning is yours to inspect: the stats overlay prints the whole
decayed table, and the reset button wipes it mid-fight.
The scoreboard is session-only — close the tab and it is gone. No
server, no accounts, nothing leaves the page.
The bot driver is a seeded, readable baseline — walk in, poke, guard —
not a secret strong solver, and the boxers are drawn procedural, no
sprites loaded.