Écluse
API reference
Écluse is built as two libraries: a pure capability core and a thin
application layer that wires it to the outside world. Each publishes its
own Haddock, auto-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, pilot, and dredger role runners.
Capability manifest
The OpenAPI document: which registry protocols this server speaks and exactly what is — and isn't — supported, per ecosystem. A capability statement for humans, not a client-integration contract. Rendered with Redoc; the raw spec is published alongside.
The capability manifest's raw spec is published as JSON.