What problem does it solve?
This Skill ensures clinical applications are crash-safe, resumable, and reliable by enforcing transactional persistence, integrity checks, and clear user-facing recovery paths, reducing data loss and downtime in clinical workflows.
Core Features & Use Cases
- Transactional persistence with temp -> fsync -> rename to prevent data loss
- Encrypted local state DB holding artifact references, hashes, job states, and review states
- Resume behavior: continue from last completed stage and restore field states
- User-facing recovery: clear error messages and guided actions for re-import or re-run
- Observability: log error codes, job IDs, timings, and model versions with no PHI
- Reliability testing: chaos tests and end-to-end regression validations
Quick Start
Run a reliability test plan on a sample clinical workflow to verify transactional persistence, resume after interruption, and user-facing error recovery.