How to structure a data job so its inputs are visible, its effects are local, and changes can be checked: dependency injection, contract tests, configuration precedence and validation, and effective-configuration records.
Pass a workflow its reader or publisher from outside, test the dependency contract, and keep fake-adapter evidence separate from real integration behavior.
Check configuration keys, types, ranges, and relationships before work begins, and distinguish a valid setting from a safe destination or correct rule.