docs

Appearance

Production checklist

Verify Seams release identity, origins, policy, lifecycle recovery, accessibility, observability, and rollback before launch.

Production checklist ​

Complete this list against the exact artifacts and environment that will serve users.

Build and identity ​

  • [ ] SDK package code and hosted wallet assets come from a compatible release.
  • [ ] The docs, application, wallet runtime, workers, and WASM build without uncommitted generated output.
  • [ ] Network, project environment, wallet origin, and RP ID match the target lane.

Security boundaries ​

  • [ ] Exact origin allowlists, CSP, iframe message validation, and request authentication are enabled.
  • [ ] Browser configuration contains no secrets.
  • [ ] Router A/B custody roles have independent credentials and operational authority where strict isolation is claimed.
  • [ ] Challenge, registration, recovery, export, and signing endpoints have appropriate rate and replay controls.

Product flows ​

  • [ ] Registration, unlock, first signing, cancellation, recovery, linked device approval, export, and revocation complete on supported browsers.
  • [ ] Expired sessions, retryable provisioning, transport failure, policy denial, and uncertain broadcast state have clear recovery actions.
  • [ ] Mobile, keyboard, screen-reader, reduced-motion, and 200% zoom checks pass for the wallet surfaces.

Operations ​

  • [ ] Audit events exclude credentials, key material, OTP codes, and tokens.
  • [ ] Alerts identify the affected lane and boundary without exposing secrets.
  • [ ] Backup, restore, rollback, and secret-rotation procedures have been rehearsed.
  • [ ] Support can map public error codes to the current troubleshooting runbook.

Tenant-root release ​

  • [ ] The deployed release includes the intended refresh admission policy; same-operation retries replay, and a distinct manual refresh during the hourly cooldown is rejected before provider work.
  • [ ] Fresh ECDSA and Ed25519 registration and signing pass on the deployed lane, with stable wallet identity across tenant-root refresh.
  • [ ] A/B backup objects and the authoritative identity/activation metadata needed for managed restore are recoverable. Each role can access only its configured backup key through its runtime credential.
  • [ ] Managed restore completes its mandatory forward refresh, and interrupted activation/retirement can resume from recorded checkpoints.
  • [ ] Published security claims match actual administration and key-retention boundaries. Shared KMS versions do not establish per-tenant erasure.

R120 implementation closure does not complete this deployment checklist. Keep R121 recovery UI/CLI and R122 portability unavailable until their own operating paths ship; do not infer availability from a design document.