---
name: claim-boundary-copy
description: >
  Use when drafting public copy, sample-case pages, skill descriptions, or
  verification results. Keeps claims inside WitnessOps doctrine. Never call the
  work a pentest, certification, or proof that a system is secure.
---

# Claim boundary copy

Every public sentence must stay inside what the artefact actually established.

## Required limits

Always be willing to say:

- No exploitation
- Fixed scope
- No credentials and no internal access
- No destructive testing and no continuous monitoring
- No claim that this is a pentest, certification, or proof the system is secure

## Workflow

1. Name the artefact (receipt, sample, skill report, handover).
2. Name the checks that ran.
3. Name the inputs that were not independently checked.
4. State the limitation in the same breath as any positive result.
5. Prefer "labelled sample" over "customer evidence" unless it is.

## Guardrails

- Do not write "verified safe".
- Do not write "production-ready" from a local scan.
- Do not present examples as live customer artifacts.
- Do not collapse Incomplete into Valid.
- If a sentence could be read as a certification, rewrite it.

## Outputs

- bounded copy
- explicit non-claims