config-conventions

How do I enforce YAML configuration defaults in NeMo-RL? Enforce YAML configuration defaults in NeMo-RL by making YAML the single source of truth, preventing hardcoded values in code, and ensuring runtime behavior remains explicit and user-controlled through mandatory defaults pointers in recipe YAMLs.

Why should configuration defaults be defined in YAML instead of Python code? Configuration defaults should be defined in YAML to prevent hidden or inconsistent values in NeMo-RL. This approach ensures runtime behavior is explicit, user-controlled, and reviewed correctly, avoiding magic fallback values in function parameters.

What is the best way to handle NotRequired TypedDict fields in policy config schemas? Handle NotRequired TypedDict fields in policy config schemas by treating absence as meaningful rather than masking it with magic fallback values. You must use presence checks to ensure optional config behavior remains explicit.

How do I keep recipe YAML files minimal while documenting configuration defaults? Keep recipe YAML files minimal by inheriting defaults from exemplar YAMLs via a required defaults pointer. Exemplar YAMLs define and document the defaults, while recipe YAMLs remain concise by referencing this single source of truth.

What are common forbidden patterns that leak configuration defaults into code? Common forbidden patterns that leak configuration defaults include using dictionary get methods with hardcoded fallbacks like get(..., "bfloat16") or setting function parameters to default config values. These patterns mask explicit runtime behavior and reduce review quality.