# Flow 05 parity proof

Verdict: **PASS**

Signed: 2026-07-17T09:52:37.385200Z

## What passed

- The same 53-line artifact was used for both sinks. SHA-256:
  `e2aa6dd6cbbf0ed9d32d61c6dbd8b568732b007b7bbdf7a89f560f3f381c6494`.
- Native Hermes delivered it to Discord channel `1483956352073203796` and
  returned provider message ID `1527610518821539940` with exit code `0`.
- Owner email delivery was provider-accepted once for each approved address.
  Gmail readback found message `19f6f71cdc6affb4` in `INBOX`, with DKIM, SPF
  and DMARC passing. iCloud has provider acceptance but no inbox connector.
- An idempotent rerun preserved one attempt per recipient and created zero
  duplicate sends.
- Email deadman v2 was healthy and non-emitting. The Discord deadman passed an
  isolated 08:11 schedule-boundary fixture with one official emitter and no
  competing digest emitter. This fixture is not represented as a live 08:10
  production observation.
- Native Inspector task `t_c228bea9`, run `22`, worker PID `17302`, signed the
  full parity receipt after all 14 checks passed with no remaining blocker.

## Evidence

- `clean-run/2026-07-17.md`
- `flow05-discord-receipt.json`
- `flow05-email-receipt.json`
- `flow05-email-idempotency.json`
- `flow05-email-deadman.json`
- `flow05-discord-deadman.json`
- `INSPECTOR-FULL-PARITY-VERDICT.json`

## Boundaries

This parity canary created no commercial send or publication, changed no gate,
authorized no cutover, left production authoritative, and did not touch ALZO.
Direct Discord REST readback is unavailable because the bot lacks read
permission; the receipt is the provider-issued message ID and native Hermes
success. No runtime rollback is required for this evidence sync.