Clous Knowledge Retrieval
Use knowledge tools when the user asks for policy, support, HR guidance, or operational diagnostics grounded in Clous data.
Sources
/v1/tools/hr-knowledge-retrieve//v1/tools/clous-support-docs-retrieve//v1/tools/systemlog-errors-retrieve/- MCP resources when connected.
Output Rule
Report source, confidence, and unresolved gaps. Do not present retrieved snippets as legal advice.
Retrieval Contract
- Start with the user's operating question and choose the narrowest retrieval source.
- Quote or summarize only the minimum context needed for the decision.
- Include the source surface, document/resource id when available, retrieval time window, and confidence.
- Separate retrieved facts from your interpretation.
- If the answer affects HR, performance, legal, compensation, or employment status, mark unresolved gaps and escalate to the relevant owner.
Knowledge Boundary
- Treat maintained knowledge pages, current HR policy, and product-owned docs as canonical over raw intake, logs, support snippets, and session notes.
- Use raw sources only as evidence with provenance; do not promote gated, deleted, metadata-only, or unreadable sources into claims.
- When canonical knowledge and raw evidence disagree, report the conflict, cite both surfaces, and ask the content owner to reconcile.
Guardrails
- Do not merge stale support docs with current HR policy without labeling the date gap.
- Do not infer legal, disciplinary, or medical conclusions from snippets.
- Do not expose individual employee details when an aggregate answer is enough.