Kalshi Demo Environment Support
This post covers the implementation of ADR-015 (Kalshi Demo Environment Support), enabling safe testing with Kalshi's demo API without risking production credentials or capital.
Engineering blog posts documenting intent, decisions, and implementation details.
Each post follows the CLAUDE.md requirement: developer-centric articles explaining the decision-making process with implementation examples.
This post covers the implementation of ADR-015 (Kalshi Demo Environment Support), enabling safe testing with Kalshi's demo API without risking production credentials or capital.
This post covers Phase 1 of ADR-017 (Automated Market Discovery and Matching) - establishing the data types and persistence layer for the discovery system.
This post covers Phase 2 of ADR-017 - implementing the text similarity matching engine that powers automated market discovery between Polymarket and Kalshi.
This post covers Phase 3 of ADR-017 - implementing the API clients that fetch market listings from Polymarket and Kalshi for automated discovery.
This post covers Phase 4 of ADR-017 - the scanner actor for periodic discovery and the safety-critical human approval workflow.
This post covers Phase 5, the final phase of ADR-017 - CLI command integration for the discovery workflow.
Completing the remaining implementation gaps across ADRs 004, 005, 007, and 009 with thread-safe nonce management, risk manager actor, compensation executor, and key rotation support.
How we resolved an ADR naming conflict and established bidirectional traceability between requirements, decisions, and implementation.
How we built infrastructure-as-code with Terraform for deploying our trading system to AWS, including ECS Fargate, Aurora PostgreSQL, and ElastiCache Redis.
How we built a trading control plane with gRPC for programmatic access and Telegram for mobile-friendly monitoring.