# Trust/ship bar

**Test family:** `SHIP`

Apply these to the task, not mechanically to every pixel. Cross-cutting failures often emerge only through interactions with domain item files.

- **SHIP-001** Every core product promise has direct evidence at its highest-risk boundary.
- **SHIP-002** No unresolved severe security, privacy, integrity, accessibility-blocker, payment, or tenant-isolation failure.
- **SHIP-003** Recovery, rollback/cancel, monitoring, audit, and ownership exist for residual risk.
- **SHIP-004** Blocked and untested areas are explicit enough that the decision maker cannot mistake absence of evidence for a pass.

## Comprehensive per-item coverage

- **SHIP-005** Apply the quality concern to absent, empty, ordinary, boundary-size, malformed, stale, concurrent, and failure-state data.
- **SHIP-006** Include text containing ASCII emoticons, emoji/ZWJ sequences, kaomoji, accents, mixed scripts, RTL, combining marks, confusables, invisible characters, and control characters.
- **SHIP-007** Exercise UI, API, import/export, automation, mobile, background jobs, notifications, analytics, logs, caches, and stored representations.
- **SHIP-008** Test anonymous, ordinary, privileged, suspended, removed, and cross-tenant actors with least privilege and final-commit authorization.
- **SHIP-009** Use fresh, stale, conflicting, deleted, archived, and partially migrated records; expose uncertainty rather than silently choosing.
- **SHIP-010** Repeat and race operations before commit, after commit before response, and after partial downstream success; require safe idempotency.
- **SHIP-011** Force timeout, disconnect, quota, dependency error, malformed response, regional failover, and recovery failure.
- **SHIP-012** Use supported browsers, devices, network qualities, locales, time zones, input methods, and assistive technologies.
- **SHIP-013** Measure median and tail latency, throughput, resource use, queue depth, retries, and degradation at normal and supported boundary load.
- **SHIP-014** Use inert injection canaries across markup, script, SQL, templates, commands, paths, headers, CSV formulas, and logs.
- **SHIP-015** Inspect URL, referrer, DOM, storage, clipboard, telemetry, logs, traces, notifications, exports, caches, backups, and screenshots for leakage.
- **SHIP-016** Verify labels, roles, names, descriptions, focus, keyboard behavior, announcements, reflow, contrast, motion, alternatives, and error recovery.
- **SHIP-017** Translate and lengthen text, switch RTL/LTR direction, change number/date/currency formats, and use unsupported glyph fallbacks.
- **SHIP-018** Delete, restore, archive, expire, retain, export, anonymize, and purge; reconcile user-visible, indexed, cached, and backed-up state.
- **SHIP-019** Verify one coherent audit trail with actor, authority, target, old/new state, time, source, correlation ID, attempts, and outcome.
- **SHIP-020** Define observable success and failure signals, alert thresholds, dashboards, ownership, runbooks, and a way to test the monitors.
- **SHIP-021** Compare intended requirement, implementation, deployed behavior, and evidence; do not promote inspected code or a single run into a pass.
- **SHIP-022** Segment results by role, tenant, locale, platform, data shape, load, and consequential workflow so averages do not hide severe failures.
- **SHIP-023** Run destructive, high-volume, privacy-invasive, and security probes only in an authorized isolated environment with recovery and stop conditions.
- **SHIP-024** State residual risk, untested combinations, evidence tier, confidence limits, rollback trigger, and owner before recommending release.

[Back to Cross-cutting quality index](../../cross-cutting.md)
