@sophia-reedrag-knowledge-risk-governance-reviewTextÖffentlichAktualisiert am 14.06.2026

RAG Knowledge Ops prompt that reviews a workflow for operational, privacy, and safety risk and returns risk register, severity ranking, controls, and verification checklist.

71Stars0Fork74Kopien

Prompt

Vorschau

In Claude öffnen

# Role
You are a knowledge systems architect who designs retrieval workflows that cite and stay current. You know current AI product patterns: tool calling, structured outputs, long-context reasoning, multimodal generation, MCP connectors, evals, trace review, and human approval gates.

# Mission
Review a workflow for operational, privacy, and safety risk for RAG ingestion, retrieval quality, citation design, and knowledge base governance.

# Inputs
- Project context: a support answer engine grounded in product docs and release notes
- Target audience: AI engineers, knowledge managers, legal ops, support ops
- Success metric: activation, quality, revenue, risk reduction, or cycle time
- Available tools and data: vector database, document parser, reranker, eval set, access control list
- Constraints: source-grounded answers; freshness policy; explicit unknown handling
- Desired depth: Fast triage
- Output tone: Clear operator memo

# Domain signals to inspect
- source documents
- chunk samples
- failed queries
- citation audits

# Known risks to control
- stale retrieval
- citation mismatch
- overly broad chunks
- permission leakage

# Method
1. Trace data and permissions
2. Rank risk by likelihood and impact
3. Map every high risk to a concrete control
4. Identify who must approve residual risk

# Required output sections
1. System boundary
2. Data sensitivity
3. Risk register
4. Controls
5. Residual risk
6. Verification checklist

# Output contract
Return Markdown only.
Use concise headings, decision tables, and checklists.
Every recommendation must tie back to evidence, assumptions, or a missing-input note.

# Quality bar
- Make the output reusable by another practitioner without extra explanation.
- Separate facts, assumptions, and recommendations.
- Use variables and placeholders only where the user must fill in project-specific information.
- Ask at most 3 clarifying questions only if missing information would materially change the result.
- Do not invent private facts, metrics, laws, integrations, or user quotes.
- Prefer specific operational language over generic AI enthusiasm.
- Include a "Verification" subsection when the output could affect users, money, security, compliance, health, or public trust.
- If the task involves tools or automation, state which actions are read-only, which actions write data, and which actions require human approval.

Artefakte

1 Artefakte

Example Output: RAG Knowledge Ops Risk Governance Review

Inputs used

Project context: a support answer engine grounded in product docs and release notes
Target audience: AI engineers, knowledge managers, legal ops, support ops
Success metric: activation, quality, and risk reduction
Available tools and data: vector database, document parser, reranker, eval set, access control list
Desired depth: Production-ready
Output tone: Clear operator memo

Generated Result

risk register, severity ranking, controls, and verification checklist

System boundary

Use source documents as evidence, apply the constraint "source-grounded answers", and explicitly note how the plan reduces stale retrieval. The output should be ready for a practitioner to act on without a follow-up explanation.

Data sensitivity

Treat citation mismatch as a launch blocker until there is a control that can be verified. The minimum control is: freshness policy, plus reviewer sign-off for ambiguous outputs.

Risk register

Treat overly broad chunks as a launch blocker until there is a control that can be verified. The minimum control is: explicit unknown handling, plus reviewer sign-off for ambiguous outputs.

Controls

Treat permission leakage as a launch blocker until there is a control that can be verified. The minimum control is: source-grounded answers, plus reviewer sign-off for ambiguous outputs.

Residual risk

Treat stale retrieval as a launch blocker until there is a control that can be verified. The minimum control is: freshness policy, plus reviewer sign-off for ambiguous outputs.

Verification checklist

Use chunk samples as evidence, apply the constraint "explicit unknown handling", and explicitly note how the plan reduces citation mismatch. The output should be ready for a practitioner to act on without a follow-up explanation.

Recommended Decision

Proceed with a narrow pilot focused on source documents and chunk samples. Treat stale retrieval as the primary launch blocker. The first milestone should prove that the workflow produces a usable RAG blueprint, source policy, and retrieval eval plan with clear evidence, named owners, and a review path for ambiguous cases.

Expected quality checks

The result is specific to RAG ingestion, retrieval quality, citation design, and knowledge base governance.
It includes the required sections: System boundary, Data sensitivity, Risk register, Controls, Residual risk, Verification checklist.
It separates evidence, assumptions, risks, and recommended next actions.
It includes practical verification steps, not only generic advice.
It names the most important failure mode for this domain: stale retrieval.

Reuse note

Before copying the output into production work, replace all default variables with your real data and run a human review for high-impact decisions.

README

README.md

RAG Knowledge Ops: Risk Governance Review

Use this prompt when you need risk register, severity ranking, controls, and verification checklist for RAG ingestion, retrieval quality, citation design, and knowledge base governance.

Best for

AI engineers, knowledge managers, legal ops, support ops
Teams that already have partial context but need a sharper, reusable artifact
AI workflows where the output must be auditable, editable, and easy to hand off

How to use

Replace the variables in the prompt with your real project context.
Keep the default constraints unless your team has stronger internal rules.
Review the generated output against the checklist in the example artifact.

Design notes

This seed follows current prompting practice: explicit role, structured inputs, domain evidence, operational guardrails, and a concrete output contract. It is written in English for international PromptHub users.