[Enhancement]: 🌟 NeMo Relay x WisePick - Runtime Contracts & Replayable Routing Semantics

[w2jmoe]

Affected area

Middleware or guardrails

Problem or opportunity

Hi 👋

Been reading through NeMo Relay recently — it really feels like you're building a framework-independent runtime contract layer.

Especially around:

• hierarchical scopes
• lifecycle events
• middleware semantics
• observability streams
• adaptive runtime behavior

Those abstractions feel very infrastructure-grade ✨

WisePick has been exploring the semantic boundary of a dedicated capability routing layer.

One question we've been thinking about a lot lately is:

routing feedback shouldn’t reset to zero every runtime

Meaning routing itself may eventually need to become:

• observable
• replayable
• inspectable
• benchmarkable

as part of runtime artifacts.

WisePick is currently focused more on:

• routing reduction
• replayable routing
• bounded determinism
• execution efficacy feedback

rather than orchestration or governance ownership.

Reading NeMo Relay’s runtime lifecycle abstractions made the ecosystem adjacency feel surprisingly interesting 👀

Particularly curious whether future runtime ecosystems may eventually treat:
“routing state”
as part of the runtime lifecycle surface itself.

Very cool work — starred 😊

Proposed enhancement

.

Runtime contract and binding impact

.

Alternatives considered

.

Acceptance criteria

.

[willkill07]

Routing itself could be driven/shipped via a NeMo Relay plugin.

Where the plugin:

• holds onto some internal state
• ships its own configuration
• ships its own self-standing router implementation
• registers its own subscriber to listen to NeMo Relay Events
• registers its own LLM execution intercept to change the routing behavior