Design fixture
Evidence card
Show source path, generated output, date, residual risk, and next action without nesting cards.
Good Example
A card lists the crawl export path, generated report, date, status, residual risk, and the next verification command.
pass
Crawl evidence
Source: reports/crawl/crawl-evidence-report.json
Generated: current QA run
Risk: production domain crawl still requires QA_PRODUCTION_URL before launch.
Bad Example
A proof card claims Passed with no report path, date, or remaining risk.
Ambiguous decorative status without enough context, source, or command evidence.
States
- pass
- needs-review
- blocked
- stale
- missing-file
Responsive Constraint
Dense evidence metadata stays readable in a single card and never nests another card inside it.
Accessibility Constraint
Status labels include text and remain readable in light and dark color schemes.
Agent Check
Can an agent cite this evidence in a handoff report without inventing missing context?
QA Gates
npm run qa:browsernpm run qa:handoff