NeMo Guardrails 0.24

Apply the Python 3 prompt first. These rules target the NeMo Guardrails 0.24 line as implemented by nemoguardrails 0.24.1 on Python 3.10–3.13, including LLMRails, IORails, Colang, custom actions, and the library's API servers.

Trusted configuration and runtime

• Load RailsConfig.from_path() and import_paths only from reviewed application-controlled directories. Treat YAML, Colang, prompt templates, config.py, actions.py, and actions/ as executable policy; initialization imports Python code, including config.py from combined configurations in 0.24.1.
• Set colang_version deliberately and initialize every production configuration combination before accepting traffic. Exercise each mandatory rail during readiness checks: successful configuration parsing does not prove that lazily imported detectors, credentials, models, or custom actions work.
• Use Python 3.10–3.12 when relying on the sdd or all extra to install Presidio; those extras omit Presidio on Python 3.13. Verify the required spaCy model and recognizers are installed before enabling sensitive-data rails.

Engine selection and rail decisions

• Use LLMRails for dialog, retrieval, custom execution actions, or Colang 2.x. When relying on IORails-specific tool validation, construct Guardrails(config, require_iorails=True) and verify compatibility with IORails.unsupported_reason(). Automatic fallback to LLMRails must not silently remove required controls.
• Populate the required rails.input.flows, rails.output.flows, retrieval flows, and tool flows explicitly. Empty flow lists provide