RAINavigator

Representativeness checks, bias metrics and mitigation per ISO/IEC 5259; versioned datasets with lineage.

• practice-derived2 triggering use cases require Bias Testing & Data Quality Pipeline

Computes a probabilistic confidence score for every output and holds the transaction when the score falls below the workflow's regulatory threshold.

• practice-derived2 triggering use cases require Confidence Scoring & Threshold Gate

Feature attributions for classical ML, reasoning-trace summaries for GenAI — feeds the human reviewer and the technical file.

• practice-derived2 triggering use cases require Explainability API (SHAP/LIME/CoT)

HITL escalation queue & review UI ('Human-as-a-Tool': the agent calls the human like any other tool via propose-action objects). Confidence- and risk-threshold routing, SLA timers, structured accept/modify/reject verdicts with digital reviewer signature at gate release — each verdict is itself Art. 14 evidence and feeds the active-learning loop.

• practice-derived2 triggering use cases require HITL Escalation Queue & Review UI

Operator stop controls and degraded-mode fallbacks; real-time override (veto) channels for HOTL operation.

• practice-derived2 triggering use cases require Kill Switch / Graceful Degradation

Automated detection, pseudonymisation and blocking of personal data in inputs, retrievals and outputs.

• practice-derived2 triggering use cases require PII Scrubbing / DLP-NER Layer

Escalation triggers built from two independent signals, because raw model confidence is uncalibrated: calibrated trust scores (prompt relevance, similarity to historic successes, cross-model consistency) plus deterministic risk scores (sensitive categories, transaction value, protected data) — either crossing its threshold forces human review.

• practice-derived2 triggering use cases require Trust & Risk Dual Scoring

Append-only, hash-chained audit vault (WORM object-lock storage, AES-256 at rest, TLS 1.3 in transit). Guarantees tamper-evidence within the organization's trust domain — which stops your own team, but not an admin who can rebuild the vault. Pair with an external trust anchor and key ceremonies outside the operating team for evidence that holds against the insider scenario.

• practice-derived2 triggering use cases require WORM / Immutable Audit Vault

Pre-model validation of user input: injection detection, topic blocking, encoding checks.

• practice-derived1 triggering use case require Input Rails / Prompt Shields

Continuous evaluation against golden sets and sampled human verdicts; raises drift alerts and feeds the recertification cycle.

• practice-derived1 triggering use case require Model Drift & Accuracy Monitor

Abstraction layer decoupling application logic from model providers: dynamic routing on capability, cost, latency SLA and regulatory constraint (sensitive-data classes pinned to ZDR private/VPC endpoints or on-prem open-weight instances); real-time health monitoring with automatic fallback to secondary endpoints or local fine-tuned models on outage/latency spikes. Discharges resilience duties (DORA-class), prevents provider lock-in, and makes model deprecations a routing-table change instead of a re-architecture. Router decisions are logged into the decision trace — model version per event is an audit-packet field.

• practice-derived1 triggering use case require Multi-Model Router & Fallback Abstraction

Faithfulness scoring of answers against retrieved sources; deterministic fallback instead of hallucination; schema-validated structured output.

• practice-derived1 triggering use case require Output Rails / Groundedness Check

Relevance, freshness and per-user permission checks on every retrieved chunk; curated, versioned index.

• practice-derived1 triggering use case require Retrieval Rails (ACL-aware RAG)

Synthetic-content labelling & watermarking: visible disclosure plus machine-readable provenance (C2PA Content Credentials) embedded in generated images, audio and video; metadata identifying artificial origin survives common transformations. Discharges Art. 50(2)/(4) for deepfakes and synthetic media; verification telemetry (watermark presence/validity checks at publication gates) is the corresponding evidence stream.

• practice-derived1 triggering use case require Synthetic-Content Labelling / Watermarking