Runtime Settings
Runtime settings control how a generated application starts, connects, stores, observes, and responds to work.
Main Surfaces
| Surface | Examples | Full reference |
|---|---|---|
| Generated orchestrator clients | downstream service locations, client wiring | Orchestrator Client Wiring |
| REST client endpoints | generated REST client base URLs | REST Client Endpoints |
| Pipeline execution | synchronous/background execution mode and worker behavior | Pipeline Execution |
| Telemetry | generated telemetry export and runtime telemetry behavior | Telemetry |
| In-flight probe | operator-facing pause/kill switch | In-flight Probe |
| Health checks | startup/runtime health validation | Startup Health Checks |
| Global defaults | defaults shared across generated components | Global Defaults |
| Circuit protection | global policy, boundary overrides, and runtime scope capability | Circuit Protection |
Design Guidance
Runtime settings should not change the business contract. They should change deployment behavior around an already-generated pipeline:
- where adapters call,
- which providers are selected,
- how work is scheduled,
- how failures are retried or surfaced,
- how telemetry and health are exposed.