Informational Fresh jira_story: GOV-221

Lesson 2 of 6 — Tunable RAG thresholds per tenant

Command Centre Enhancements · Source: Jira Story GOV-221 (3 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Let each tenant tune Red/Amber/Green thresholds.

Why it matters

Risk appetite differs by tenant; fixed thresholds mislead.

Where this lives

Runs in the Customer AI Governance platform (components: command-centre). Per-tenant threshold config drives the RAG computation. Learn teaches this read-only.

Workflow

Given custom thresholds
When they are set
Then the RAG status reflects them

Worked example

A conservative bank wants 'Amber' to trigger earlier than default. Can they?

Yes — RAG thresholds are per-tenant configurable and the status reflects them.

Acceptance criteria (authoritative — GOV-221)

Given custom thresholds, when they are set, then the RAG status reflects them.

Common pitfalls

Hard-coding thresholds globally instead of per-tenant.

Knowledge check

Scenario: A conservative bank wants 'Amber' to trigger earlier than default. Can they?
Look for: Yes — RAG thresholds are per-tenant configurable and the status reflects them.

Key concepts

tunable thresholds
per-tenant config
RAG status

For the AI Tutor

Summary: Let each tenant tune Red/Amber/Green thresholds.
When to use: teaching or answering questions about "tunable rag thresholds per tenant".
When NOT to use: the underlying posture computation (that is GOV-135).
Key concepts: tunable thresholds, per-tenant config, RAG status.

Completion criteria

Learner passes the scenario knowledge check and can point to the system state that satisfies GOV-221's acceptance criterion.

Module: LEARN-MOD-008 (Command Centre Enhancements)
Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
Next: LEARN-LSN-041