NVIDIA Maintain Adaptive Surfaces
Use this skill when changing adaptive config schema, built-in sections, shared plugin lifecycle, plugin registration, or binding-native helper APIs.
Public Boundary
The stable adaptive boundary is the config document plus the shared plugin lifecycle:
- Config types and policies
- Built-in adaptive section helpers
- Plugin registration and composition
- Plugin lifecycle
- Reports and diagnostics
There is no separate public adaptive runtime handle.
See docs/configure-plugins/adaptive/configuration.mdx and
docs/configure-plugins/about.mdx.
Keep In Sync
crates/adaptive- Shared plugin behavior in core and bindings
- Python adaptive/plugin wrappers in
python/nemo_relay/adaptive.pyandpython/nemo_relay/plugin.py - Go adaptive helpers under
go/nemo_relay/adaptiveplus shared plugin helpers ingo/nemo_relay - Node.js adaptive helpers and plugin wrappers
- Docs and examples that show canonical config shapes
Checklist
- Dynamic config shape still matches the documented canonical model
- Typed helper constructors still map cleanly to the same config document
- Plugin lifecycle is consistent across languages
- Plugin context surfaces remain aligned
- Validation/report behavior remains documented and tested
- Any new component kind has docs, examples, and binding coverage
Validation
- Run adaptive-focused Rust tests
- Run binding tests for every changed adaptive or plugin surface
- Update adaptive docs and any examples in the same branch
References
docs/configure-plugins/adaptive/configuration.mdxdocs/configure-plugins/adaptive/about.mdxdocs/configure-plugins/adaptive/acg.mdxdocs/configure-plugins/adaptive/adaptive-hints.mdxdocs/build-plugins/about.mdxdocs/build-plugins/configuration-and-validation.mdx