Archived
feat!: a generic core, and Kalshi through it
The orchestrator, the connection loop and the book thread's shell move to src/core/, generic over an Exchange and its loss rule (ADR 0004). Polymarket runs through it unchanged. Kalshi joins: a signed handshake (KALSHI_KEY_ID_FILE, KALSHI_PRIVATE_KEY_FILE), a reconnect on a skipped sequence number, first one wins by clock and rank, and its market listing with markets tracked from three hours before they open. Breaking: the exchange is now the first argument, `engineering-challenge <polymarket|kalshi|kalshi-demo> [OUTPUT]`.
This commit is contained in:
33 files changed
+8150
-1846
No files matched your search
@@ -44,4 +44,5 @@ Trade-off: the routing step 0002 avoided is back, parsing moves into the
|
||||
connection thread, and the book thread's rules get subtler (held changes, a
|
||||
ceiling, a chain declared broken). The design leans on an exchange that lets
|
||||
the same change be recognised across connections: Polymarket's hash does;
|
||||
Kalshi's `clock` looks as if it would (to confirm in M6).
|
||||
on Kalshi a change's `clock` and its rank among the changes of that clock do
|
||||
(recorded in M6, [sprint 06](../../roadmap/06.%20generic%20core%20and%20kalshi.md)).
|
||||
Reference in new issue
Block a user