---
name: real-user-verification
description: Verify user-facing work through real journeys, visual evidence, and inspected outcomes.
version: 1.0.0
updated: 2026-08-14
---

# Real-User Verification

1. Turn each user story and edge case into a click-by-click journey with a measurable terminal state.
2. Use the application surface a user actually uses. Authenticate as the relevant role; do not replace final UI proof with HTTP or SSR checks.
3. Capture page load, inputs, state changes, errors, recovery, and completion at relevant desktop and mobile sizes.
4. For time-varying flows, capture roughly every second and build a labeled, chronological contact sheet.
5. Assert important network responses, persisted state, timings, and unexpected console/page errors.
6. Test refresh, retry, interruption, partial completion, and device change when the feature promises them.
7. Inspect every screenshot yourself and describe what it proves. Green automation alone is insufficient.
8. Clean up test records and processes only through safe, authorized, reversible procedures.

If live providers or production systems are required, obtain current explicit authority first. State exactly what was mocked, skipped, failed, or could not be observed.

Record served-artifact identity: exact process and entrypoint, source/build revision, asset freshness, environment, and database target. Development freshness cannot stand in for production-bundle evidence.

For a tutorial completion gate, use `tutorial-verified-done`. Capture narrated desktop/mobile light/dark variants where applicable, derive transcripts from recorded audio, and pin contact sheets and verdicts to exact bytes. Declare which source controls layout and which controls color and tone; narrate the visible frames supporting each claim. Any failed or mismatched flow must be repaired and re-recorded end to end.