Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Glossary

Glossary of names used across this guide. Bold entries are cross-cutting domain terms registered in CONTEXT-MAP.md. Plain-text entries are foundational primitives defined in their owning crate's CONTEXT.md. The bold list is alphabetical. Each entry links its canonical guide page and the decision or crate that defines it.

Cross-cutting terms

  • ArcSwap<TlsAcceptor> — atomic-swap holder for the gRPC TLS acceptor. Each accept loop loads a cert snapshot. HTTP and WS swap certs through RustlsConfig. Hot reload, ADR-0004.
  • Bounded context — behavioral area of camel-core that owns its own domain vocabulary. The CQRS flavor is a per-context decision, never a crate-wide one. Architecture, ADR-0045.
  • Bridged error — consumer failure that a bridge_* path converts into a synthetic error-bearing Exchange through send_and_wait. The route error handler owns the operational signal. Error handling, ADR-0012.
  • CanonicalRouteSpec — versioned minimal route contract that runtime commands, config tooling, and hot-reload consume. v2 adds lifecycle metadata and rejects unsupported fields. Route structure, ADR-0011, ADR-0016.
  • CircuitBreaker — DSL-declared fault tolerance pattern. It compiles into error-handling middleware, not a Pipeline Step. Circuit breaker, ADR-0019.
  • ConsumerStopping — CamelError variant for producer poll_ready shutdown. It signals that the producer channel is closing. Distinct from Stop EIP. Error handling, ADR-0024.
  • Credential redaction boundary — types that hold passwords, tokens, keys, or credential bytes must not expose those values through Debug or general-purpose Serialize. Use manual redaction or a tested wrapper. Auth, ADR-0051.
  • Degraded — health state meaning the component can still process Exchanges: HTTP 200 on /readyz, pod Ready. Unhealthy returns HTTP 503 and marks the pod NotReady. Health.
  • EnrichmentStrategy — strategy that merges the original Exchange with the polled or enriched Exchange in the enrich and pollEnrich verbs. Distinct from the EIP-22 AggregateStrategyDef family. Content enricher, ADR-0015.
  • ErrorHandler — DSL declaration (ErrorHandler, OnException) that compiles into ErrorHandlerConfig and ExceptionPolicy at runtime. Error handling, ADR-0019.
  • Exchange-data trust boundary — operator config is trusted. Exchange data (headers, body, properties, correlation keys) is untrusted and adversary-controlled. Such data must not reach a control-plane action, an unbounded decision, or an executable sink without validation. Planes, ADR-0032.
  • ExceptionDisposition — enum (Propagate | Handled | Continued) that replaces handled: bool. Propagate returns the error upstream. Handled ends the route normally. Continued clears the error and advances. Error handling, ADR-0019.
  • ForcedHealthFailure — when a Consumer crashes, HealthCheckRegistry pins the route's health entry to Unhealthy through force_unhealthy_for_route() until a ConsumerRestart replaces it with a live probe. Health.
  • Handler-contract boundary — conceptual line between an error emitter and the route element that owns the failure's operational signal. Emitters inside the boundary log at warn! or below. Error handling, ADR-0012.
  • LlmProvider — trait abstraction over LLM backends (OpenAI, Ollama, Mock). Camel-shaped, not siumai-shaped. All siumai imports stay in the adapter. Components, ADR-0020.
  • Message — body and headers container inside an Exchange. exchange.input is the incoming Message. exchange.output is the optional reply Message. Exchange & Message.
  • Module-discipline ceiling — camel-core 1.0 policy. Clean Architecture rings are enforced by module paths and boundary tests, not by crate isolation. A crate split stays a post-1.0 option. Architecture, ADR-0045.
  • OpenAPI code-first generation — rest: AST compiled into an OpenAPI 3.0.3 document via camel openapi generate or camel_dsl::openapi::generate_openapi(). YAML DSL.
  • OutcomePipeline — internal trait one layer above Tower for structural EIP sub-pipelines. It returns PipelineOutcome directly so Stopped(ex) keeps Exchange state intact. Error handling, ADR-0025.
  • OutcomeSegment — wrapper struct over Box<dyn OutcomePipeline> with tracing and metrics hooks. It is the payload of CompiledStep::Segment. Error handling, ADR-0025.
  • PipelineOutcome — enum (Completed(Exchange) | Stopped(Exchange) | Failed(CamelError)) produced by the pipeline executor one layer above Tower. Stop EIP is successful control flow, not an error. Error handling, ADR-0024.
  • PollingConsumer — pull-based adapter created on demand from an Endpoint. It delivers one Exchange per call. Used by pollEnrich and the WASM camel_poll host function. Poll enrich, ADR-0015.
  • ProviderMap — HashMap<String, Arc<dyn LlmProvider>> owned by LlmComponent and resolved by name from config. Not a global registry. Components, ADR-0020.
  • REST DSL — declarative rest: YAML/JSON blocks that lower to http: consumer routes with JSON binding, path templates, and optional schema validation. YAML DSL.
  • RetryableStep — object-safe trait that unifies BoxProcessor and OutcomeSegment for RouteErrorHandler::retry_step. One retry path serves both Tower processors and outcome-aware segments. Error handling, ADR-0019.
  • Route lifecycle compensation — control-plane recovery rule. If a lifecycle side effect fails after durable intent changed, the Runtime marks the Route Failed. It reconciles the projection and publishes failure events instead of rolling history back. Routes & pipelines, ADR-0018.
  • RouteChannelService — service that chains Security, CircuitBreaker (before_call), Pipeline (run_steps), and CircuitBreaker (after_result). Built only when an errorHandler is configured. Error handling, ADR-0019.
  • RouteErrorHandler — trait injected into the pipeline with four async methods (match_policy, retry_step, handle_step, handle_boundary). The returned disposition drives the loop. Error handling, ADR-0019.
  • SecurityPolicy — route-level authorization contract applied before normal Route Steps run. Denials return Unauthorized into route error handling. Auth, ADR-0010.
  • Security defaults & fail-closed startup validation — five-disposition policy (Intent-Violation, Intent-Declaration, Require-Explicit-Choice, Safety-Primitive, Untrusted-Data-Validation) enforced by one fail-closed startup phase. Each hardened default has its own per-item flag. Auth, ADR-0033.
  • ServerTlsSource — shared cert-file source struct (cert_path, key_path, client_ca_path) used by the gRPC, HTTP, and WS server components for initial TLS setup and reload. Hot reload.
  • Side-effect failure — consumer failure that occurs after a successful send_and_wait, for example SQL onConsume post-processing. No route-level handler runs for it. The emitter owns the signal. Error handling, ADR-0012.
  • Starting Route — externally observable Route lifecycle state between accepted start intent and confirmed Consumer or Pipeline side effect. Operators can see Starting in RouteStatusProjection. Routes & pipelines, ADR-0018.
  • StopSegment — outcome-aware analog of CompiledStep::Stop for structural EIP sub-pipelines. It always returns PipelineOutcome::Stopped(ex). Stop, ADR-0024.
  • Supervision — route-level crash recovery. A Consumer task failure sends a CrashNotification. The RuntimeBus records the route as Failed. An optional restart policy recreates the whole Route with backoff. Error handling, ADR-0007.
  • Synchronous-projection CQRS — CQRS variant where the read-side projection updates inside the same optimistic-versioned UnitOfWork as the command. This gives strong read-model freshness with no projection lag. Planes, ADR-0002.
  • System-broken error — failure that indicates corruption, a panic equivalent, or a contract violation. Always logged at error!, never downgraded. Error handling, ADR-0012.
  • Template rendering language — language SPI implementation that renders templates (HTML, JSON, prompts) against Exchange data. Phase 1 covers inline templates. Phase 2 adds external file loading and hot-reload. MiniJinja, ADR-0047.
  • TLS cert hot-reload — platform-wide inbound TLS certificate rotation via RuntimeCommand::ReloadTlsCerts { scheme, host, port }. The reload is idempotent and skips the journal. Hot reload, ADR-0004.
  • TlsReloadHandler — trait that each TLS-terminating component implements (matches(scheme, host, port) plus async reload()). Components register it lazily in TlsReloadRegistry::global(). Hot reload.
  • Vertical slice — unit of decomposition for camel-core. Each bounded context is a self-contained slice with its own domain/application/ports/adapters layout, not a shared technical layer. Architecture, ADR-0045.
  • WASM sandbox capability posture — per-world grant model across Camel host functions and WASI interfaces. Camel calls use explicit scheme allowlists. WASI uses selective registration, not full-linker registration with runtime denial. Extending, ADR-0050.

Foundational primitives

Crate-local building blocks. The owning crate's CONTEXT.md is the canonical definition. These terms are intentionally not bold, so they stay out of the lint-glossary vocabulary check.