vault_context all run locally. The inference gateway is the one optional seam
to a text-generating model, and everything that writes or judges prose routes
through it by role:
Absence is a supported state. With no gateway configured,
reflect returns
recall with available: false, knowledge_challenge reports unavailable, the
evaluator runs its deterministic rules without the judge layer, and the plane
scheduler idles. Nothing else degrades.
How the engine finds it
Two environment variables — there is deliberately no config-file block, so the gateway can differ per launcher:extract, synthesize, judge). Your
gateway’s only job is to answer those three aliases and route them to real models.
The resolved provider:model comes back with every response and is stamped into
the attestation of anything the gateway produces (e.g. a persisted reflection’s
source_model), so model swaps stay auditable.
Recommended setup: LiteLLM in Docker
One container plus a config file mapping the role aliases. All-local example (Ollama backend — zero keys, nothing leaves the machine):RELIQUARY_TC_GATEWAY_URL=http://127.0.0.1:4000 in your MCP client’s
server entry (the env block) and restart the client.
A plain http:// gateway URL on loopback needs nothing else. A non-loopback http:// URL (for example a
LiteLLM container at http://litellm:4000) must resolve to a private address and should be named in
network.plainHttpHosts; a public address is refused. See
Plain-http provider endpoints.
Deployment notes, learned the hard way:
- Pin the image. LiteLLM’s PyPI channel was compromised in early 2026; the
container channel is the safe distribution, but pin a digest
(
ghcr.io/berriai/litellm@sha256:…fromdocker image inspect) rather than a floating tag, and keep the container free of credentials it doesn’t need — an all-local config holds zero keys, which makes the supply-chain blast radius zero. - Bind loopback-only (
-p 127.0.0.1:4000:4000) unless you add a master key. - On Windows git-bash, prefix
docker runwithMSYS_NO_PATHCONV=1or the container-side/app/...paths get mangled into Windows paths.
Verify
reflect tool with any query: a working gateway returns a grounded
synthesis with chunk provenance; a missing/broken one returns sources with
available: false (that distinction is your health check).
Choosing models per role
The role→model map is a policy decision, and the yaml is the whole switch — reliquary-tc never changes:- All-local (above): private, free, offline. Trade-off: a 7B-class
synthesizeproduces grounded but imperfect prose — treat syntheses as drafts and verify against the returned sources. The engine is designed for weak judges: the evaluator’s judge can only lower eligibility verdicts, and a parse failure disables that layer rather than corrupting anything. - Hybrid: point
synthesizeat a hosted model (model: "anthropic/claude-sonnet-5-5"+ the API key in the container’s env) and keepjudge/extractlocal. Best quality where it shows most — but retrieved vault content leaves the machine on synthesis calls. That is a privacy boundary; cross it deliberately. - Any OpenAI-compatible endpoint works in place of LiteLLM if it can serve the three aliases (including Ollama directly, using model aliases created via Modelfiles).
What wakes up
With the gateway live:reflect synthesis and mode: "challenge",
knowledge_challenge (red-team against decision history), gateway-gated
preference extraction, and citation-inference stage 2.
The 4-hour plane sleep-time consolidation is the one exception — it is
opt-in, separate from the gateway itself. A gateway alone is not
consent to unattended, whole-vault LLM calls, so plane.enabled also defaults
to false and must be set explicitly:
reliquary-tc reflect (CLI), which gates
on the same env vars but not on plane.enabled — that flag only gates the
scheduled/ambient path.
The episode-eligibility evaluator is deliberately not on this list. It used
to consult the judge role, and no longer does: measurement showed the judge’s
entire effect was reproducing a status = "error" comparison, so it was removed
and the pass is now purely deterministic. It therefore runs identically with or
without a gateway, and acquires no network dependency at all.