disclaimer-language — Claude Code rule: what it does, how to install
The disclaimer-language rule supplies caution text for AI-assisted plans and reviews. It clarifies that agent output supports human assessment rather than replacing qualified review.
MIT ★ 1,627 updated 2026-10-25
.github/instructions/disclaimer-language.instructions.mdWhat disclaimer-language does
The rule provides separate disclaimers for work such as security planning, privacy review, Responsible AI planning and supply chain security. An agent displays the relevant notice at startup or when it presents findings. The notice frames its output as suggestions for internal assessment, not professional advice, approval or certification.
For Claude Code, place the rule at .claude/rules/disclaimer-language.md. Its scope covers planning and review files under .copilot-tracking/, along with documents under docs/planning/. Security, privacy and Responsible AI conclusions still need independent review by qualified people; the rule makes clear that an agent’s output is not sign-off.
What it helps with
- attach a caution notice to a security plan
- flag privacy findings for review by a qualified person
- clarify that Responsible AI suggestions are not legal approval
- require validation of supply chain security assessments
Example prompts for the agent
- Add the rule’s caution notice to this security plan.
- Show the privacy review disclaimer before presenting findings.
- Include a reminder that the Responsible AI assessment needs independent review.
How to install disclaimer-language
Manually: put the files in place
.github/instructions/disclaimer-language.instructions.mdThe applyTo field sets which files it applies to
Manually: put the files in place
.claude/rules/disclaimer-language.mdThe paths frontmatter field limits the files: move applyTo from the source into paths
AGENTS.md
Codex reads AGENTS.md: paste the rule text there
Manually: put the files in place
.cursor/rules/disclaimer-language.mdcFrontmatter: description, globs, alwaysApply. Move applyTo from the source into globs, or the rule will not attach on its own
Manually: put the files in place
.devin/rules/disclaimer-language.mdManually: put the files in place
.clinerules/disclaimer-language.mdStep by step, with commands for each platform: AGENTS.md vs CLAUDE.md: what they are and which one to use
Questions about disclaimer-language
How do I install disclaimer-language in Claude Code?
Place the rule file at .claude/rules/disclaimer-language.md.
What does disclaimer-language do?
It provides caution notices for AI-assisted planning and review work. The notices explain that agent output is for human assessment and does not replace qualified review.
Does the rule approve security or privacy findings?
No. It calls for independent review of relevant findings and states that agent output is not professional sign-off or certification.
Source text
disclaimer-language.instructions.md · MIT
---
description: "Centralized disclaimer language for AI-assisted planning and review agents requiring professional review acknowledgment"
applyTo: '**/.copilot-tracking/rai-plans/**, **/.copilot-tracking/rai-reviews/**, **/.copilot-tracking/security-plans/**, **/.copilot-tracking/sssc-plans/**, **/.copilot-tracking/sssc-reviews/**, **/.copilot-tracking/performance-plans/**, **/.copilot-tracking/adr-plans/**, **/.copilot-tracking/dt/**, **/.copilot-tracking/ds/**, **/docs/planning/adrs/**, **/docs/planning/outcome-hypotheses/**, **/.copilot-tracking/reviews/code-reviews/**, **/.copilot-tracking/security/**, **/.copilot-tracking/accessibility/**, **/.copilot-tracking/privacy-plans/**, **/.copilot-tracking/privacy-reviews/**, **/.copilot-tracking/prd-sessions/**, **/.copilot-tracking/brd-sessions/**, **/.copilot-tracking/documentation/**'
---
# Disclaimer Language
Planning and review agents display a CAUTION disclaimer at startup or when presenting findings. Each H2 section below is the verbatim disclaimer for one planner or review family and is loaded by its consuming artifact before use.
<!--
Authoring contract (parsed by scripts/linting/Validate-PlannerArtifacts.ps1):
- Each planner or review family gets exactly one H2 section. The first whitespace-delimited word of the heading, lowercased, is the slug (e.g. "SSSC Planning" -> "sssc"; "Code-Review" -> "code-review").
- A section may override the derived slug with exactly one `<!-- disclaimer-id: lower-kebab -->` marker immediately before its CAUTION block. The identifier must use lowercase letters or digits separated by single hyphens. Explicit metadata takes precedence; first-word derivation applies only when metadata is absent. Empty, malformed, misplaced, or repeated markers are invalid.
- The slug derives: planner key `{slug}-planner`; disclaimer id `{slug}-full-disclaimer`; disclaimer label `{heading} Disclaimer`.
- Each H2 must contain exactly one `> [!CAUTION]` blockquote; only the first is extracted.
- The CAUTION prose should begin with `**Disclaimer:**` (trailing colon optional); the prefix is stripped before matching against artifact footers.
- Multi-line blockquote prose is joined with single spaces.
-->
## RAI Planning
> [!CAUTION]
> **Disclaimer:** This agent is an assistive tool only. It does not provide legal, regulatory, or compliance advice and does not replace Responsible AI review boards, ethics committees, legal counsel, compliance teams, or other qualified human reviewers. The output consists of suggested actions and considerations to support a user's own internal review and decision‑making. All RAI assessments, risk classification screenings, security models, and mitigation recommendations generated by this tool must be independently reviewed and validated by appropriate legal and compliance reviewers before use. Outputs from this tool do not constitute legal approval, compliance certification, or regulatory sign‑off.
## Security Planning
> [!CAUTION]
> **Disclaimer:** This agent is an assistive tool only. It does not provide legal, regulatory, or compliance advice and does not replace professional security review boards, penetration testing teams, compliance auditors, legal counsel, or other qualified human reviewers. The output consists of suggested actions and considerations to support a user's own internal security review and decision‑making. All security plans, threat models, security models, and mitigation recommendations generated by this tool must be independently reviewed and validated by appropriate security and compliance reviewers before use. Outputs from this tool do not constitute security approval, compliance certification, or regulatory sign‑off.
## Privacy Planning
> [!CAUTION]
> **Disclaimer:** This agent is an assistive tool only. It does not provide legal, regulatory, or privacy compliance advice and does not replace privacy counsel, data protection officers, compliance teams, or other qualified human reviewers. The output consists of suggested analyses, control recommendations, and privacy considerations to support a user's own internal privacy review and decision‑making. All privacy plans, DPIA assessments, data-flow analyses, and mitigation recommendations generated by this tool must be independently reviewed and validated by appropriate privacy and compliance reviewers before use. Outputs from this tool do not constitute legal approval, privacy certification, or regulatory sign‑off.
## Privacy Review
> [!CAUTION]
> **Disclaimer:** This agent is an assistive review tool only. It does not provide legal, regulatory, or privacy compliance sign-off and does not replace privacy counsel, data protection officers, compliance teams, or other qualified human reviewers. The output consists of AI-assisted findings, observations, and suggested next steps to support a reviewer's own privacy analysis and decision‑making. All privacy-review findings, DPIA observations, control recommendations, and risk assessments generated by this tool must be independently reviewed and validated by a qualified privacy reviewer before acting on them or treating any finding as resolved. Outputs from this tool do not constitute legal approval, privacy certification, or regulatory sign‑off.
## SSSC Planning
> [!CAUTION]
> **Disclaimer:** This agent is an assistive tool only. It does not provide legal, regulatory, or compliance advice and does not replace professional supply chain security review boards, OpenSSF Scorecard evaluators, SLSA auditors, legal counsel, or other qualified human reviewers. The output consists of suggested actions, review findings, and considerations to support a user's own internal supply chain security review and decision‑making. All supply chain assessments, review reports, gap analyses, backlog items, and mitigation recommendations generated by this tool must be independently reviewed and validated by appropriate security and compliance reviewers before use. Outputs from this tool do not constitute security approval, compliance certification, or regulatory sign‑off.
## Outcome-Hypothesis
> [!CAUTION]
> **Disclaimer:** This skill is an assistive decision-support tool only. It does not provide financial or professional investment advice and does not replace affected stakeholders, measurement owners, accountable sponsors or decision owners, or other qualified human reviewers. The investability verdict is an evidence-readiness signal only: "investable" means the defined evidence gates passed, and "not investable" means required evidence is incomplete. All scorecards, outcome hypotheses, investability verdicts, targets, and measurement plans must be independently reviewed and validated by affected stakeholders, the measurement owner, and the accountable sponsor or decision owner before funding, commitment, or implementation. Outputs from this tool do not constitute investment approval, funding authorization, stakeholder commitment, or measurement sign-off.
## ADR Planning
> [!CAUTION]
> **Disclaimer:** This agent is an assistive tool only. It does not provide legal, regulatory, architectural, or compliance advice and does not replace architecture review boards, design authorities, technical leadership, legal counsel, or other qualified human reviewers. The output consists of suggested decisions, considered options, consequences, and lineage metadata to support a user's own architecture decision-making. All Architecture Decision Records, supersession lineage, ASR trigger evaluations, and handoff work items generated by this tool must be independently reviewed and validated by appropriate architecture and engineering reviewers before adoption. Outputs from this tool do not constitute architectural approval, design sign-off, or compliance certification.
## PRD Requirements Planning
> [!CAUTION]
> **Disclaimer:** This agent is an assistive tool only. It does not provide product management approval, technical feasibility validation, or business sign-off and does not replace product managers, engineering leads, business stakeholders, or other qualified human reviewers. The output consists of suggested requirements, acceptance criteria, and product specifications to support a user's own product planning and decision-making. All Product Requirements Documents, functional requirements, non-functional requirements, and constraint definitions generated by this tool must be independently reviewed and validated by appropriate product and engineering reviewers before adoption. Outputs from this tool do not constitute product approval, requirements sign-off, or engineering commitment.
## BRD Requirements Planning
> [!CAUTION]
> **Disclaimer:** This agent is an assistive tool only. It does not provide business approval, regulatory compliance validation, or executive sign-off and does not replace business analysts, stakeholder representatives, compliance teams, or other qualified human reviewers. The output consists of suggested business requirements, objectives, and scope definitions to support a user's own business analysis and decision-making. All Business Requirements Documents, business objectives, stakeholder analysis, and requirement traceability generated by this tool must be independently reviewed and validated by appropriate business and compliance reviewers before adoption. Outputs from this tool do not constitute business approval, requirements sign-off, or stakeholder commitment.
## Design Thinking Coaching
> [!CAUTION]
> **Disclaimer:** This agent is an assistive coaching tool only. It does not conduct user research, observe stakeholders, or speak for the people whose problems you are designing for, and it does not replace primary research, direct stakeholder contact, design review, or product and strategy decision authority. Personas, problem statements, journey maps, empathy maps, concept tests, and other Design Thinking artifacts produced with this tool are scaffolding for your own research and synthesis — not substitutes for real stakeholder voice or observed behavior. Validate all AI-generated assumptions, personas, themes, and insights against actual stakeholders before treating any Design Thinking artifact as a basis for product, design, or strategy commitments. Outputs from this tool do not constitute validated research findings or design approval.
## Data Science and Engineering Coaching
<!-- disclaimer-id: data-science-engineering -->
> [!CAUTION]
> **Disclaimer:** This agent is an assistive data-science and data-engineering coaching tool only. It does not validate customer data, execute production pipelines, establish model fitness, or replace data owners, privacy and Responsible AI reviewers, engineering review, or business decision authority. Catalogs, feasibility findings, analyses, experiments, tests, and operational recommendations generated with this tool may be incomplete or inaccurate and must be independently reviewed against approved data sources, stakeholder evidence, and organizational controls before use. Outputs from this tool do not constitute data approval, feasibility sign-off, model approval, privacy or Responsible AI approval, or production readiness.
## Code-Review
> [!CAUTION]
> **Disclaimer:** This agent is an assistive review tool only. It does not provide engineering sign-off, security certification, or compliance approval and does not replace qualified human code review, security review boards, or other professional reviewers. The output consists of AI-assisted findings, observations, and suggested remediations to support a reviewer's own analysis and decision-making. All code-review findings — including functional, standards, and accessibility observations — generated by this tool must be independently reviewed and validated by a qualified human reviewer before acting on them, merging changes, or treating any finding as resolved. Outputs from this tool do not constitute engineering approval, merge authorization, or compliance certification.
## Security-Review
> [!CAUTION]
> **Disclaimer:** This agent is an assistive review tool only. It does not provide legal, regulatory, or compliance advice and does not replace professional security review boards, penetration testing teams, compliance auditors, or other qualified human reviewers. The output consists of AI-assisted findings, risk observations, and suggested remediations to support a reviewer's own security analysis and decision-making. All security-review findings, vulnerability assessments, and remediation recommendations generated by this tool must be independently reviewed and validated by a qualified security reviewer before acting on them or treating any finding as resolved. Outputs from this tool do not constitute security approval, compliance certification, or regulatory sign-off.
## Accessibility-Review
> [!CAUTION]
> **Disclaimer:** This agent is an assistive review tool only. It does not provide accessibility conformance certification or legal compliance sign-off and does not replace professional accessibility audits, assistive-technology user testing, or other qualified human reviewers. The output consists of AI-assisted findings, success-criteria observations, and suggested remediations to support a reviewer's own accessibility analysis and decision-making. All accessibility-review findings, conformance assessments, and remediation recommendations generated by this tool must be independently reviewed and validated by a qualified accessibility reviewer before acting on them or treating any finding as resolved. Outputs from this tool do not constitute accessibility conformance certification or legal compliance sign-off.
## Canonical session-state fields consumed by this disclaimer protocol
Planning and coaching agents that adopt this disclaimer protocol persist acknowledgment in their session state file (`state.json` for planners; `coaching-state.md` YAML for the DT Coach). The following field is required:
- `disclaimerShownAt` — ISO 8601 timestamp recording the most recent time the full disclaimer was shown to the user. Set to `null` until first display, leave unchanged during normal continuation, and update only when the full disclaimer is actually shown again. This field is not the immutable first-display audit record; the `noticeLog` array preserves the display history.
© microsoft · MIT · microsoft/hve-core