🔦How to Read This Spec (Flags & Defaults)
"Implemented" and "enabled by default" are different things. A feature whose flag defaults to OFF is not running in production.
This site distinguishes “implemented” from “enabled by default”. Even when the feature map
says done, a feature whose flag defaults to OFF is not running in production. That’s why each
feature’s note states its default (e.g. notify_slack_enabled=False (off by default)).
Example: the retention sweeper is implemented, but actual deletion is impossible in code
(F1 forces dry-run — even if settings ask for real deletion, nothing is removed; unlocking that is
F2’s single-point change). Recording (the Realtime path’s recording_enabled) and notifications
(every notify_*_enabled channel) also default to OFF — the word “done” alone doesn’t mean
calls are being recorded or Slack messages are being sent.
The policy: “if the catalog says 4WD, it also says the switch ships in the OFF position.” It keeps readers — internal and partners — from misreading what the live system actually does. Whether a feature exists, and whether it is currently on, are only both communicated when they are written on separate lines.