Edge Gateway

conduvia-edge-gateway — The synchronous policy intercept at the platform boundary. Every request passes through this layer. Binary decision: admit or reject.

Layer 1 — Edge

conduvia-edge-gateway

The Edge Gateway is the first contact point for all platform traffic. It binds conduvia-policy-core to the chosen edge technology (Spring Cloud Gateway or Envoy adapter). All 10 validation steps execute here for synchronous admission. For async traffic, admitted messages are published to Kafka for downstream processing by Workers.

Full architecture reference →

Governed ingress for all platform traffic
Routes requests through the 10-step validation chain
Short-circuits on first validation failure
Assigns correlation-id if not present
Propagates traceparent (W3C Trace Context)
Supports both sync (direct forward) and async (Kafka publish) modes
Shaped platform errors — no boundary mechanics leak