Troubleshoot Inlet Scope And Entry-Point Confusion
Symptoms
You started in Inlet, but the question now appears to be only about one subsystem rather than cross-layer alignment.
What This Usually Means
Inlet is the wrong primary entry point when the issue does not actually span client, gateway, and runtime surfaces together.
Probable Causes
- The task belongs to Aqueduct because it is really only about the backplane.
- The task belongs to Reservoir because it is really only about client state.
- The task belongs to Domain Modeling because it is really only about domain behavior.
How To Confirm
- Stay in Inlet only if the primary concern is generated or runtime-aligned behavior across multiple layers.
Resolution
Use How To Choose An Inlet Package Entry Point if the issue still belongs to Inlet. Otherwise switch to the correct subsystem overview.
Verify The Fix
You should be able to describe the issue as cross-layer alignment or as a single-subsystem concern.
Prevention
Start by asking whether the problem spans client, gateway, and runtime together or only one layer.
Summary
Inlet is the correct section only when the composition problem crosses subsystem boundaries.
Next Steps
- Read Inlet Getting Started.
- Move to the specific subsystem overview if the issue is confined to one layer.