Documentation

A rule policy did not resolve (surfaced by loadConfig).

A configured mount's ecosystem has no adapter, so Écluse cannot serve it.

A mount has no initialised mirror-write provider. Every active mount derives its credential from its mirror target, so this is a safety net, not a reachable state.

The queue URL names a backend this binary cannot run.

An SQS endpoint override (AWS_ENDPOINT_URL_SQS) is set but AWS_REGION is not. An emulator or VPC endpoint carries no region in its host, so the ambient one must scope it.

ECLUSE_QUEUE__URL is set but its shape names no backend this binary knows. Guessing one would send mirror jobs somewhere the operator did not point at. Carries the value.

The configured SQS endpoint override (AWS_ENDPOINT_URL_SQS) is not a parseable endpoint URL. It can carry a credential, so the value stays redacted behind the secret.

The S3 advisory client's endpoint override (AWS_ENDPOINT_URL) is not a parseable endpoint URL. Refused rather than dropped, so a typo never silently dials real AWS.

The eager mint threw, carrying every configured consumer key and the rendered exception.

A mount declares a mirror target, but this build writes nothing for its ecosystem. The mirror could never publish, so the mount is refused rather than booted half-wired.

A publication target has no adapter that can write its ecosystem's protocol.

A publication target is set and the mount declares no first-party namespaces, so the anti-shadowing guard has nothing to enforce and any name could be shadowed.

First-party names have no private authority, so every lookup would return 404.

A static publish credential is set without a verifiable inbound edge (ECLUSE_SERVER__AUTH_TOKEN). An unauthenticated request could otherwise publish as Écluse.

A mount's publication target, at the carried registry, shares a host with the named mount's public upstream. The publisher's relayed credential would reach a public registry.

A mount's publication target is also the named mount's endpoint under the named key, at the carried registry. A publish would be relayed into a role declared for something else.

A mount's mirror target, at the carried registry, shares a host with the named mount's public upstream. Écluse's own mirror-write credential would reach a public registry.

A mount's mirror target is also the named mount's endpoint under the named key, at the carried registry. A sweep of that store would delete data the other role owns.

One repository receives caller credentials and bypasses the public rules through the private leg.

The mount's private upstream can serve public content, so every version it holds would be trusted as private. Carries what the backend reported.

Asking the mount's private upstream what it aggregates threw rather than answering, so nothing was settled about it. Carries the rendered exception.

Two endpoints, each carried as its mount and its tagged key path, name the carried registry under different tags, so the two declarations disagree about what serves that store.

An explicit memory override breaks the combined memory-plan invariant even after every tenant shed to its minimum. A computed plan degrades and boots, an operator claim does not.

A split-deployment role (carried as its invocation) was selected over the bounded in-memory queue, whose jobs never leave the process that enqueued them.

The dedicated mirror worker was launched with no mount declaring a mirror target, so it has no queue to drain and nothing to publish.

Building the configured mirror-queue backend threw. Carries the rendered exception, which tells a transient fault from a permanent one to fix.

Preparing the configured advisory sync threw. Carries the rendered exception, which tells a transient fault from a permanent one to fix.

A vetted mirror store has no store maintenance backend the Dredger can sweep it with, carrying why.

Two dredger.quotaOverrides entries declare the same capacity pool differently, carried as the pool and the two keys that define it.

The configured pause between sweep chunks is beneath its floor, carried beside it. Only the deleting role reads the dredger group, so only that role refuses.

A mount's rules deny on the advisory database and no advisory store is configured, so those rules could never decide. Carries the mount and the rule names, in policy order.

An advisory store is configured and no mount is, so ecluse pilot has no ecosystem to compile an artifact for and would publish nothing.

The progress window is zero or negative. Carries the configured seconds.

The progress window is not below the serve-path cap, so the floor could never fire first on a served request. Carries the window and the cap, in seconds.

The progress floor's byte count is zero or negative. Carries the configured count.

The mount's store tag names no control plane this build implements.

The mount's store carries no operator consent to delete from it.

The store's only control plane is the ecosystem protocol, which spells no package listing or version delete.

The declared private cache lacks a supported maintenance or authentication operation.

Building the cleared backend's client against the live environment threw.

A mount's mirror target is also the named mount's private upstream, at the carried registry. Both mounts are carried, because the two can differ.

A mount's mirror target is also its own publication target, at the carried registry.

A dredger.quotaOverrides entry names a store no mount declares, carried as the key it was written under.

Whether the mount's private upstream serves public content stayed open, so that topology stays the operator's to verify. Carries why it stayed open.