The README said the quiet rule holds for the quietest markets (it can't
judge one under 3 changes a minute) and that all four extensions were
done (two of the brief's latency ideas were not tried); LATENCY.md said
the slow recycle was not seen to fire live, two lines after the run where
it did. Limits gains the process going down, the quiet rule's blind
spots and Kalshi's skipped-change case.
CLAUDE.md loses the home network's details and the server's key paths,
of no use to a reader of the public repo.
scripts/test_watch.sh no longer puts a here-document inside `$( )`:
bash 3.2, which is sh on macOS, stopped at an apostrophe there and
scripts/ci.sh ended on a syntax error.
Sprint 08 (roadmap/08. ready to submit.md), the last milestone.
- scripts/watch.sh runs the collector with a live view of its log, stops
cleanly on Ctrl-C, then checks the output (reconcile) and shows one
symbol's book as text (show, a new binary).
- The README for the solution, with the final runs: Polymarket through an
outage it recovered from on its own, Kalshi's demo with two slow
connections recycled.
- From a review of the whole codebase: Kalshi takes RSA keys too
(RSA-PSS-SHA256); a slow Kalshi connection takes the hourly recycle's
next turn, which it nearly never got before; a market tracked again no
longer fails reconcile; Book::add checks for overflow; usage and --help
name the key variables; the first scan says how far it got.
- Tests for every gap the reviews found, an offline run of the whole
orchestrator among them; ShellCheck in CI.
Extension 4. `engineering-challenge latency EXCHANGE OUT.csv` opens 16
connections to the same busy markets and writes every copy of every change;
`scripts/latency/analyse.py` gives each connection's speed, whether it
persists, what keeping the fastest would gain, lateness by address, and lag
with the clock's offset. LATENCY.md writes up four runs: on Polymarket speed
persists but is worth under a millisecond, at the median only; on Kalshi's
demo keeping the fastest pair lowers p99 by 28% and 42%, the threshold
agreed before the runs.
So the collector now recycles a Kalshi connection whose mean lateness stays,
3 minutes running, in the slowest quarter and above twice everyone's, ahead
of its hourly turn. Kalshi's rule measures each duplicate's lateness; the
orchestrator judges once a minute. A duplicate's lag in Polymarket's minute
line is now its "lateness".
Roadmap milestone 7, roadmap/07.