A Haskell core in a modern project
A modern service is rarely one language. The part with the rules in it is written once, carefully, and the parts around it, the HTTP layer, the scripts and the tests, are written in whatever the team already runs. These pages take one small core, a pricing function over a line protocol, and put three layers in front of it: an executable, a Python HTTP service and a shared library, with the tests and the image that go with each.
The core is pure Haskell with no package outside GHC's own, so the whole set builds in an image with no network. Every page shows what was run here and says what was not: the service was started and called, the library was built and loaded, the tests were run, and the Dockerfile is marked as not built because this container has no Docker.
The pages are independent of the Haskell course. The lessons behind them are standard input and output, calling Haskell from Python and a Cabal project, offline.
The programs were built with GHC 9.10.3 and run with Python 3.14.10, on Alpine Linux 3.24.3 (x86_64) in a Docker container with 4 CPUs.