docs: remove HIPAA claim and persist compliance approval policy

.agents/references/compliance-claims-policy.md

@@ -0,0 +1,18 @@
+# Compliance claims policy
+
+Apply this policy when writing, reviewing, or answering questions from Warp documentation and other customer-facing content, including content about Oz and the Automation Platform.
+
+Warp is not HIPAA compliant. Omit HIPAA from customer-facing content and never imply that Warp or Oz supports HIPAA-regulated workloads or offers a HIPAA business associate agreement.
+
+Include other certifications, attestations, or compliance commitments only when a current Warp Security or Legal-approved source confirms the exact claim and its scope. Omit unsupported claims and flag them internally.
+
+Before retaining or adding a claim:
+
+* Record the approved source, its date or revision, the approving Security or Legal authority, and the exact product, plan, provider, model, deployment, and data scope it covers in the PR evidence.
+* Distinguish an attestation from a certification, provider-side retention from Warp storage, and technical controls from contractual commitments. Do not infer compliance from encryption, self-hosting, a provider's certification, or a telemetry setting.
+* Do not treat existing docs, source code, a generated draft, a positioning document, a sales or support statement, or a general PR approval as Security or Legal approval.
+* Omit a claim when its approval, currency, or scope cannot be established. Report the omitted claim and missing evidence in the internal handoff or PR's `Unverified claims` section, without exposing confidential source material. Do not leave the unsupported promise in public prose with a `VERIFY` marker.
+
+For review, request changes if customer-facing content violates this policy. An ordinary documentation-risk waiver does not authorize a compliance claim.
+
+This versioned policy is durable repository guidance, not a write to platform-managed Agent Memory.

.agents/references/doc-quality-policy.md

@@ -15,6 +15,8 @@ document is the single source of truth for the *rules*; the code enforces them.
 
 ## Scope
 
+Compliance claims follow `.agents/references/compliance-claims-policy.md`. This is an exception to generic source verification and `VERIFY` handling: source code or existing docs cannot establish Security or Legal approval. Omit unsupported compliance promises from public content, flag them in the PR evidence, and request changes when they remain. A Docs override does not replace the required approval.
+
 This program covers every agent-authored content PR in `warpdotdev/docs` —
 `draft_*`, `release_updates`, AEO, `missing_docs`, and any other recurring
 skill that adds or changes public documentation. It is not limited to ambient

.agents/skills/draft_conceptual/SKILL.md

@@ -9,6 +9,8 @@ Draft a conceptual documentation page that explains what a feature or concept is
 
 ## Workflow
 
+Read and apply `.agents/references/compliance-claims-policy.md` before drafting, including its omission and internal-reporting rules.
+
 Follow the workflow in `.agents/skills/draft_docs/SKILL.md`, using the **conceptual template** at `.agents/templates/conceptual.md`.
 
 ## Frontmatter description

.agents/skills/draft_docs/SKILL.md

@@ -118,6 +118,8 @@ Once the content type is identified:
 Read 2-3 strong examples in the target section to match existing patterns and conventions.
 
 ### 6. Research source code (if needed)
+Before verifying claims, read and apply `.agents/references/compliance-claims-policy.md`. Omit HIPAA and unsupported compliance promises from customer-facing content; record missing Security or Legal approval in the internal handoff or PR evidence, not a public `VERIFY` marker. This exception overrides the generic source and marker options below.
+
 For technical accuracy, optionally look in Warp's source repositories:
 - **warp-internal** - Client-side code (Rust, Swift, etc.)
 - **warp-server** - Server-side code (Go)

.agents/skills/draft_faq/SKILL.md

@@ -28,6 +28,8 @@ If the rules do not all hold, say so and redirect:
 
 ## Workflow
 
+Read and apply `.agents/references/compliance-claims-policy.md` before drafting, including its omission and internal-reporting rules.
+
 Follow the workflow in `.agents/skills/draft_docs/SKILL.md`, using the **FAQ template** at `.agents/templates/faq.md`.
 
 ## Frontmatter description

.agents/skills/draft_feature_doc/SKILL.md

@@ -9,6 +9,8 @@ Draft a feature documentation page that combines conceptual and procedural conte
 
 ## Workflow
 
+Read and apply `.agents/references/compliance-claims-policy.md` before drafting, including its omission and internal-reporting rules.
+
 Follow the workflow in `.agents/skills/draft_docs/SKILL.md`, using the **feature-doc template** at `.agents/templates/feature-doc.md`.
 
 ## Frontmatter description

.agents/skills/draft_guide/SKILL.md

@@ -20,6 +20,8 @@ Tutorials are more conversational than other content: a developer-to-developer c
 
 ## Workflow
 
+Read and apply `.agents/references/compliance-claims-policy.md` before drafting, including its omission and internal-reporting rules.
+
 Follow the workflow in `.agents/skills/draft_docs/SKILL.md`, using the **guide template** at `.agents/templates/guide-page.md`.
 
 Guide pages live in `src/content/docs/guides/` (the Guides Astro Starlight space), not in the main product reference sections. When placing the file, use these directories:

.agents/skills/draft_procedural/SKILL.md

@@ -9,6 +9,8 @@ Draft a procedural documentation page with step-by-step instructions to accompli
 
 ## Workflow
 
+Read and apply `.agents/references/compliance-claims-policy.md` before drafting, including its omission and internal-reporting rules.
+
 Follow the workflow in `.agents/skills/draft_docs/SKILL.md`, using the **procedural template** at `.agents/templates/procedural.md`.
 
 ## Frontmatter description

.agents/skills/draft_quickstart/SKILL.md

@@ -17,6 +17,8 @@ A tutorial for a product area requires that its quickstart already exist. If you
 
 ## Workflow
 
+Read and apply `.agents/references/compliance-claims-policy.md` before drafting, including its omission and internal-reporting rules.
+
 Follow the workflow in `.agents/skills/draft_docs/SKILL.md`, using the **quickstart template** at `.agents/templates/quickstart.md`.
 
 ## Frontmatter description

.agents/skills/draft_reference/SKILL.md

@@ -9,6 +9,8 @@ Draft a reference documentation page with structured, exhaustive information for
 
 ## Workflow
 
+Read and apply `.agents/references/compliance-claims-policy.md` before drafting, including its omission and internal-reporting rules.
+
 Follow the workflow in `.agents/skills/draft_docs/SKILL.md`, using the **reference template** at `.agents/templates/reference.md`.
 
 ## Frontmatter description

.agents/skills/draft_troubleshooting/SKILL.md

@@ -9,6 +9,8 @@ Draft a troubleshooting page that helps users diagnose and fix common issues.
 
 ## Workflow
 
+Read and apply `.agents/references/compliance-claims-policy.md` before drafting, including its omission and internal-reporting rules.
+
 Follow the workflow in `.agents/skills/draft_docs/SKILL.md`, using the **troubleshooting template** at `.agents/templates/troubleshooting.md`.
 
 ## Frontmatter description

.agents/skills/review-docs-pr/SKILL.md

@@ -72,6 +72,8 @@ review focus areas, this pass is the human-review-blocking gate defined in
 
 ## Review Instructions
 
+Read and apply `.agents/references/compliance-claims-policy.md`. Flag customer-facing HIPAA references, implications of HIPAA-regulated-workload or HIPAA business associate agreement support, and other compliance promises without current Security or Legal approval as critical accuracy findings and request changes. Existing docs, source code, general approvals, and public `VERIFY` markers do not satisfy that policy.
+
 Review this documentation PR for the docs repository.
 
 Focus on:

AGENTS.md

@@ -6,6 +6,10 @@
 
 This guide establishes standards for writing Warp documentation. It covers voice, formatting, content types, and terminology. Keep the full writing rules here. Skills and templates must state the actions needed for their tasks and link here for additional detail. Document product behavior in the relevant product documentation, not in general writing rules.
 
+## Compliance claims
+
+Before writing, reviewing, or answering from docs, apply [the compliance claims policy](.agents/references/compliance-claims-policy.md). Warp is not HIPAA compliant; omit HIPAA from customer-facing content and never imply support for HIPAA-regulated workloads or a HIPAA business associate agreement. Other compliance claims require a current Warp Security or Legal-approved source for the exact claim and scope. Omit unsupported claims and flag them in the internal handoff or PR evidence.
+
 ## Writing style
 
 ### Voice & tone

src/content/docs/enterprise/team-management/admin-panel.mdx

@@ -106,7 +106,7 @@ The features available in the Admin Panel scale with your Warp plan:
 * **Enterprise secret redaction** - Custom regex patterns for secrets
 * **BYOLLM** - Route inference through your cloud infrastructure
 * **Self-hosting cloud agent workers** - Deploy cloud agent workers on your own infrastructure
-* **Advanced compliance** - SOC 2, HIPAA, and custom data handling agreements
+* **Advanced compliance** - SOC 2 and custom data handling agreements
 * **Priority support** - Dedicated Slack/Teams channels
 
 For complete plan details, see [Warp pricing](https://www.warp.dev/pricing) or [contact sales](https://www.warp.dev/contact-sales).