# Evidence Template

Use this template when submitting The Gateway evidence for install behavior, route/DNS ownership, fallback, recovery, or privacy posture.

## Summary

- Evidence type:
- Deployment mode:
- Hardware class:
- The Gateway version or commit:
- Date:
- Operator:
- Screenshot surface reviewed:
- Screenshot decision:
- Screenshot result:
- Screenshot unchanged rationale:
- Screenshot redaction or unchanged note:
- Production domain status:

## Claim Supported

What public claim does this evidence support?

## Verification Notes

- Check the canonical host first: `https://thegateway.pro/`.
- Verification order: canonical host first, `www` host second, Cloudflare Pages root alias third, release host last.
- If the evidence package is docs-only or copy-only, screenshots may stay unchanged, but the notes must name the reviewed surface and explain why the current assets were still sufficient.
- If screenshots were refreshed, name the surface reviewed, the redaction approach, and the claim each image supports so the evidence stays auditable even when the assets changed.
- If screenshots were not refreshed, record the screenshot unchanged rationale in the summary, say which surface was reviewed, and explain why the current assets remained sufficient.
- Record the canonical host and `www` host status codes in the evidence notes so the live production domain check is explicit.
- Record the observed HTTP status codes and `Location` headers in the attachment notes so the redirect path is explicit.
- Use the root URL of the release host for the verifier, without a path, query, or fragment.
- Note which release-host label was verified in the release notes or attachment summary so the post-deploy check can be reproduced for audit without exposing provider-specific URLs in visitor-facing copy.
- Capture the Cloudflare Pages root alias and release host `Location` headers in the evidence notes so the redirect target is auditable, then keep those exact labels out of public copy.

## Public Copy Hygiene

- Confirm the evidence notes and attachment summary do not expose internal development terms, tooling names, workspace paths, versioned deployment URLs, or provider-specific deployment endpoints.
- Keep the canonical host, `www` alias, Pages root alias, and release host labels in audit notes only, not in visitor-facing copy.
- If any exception is required for audit purposes, keep it out of visitor-facing copy and explain why it is needed.

## Build Output Hygiene

- Confirm `npm run build` leaves `_site` free of workspace metadata, hidden workspace directories, dependency directories, and repository internals such as `AGENTS.md`, `SOUL.md`, `USER.md`, `MEMORY.md`, `node_modules`, and `.git`.

## Pre-release Checks

- `npm audit --audit-level=high` result:
- No high-severity advisories blocked release:

## Release Host Verification

- Canonical host checked: `https://thegateway.pro/`
- `www` alias checked: HTTP 200
- Canonical host result:
- `www` host result:
- `www` alias label used for the release check:
- Cloudflare Pages root alias checked: HTTP 301 back to `https://thegateway.pro/`
- Cloudflare Pages root alias result:
- Cloudflare Pages root alias `Location` header:
- Cloudflare Pages root alias label used for the release check:
- Release host checked: HTTP 301 back to `https://thegateway.pro/`
- Release host result:
- Release host `Location` header:
- Release host label used for the release check:

## Procedure

1. Check the canonical host and the `www` host first.
2. Check the Cloudflare Pages root alias and the release host next.
3. Record the status codes, `Location` headers, and exact alias labels in the release notes or attachment summary.

## Observed Result

What happened?

## Remaining Risk

What is still unproven, partial, or environment-specific?

## Redaction

What was removed or blurred before sharing?

## Attachments

- Demo:
- Screenshot:
- Screenshot decision/result:
- Install transcript:
- Route/DNS check:
- `www` host check:
- Fallback check:
- Recovery drill:
- Production domain check:
- Alternate release host redirect check:
- Observed HTTP status codes:
- Observed redirect targets / Location headers:
- Canonical host result:
- `www` host result:
- Cloudflare Pages root alias result:
- Release host result:
- Cloudflare Pages root alias root URL used for the release check:
- Cloudflare Pages root alias label used for the release check:
- `www` alias label used for the release check:
- Release host label used for the release check: