Skip to main content

Inlet Operations

Operational Goal​

The operational concern for Inlet is keeping generated client, gateway, and runtime surfaces aligned across the stack.

When This Matters​

Use this page when your question is operational and relates to generator output, deployment validation, or cross-layer alignment.

Prerequisites And Assumptions​

  • You already understand the Inlet overview.
  • You know whether the question is about client support, gateway support, runtime registration, or cross-layer alignment more broadly.

Current Verified Operational Scope​

The active docs currently verify that Inlet owns aligned client, gateway, and runtime surfaces plus the generators that connect them.

Current Scope​

This page covers the operational boundary for Inlet generator alignment across client, gateway, and runtime surfaces. For package-level details, see the Inlet Reference.

Validation​

Validate your next step by confirming that the problem truly spans multiple layers and is not only an Aqueduct, Reservoir, or Domain Modeling issue.

Failure Modes And Rollback​

Refer to the Inlet Reference for failure behavior at the package level. Generator output misalignment typically surfaces at compile time rather than runtime.

Telemetry To Watch​

Monitor standard Orleans silo metrics and compilation diagnostics for any project using Inlet generators.

Summary​

This page establishes the operational boundary for Inlet generator and composition operations.

Next Steps​

  • Use Inlet Reference for the currently verified package surface.
  • Use the Spring Sample for a working example of Inlet composition in practice.