Wire a registry with labels and trace linkage

An enquiries drafter that fetches its system prompt from Langfuse by label with an explicit cache TTL and a pinned fallback shipped with the code, drafts with claude -p on your subscription, and records the prompt name, version and fallback flag on every trace and in a local audit log. An offline demo with Langfuse's caching rules shows a release and a rollback each taking up to a TTL to reach a running worker.

Back to the exercise

Before you start

Before you start:Install Claude Code Python with uv Docker and Docker Compose Trace LLM calls with OpenTelemetry and Langfuse

The drafter asks the registry for "whatever production points at" on every matter, and the registry answers from a per-process cache. The decision that matters most is to log the version actually served, not the version you think is live: after a label move, a running worker keeps serving the old version until its cache entry expires, and with the registry down at cold start it serves the pinned fallback. Both are invisible unless every output carries its version and a fallback flag.

Wire a registry with labels and trace linkage

Back to the exercise

Wire a registry with labels and trace linkage

Before you start

Wire a registry with labels and trace linkage

Before you start

Sign in to keep reading the answer.

Sign in to keep reading the answer.