nirs4all.pipeline.keyword_registry module
Machine-readable lifecycle keyword and effect registry.
This module is deliberately descriptive: pipeline parsing, validation, and
execution do not import it. Documentation and downstream presentation layers
can consume get_keyword_registry() without making this registry a second
runtime dispatcher.
The first registry slice focuses on the terms that are easy to confuse while
native DAG tuning and conformal calibration are introduced. planned and
partial are contract states, not promises that a surface already executes.
engine_support keys name the actor whose capability is described:
legacy, dag-ml and dual are execution backends, while optuna
and n4m are optimizer engines. An entry may list both namespaces when a
feature crosses the execution/optimization boundary.