shredbx logo
shredbx shredbx shredbx shredbx Personal
  • Home
  • Lab
  • Portfolio
  • Experience
  • Services
  • Profile
  • Contact
AClaude
  • Home
  • Lab
  • Portfolio
  • Experience
  • Services
  • Profile
  • Contact
Andrei Solovev
Knowledge
Search knowledge... ⌘K
Knowledge · Rules · Process

Verification Report Standard

Proof-of-work report template — every claim of done/working/fixed MUST include verifiable evidence

Andrei Solovev

Tags

rule

Overview

Purpose

Proof-of-work report template — every claim of done/working/fixed MUST include verifiable evidence

Rules

VER-001: NEVER use words "done", "working", "fixed", "ready", "implemented", "live", "deployed", "verified" without at least ONE piece of runtime evidence (screenshot, curl output, DOM snapshot, test result). "Build passes" alone is NEVER sufficient evidence.

VER-002: When verification is blocked (Docker down, service unavailable, network issue), report status as PENDING with explicit blocker. Never upgrade PENDING to VERIFIED without re-running verification after blocker is resolved.

VER-003: ALL UI changes MUST include a browser screenshot as evidence. Use playwright browser_take_screenshot or chrome-devtools take_screenshot. Screenshot must show the changed area, not just the page header.

VER-004: For component imports from prototypes, the screenshot MUST be compared with the prototype visually. Note specific matches and mismatches. "Looks similar" is not sufficient — list exact CSS values that match.

VER-005: The full verification chain for UI work: 1. sbx build → exit 0 2. Container/server restart → health check passes 3. curl → HTTP 200 on target URL 4. Navigate in browser → page renders 5. Screenshot → visual evidence 6. Compare with prototype → specific value match Only after ALL steps pass can work be reported as VERIFIED.

VER-006: If ANY step in the verification chain is blocked, disclose immediately. Do not proceed with "it probably works". State: - Which step is blocked - Why - What the plan is to unblock - When verification can resume

shredbx logo shredbx shredbx shredbx shredbx Andrei Solovev

Solution Architect & Lead Software Engineer

ExperiencePortfolioResearch & ExperimentsEducationCertificationSkills
GitHub ↗LinkedIn ↗Email ↗
AVAILABLE FOR NEW PROJECTS
// MY LATEST BEATS
Hobby & Interests

Lab

  • The Lab
  • Framework
  • Components
  • Packages
  • Games
  • Process (SDLC)
  • Knowledge
  • Blog

Andrei

  • Portfolio
  • Experience
  • Services
  • Profile
  • Contact
  • Lifestyle

Team

  • Team
  • Andrei
  • Claude

Legal

  • Privacy
  • Terms
  • Cookies
© 2026 shredbx.com. All rights reserved. — Andrei Solovev |