API reference
Écluse is built as three libraries: a pure capability core, an effectful runtime edge, and a
thin composition shell. Each publishes its own Haddock, generated from main.
ecluse-core
The capability core: the registry protocol, the rules engine, the queue and credential handles, version and integrity, and the request pipeline. It names no backend and reads no environment.
ecluse-runtime
The effectful edge: the OpenTelemetry SDK and OTLP export, the warp server binding, the log scribes, and the cloud adapters (SQS, CodeArtifact, and S3) that implement the core's handles.
ecluse
The composition shell: the run entry point, configuration loading and
resolution, the composition root that assembles the runtime, and the proxy and pilot role
runners.
Protocol support
Which registry protocols this server speaks, and exactly what is supported and what is not, per ecosystem. The page renders from the OpenAPI document the server publishes. A statement for humans, not a client-integration contract.