# Public issue template 010

## Title

[pilot] Prepare Pilot Acceptance Checklist v2

## Labels

`pilot`, `qa`, `docs`

## Purpose

Update pilot acceptance criteria after the residual risk register and public
issue plan.

## Background

Pilot acceptance must distinguish technical readiness, operational evidence,
governance visibility and pending registry release evidence.

## Scope

- Update pilot acceptance checklist.
- Reference residual risks and smoke checks.
- Define evidence required for pilot closeout.
- Keep registry completion claims out of pilot wording.

## Non-goals

- No change to runtime behavior.
- No claim that registry submission is complete.
- No automatic acceptance without evidence.

## Acceptance criteria

- Pilot checklist v2 exists.
- Residual risks are referenced.
- Smoke and evidence checks are listed.
- Pending registry items remain marked pending.

## Evidence required

- Updated checklist.
- Links to residual risks and validation runbooks.
- Pilot smoke command results when available.
- Open gap list.

## Safety/privacy guardrails

- Do not publish real customer data, employee logs or confidential pilot notes.
- Use sanitized evidence references.
- Keep private pilot evidence outside public issue text.

## Registry-positioning guardrails

- Pilot acceptance is not registry registration.
- Registry release evidence still requires the Russian build-runner.
- Do not claim certification or SIEM/DLP replacement.

## Checklist

- [ ] Review current pilot checklist.
- [ ] Add residual risk references.
- [ ] Add smoke/evidence requirements.
- [ ] Mark pending registry items.
- [ ] Review forbidden claims.
