If you took these systems over from me tonight

Live product (employment)

You should know

• Everything here is self-reported; the code and raw data are private.
• Production ran on a single node, and backups arrived in August 2026.
• The load test is one run from one machine, and it missed two of its own targets.
• The incident fixes were still being rolled out when my work ended.

Where this comes from

Open source · public alpha

You should know

• Validated on six held-out tasks, with one model, on one machine. It shows no proven advantage over the same model run without BoundedCode.
• macOS and Windows are experimental, and some test packages fail there.
• Frontier escalation is implemented and tested against a fake, but it has not been shown to improve outcomes.

Where this comes from

Development environment · not launched

You should know

• Not launched, so there are no usage figures, and nothing here has served real players.
• The deployment workflows build and deploy but do not run the tests.
• The preview uses the generator's default settings and its fixed fallback for win probability, because it ran without the production database.
• The preview's market data is Dukascopy's (EURUSD, February 2019; BTCUSD, February 2023).

Where this comes from

Live product

You should know

• Deploys are started by hand and do not run the test suites first.
• I did not load-test the hardening changes; the repository's load scripts are the other engineer's.
• No usage or revenue figures are published.

Where this comes from

Live · open source · collecting since Oct 2026

You should know

• The site is small: production measurements describe little traffic, so intervals are wide.
• The origin view is reported by the system it describes, and cannot see failures before nginx.
• The external probe samples every 5 minutes from GitHub's network; outages between runs are not observed, and GitHub may delay or skip runs.
• Signatures prove which workflow published which bytes; they do not prove the observations.

Where this comes from

Live

You should know

• One host: a deploy restarts the containers, and there is no failover.
• Visitor analytics are private (self-hosted, first-party, no cookies; ADR-0018) and never published, so there are no public traffic figures.
• The repository is private; the pipeline is described here, not published.

Where this comes from

Prototype · dry-run only

You should know

• A prototype with a squashed history; not used for real sending.
• Known gaps are documented in the project: some internal services accept any caller on their network, several services share a database role, and there is no TLS inside Docker.
• The model comparison is small, single-run and not like for like (see the notes under the table).

Where this comes from

Design only · not implemented

You should know

• Design only; no prototype, no tests, no measurements.
• The review was mine, not an external one.

Where this comes from