Iris Admin Lab

Ops help

Settings & rollout

Server env flags are not editable from the browser in v1. Copy these into Carelines .env and restart.

Environment flags

EnvDefaultMeaning
IRIS_BOT_VERSIONS_LIVEfalseWhen false, assignments are stored but live chat stays Builtin Iris v2.
IRIS_BOT_VERSIONS_LIVE_CLINIC_IDSemptyComma-separated clinic UUIDs. Empty + live=true → all clinics.
IRIS_BOT_VERSIONS_REQUIRE_SUITEtrueAssign / bulk-assign must pass golden suite (or override reason).

Safe rollout checklist

  1. 1

    Understand Builtin = Iris v2

    Production default is iris_v2 (persona prompt + JSON tools). No clinic assignment needed. Director versions only apply when IRIS_BOT_VERSIONS_LIVE is on and a published version with reply_engine=director is assigned.

  2. 2

    Clone builtin → edit → playground

    Create a draft from builtin, pick Iris v2 / Director / system-prompt-only, then verify in Playground.

  3. 3

    Publish

    Publishing freezes the config. Further changes require a new clone.

  4. 4

    Run suite

    Golden director scenarios must pass (or provide suite_override_reason when assigning).

  5. 5

    Assign dogfood clinic

    Set IRIS_BOT_VERSIONS_LIVE=true and optionally IRIS_BOT_VERSIONS_LIVE_CLINIC_IDS to one clinic UUID, then assign.

  6. 6

    Confirm live-status

    Overview should show that clinic as assigned_live.

  7. 7

    Assign all

    Clear allowlist (empty = all), keep live=true, then bulk-assign from the published version page.

  8. 8

    Rollback always available

    DELETE clinic assignment (one click in Clinics) or set IRIS_BOT_VERSIONS_LIVE=false on the server — falls back to Builtin Iris v2.

Production (static dist + nginx)

Build with npm run build, copy dist/ to the server. Browser calls /api/admin/*; nginx injects X-Admin-Api-Key and proxies to FastAPI. Do not put the admin key in the frontend build.

Local next dev only

NEXT_PUBLIC_IRIS_API_BASE=http://localhost:8000/api/v1
NEXT_PUBLIC_ADMIN_API_KEY=your-admin-api-key