@mavbozo the underlying implementation is intended to work with an Interceptor record as opposed to implementations that satisfy IntoInterceptor. The intent is to minimize checks at the time of execution. I consider the ability to enqueue things that implement IntoInterceptor but are not an Interceptor record to be unintended. It’s appropriate to use the io.pedestal.interceptor/interceptor constructor when creating interceptors.