reliability

Enforce transactional persistence and resume logic for clinical applications.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/JustinChaney2023/orate --skill reliability
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reliability
Source: https://github.com/JustinChaney2023/orate/tree/main/roles/reliability
Command: npx skills add https://github.com/JustinChaney2023/orate --skill reliability

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about reliability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make clinical applications crash-safe and resumable across restarts?

Clinical applications achieve crash-safe resumability through transactional persistence using temp, fsync, and rename operations, alongside encrypted local state databases that restore job states and field states after unexpected interruptions.

What is transactional persistence and how does it prevent data loss in clinical workflows?

Transactional persistence prevents data loss by writing data to a temporary file, synchronizing it to disk with fsync, and atomically renaming it, ensuring clinical workflow data remains intact even if the application crashes mid-write.

How do I implement resume logic that continues from the last completed stage after an interruption?

Resume logic captures the last completed stage and field states in an encrypted local database, allowing interrupted clinical workflows to automatically recover and continue processing without restarting from the beginning.

Does this reliability approach work for clinical tools requiring encrypted state management?

Yes, this reliability approach supports clinical tools by maintaining an encrypted local state database that securely holds artifact references, hashes, job states, and review states without exposing protected health information.

What is the best way to test error recovery and crash safety in clinical applications?

The best way to test clinical application crash safety is running chaos tests and end-to-end regression validations that verify transactional persistence, resume behavior after interruptions, and user-facing error recovery paths.

How do I add observability to clinical workflows without exposing protected health information?

Observability in clinical workflows is achieved by logging error codes, job IDs, timings, and model versions, ensuring system reliability can be monitored and debugged without capturing any protected health information.