Twelve-factor style services read their configuration from the environment, and environment values are always text. A production service converts them once, at startup, into typed settings, and refuses to start when something is missing or malformed. That turns a crash at 3 a.m. into a clear message during deploy.
This lesson builds that layer. You convert text into integers, floats, flags and lists with the edge cases that bite: "false" is truthy as text, list values carry stray spaces and empty items. You collect every problem instead of stopping at the first, combine defaults, a profile such as dev or prod and per-deploy overrides in a fixed order, and enforce what production requires.
Finally you redact the settings before logging them, including a password hidden inside a database URL. Each task receives the schema and environment as JSON.
Out: (True, False). Only an explicit comparison reads a flag correctly.